[reSIProcate] Many DUM -> one SipStack... Does it actually work??

[Byron Campen]

	The TuSelector in the resip stack uses TransactionUser::isForMe 
(SipMessage& msg) to determine which TU to send the message to. The  
TuSelector will hand the message to the first TU that returns true  
when isForMe is called. You can influence how a given DUM answers  
isForMe by registering MessageFilterRules with that particular  
instance of DUM. (see repro/repro.cxx for an example of how this can  
be done)

Best regards,
Byron Campen

> All,
>
> Although I was told several months ago that this should work, I am  
> seeing problems with the same SipStack associated with 2 different  
> UAs.
>
> The Registration of each UA seems to get routed correctly, i.e. the  
> OnSuccess() for the Register for a specific UA is being delivered  
> to the correct UA.
>
> However, when an INVITE is sent to a particular URI, it goes to the  
> first UA that was associated with the SipStack.
>
> Any thoughts?? It seems the transaction layer is tied to IP:PORT  
> somehow which could be a cause of this problem...
>
> Bill Kovar
> Avaya Inc.
> (732) 852-2609
> bkovar at avaya.com
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at list.sipfoundry.org
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20060807/54f00939/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2369 bytes
Desc: not available
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20060807/54f00939/attachment.bin>