Multiple Call Handling using PJSIP

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Alaa,

It's pretty easy to code an announcement system using pjsua, and if you 
don't want to use pjsua you can look at the pjsua code as a guide. 
Basically when the call connects you create a wav player object and 
connect it to the incoming call via the bridge. See the --auto-play 
option in pjsua. You would use --null-audio option so your server 
doesn't need an audio device to clock media flow. You can use a single 
conference bridge and use this for all calls. However you will then be 
limited to using a single processor core which might be a problem if you 
want to handle hundreds of simultaneous calls. Creating a bridge for 
each call is more complicated but will allow your server to take full 
advantage of multiple cores and hence handle more calls.

Regards,

Bill

On 3/2/2016 8:04 AM, alaa wrote:
> I am trying to create a system that can handle Multiple Calls 
> simultaneously and play announcements to each call.
> I need to use PJSIP and PJMedia (not PJSUA).
> Is there any document or sample code on how to use pjsip and pjmedia 
> with multiple calls , and what design structure i should create ?
> should i create one conference bridge to handle all calls or a one for 
> every calls? should i create one pjmedia endpoint or multiple ?
>
>
> -- 
> Signatures
>
> Kind Regards,
>
> **
>
>
> *Alaa Al Ashkar*
>
> Senior Signaling Engineer
>
> **
>
> *Apliman S.A.L*. | P.O. Box 13-5412, Beirut, Lebanon
>
> **
>
> *t.*+961 1 785382/3 ext. 135 | *m.*+961 3 088231 | *e.*** 
> alaa at apliman.com <mailto:alaa at apliman.com>
>
> *web.*<http://www.apliman.com>http://www.apliman.com| 
> *twi.*www.twitter.com <https://twitter.com/AplimanTech>
>
> *in.* www.linkedin.com/apliman 
> <http://www.linkedin.com/company/apliman-technologies>
>
> ---------------------------------------------------------------------------------------------------------------------
>
> Please consider the environment before printing this email.
>
> /This email, including any attachment, is private and confidential. It 
> should not be read, copied, disclosed /
>
> /or otherwise used by any person other than intended recipient(s). If 
> you have received this email in error, /
>
> /please notify the sender immediately/
>
>
>
> _______________________________________________
> Visit our blog: http://blog.pjsip.org
>
> pjsip mailing list
> pjsip at lists.pjsip.org
> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20160302/2104205a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 2826 bytes
Desc: not available
URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20160302/2104205a/attachment.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 35 bytes
Desc: not available
URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20160302/2104205a/attachment.gif>


[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux