RE: [reSIProcate] Sharing of DUM by UAs a good idea?
One DUM is recommended. BasicCall is setup so that it can call itself
(on a different port and stack instance) for demo/test purposes only.
> -----Original Message-----
> From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:resiprocate-
> devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of C Y
> Sent: Tuesday, January 24, 2006 9:42 AM
> To: Resip Devel
> Subject: [reSIProcate] Sharing of DUM by UAs a good idea?
>
> Hello,
>
> My application is acting as both UAC and UAS
> (listening for and sending INVITEs) - as most SIP
> applications are, I believe.
>
> I read in the reSIProcate wiki that a single DUM can
> be shared by multiple UAs.
> However, I also went through the BasicCall example in
> the dum directory (in the source), and that initiates
> not only 2 DUMs, but also 2 SipStack - one for UAC,
> and for another for UAS.
>
> Now I am confused. Should I be using just a single DUM
> or more?
>
> Thanks in advance for any advice.
>
> Chee
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel