On Sun, 2009-11-01 at 13:08 -0800, Scott Lawrence wrote:
> Why do you conclude that sipXbridge modifies the contact for the benefit
> of the proxy?
A couple of days ago I talked to Ranga, who mentioned that the proxy
does not handle maddr parameters correctly, and I have some vague memory
that he said that sipXbridge removed them. In any case, we have to
worry about the situation, since if sipXbridges does *not* remove the
maddr parameter, the proxy *will* handle the request incorrectly.
> Does the bridge leave the contact unmodified when it forwards the INVITE
> to the proxy?
I haven't checked, but I believe so. But that is not particularly
relevant, since the ACK is sent to the Contact that the UAC provided in
its 200 response.
> Could you be clearer about what form the addressing of the ACK takes
> when it arrives from the caller at the bridge and when sent back to the
> caller from the bridge?
The data is in the merged.xml:
UAC sipXbridge UAS
---> INVITE sip:[email protected]:5080;transport=udp
---> INVITE
sip:[email protected]:5060;maddr=192.168.3.76
<--- 200 / Contact:
<sip:comm:49171;transport=Tcp;maddr=192.168.3.47>;automata
<--- 200 / Contact: <sip:[email protected]:5080;transport=udp>
---> ACK sip:[email protected]:5080;transport=udp
---> ACK sip:comm:49171;transport=Tcp / Route:
<sip:192.168.3.76:5060;lr;[sipXecs parameters deleted]>
Dale
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/
