[Serusers] SER with stock Mediaproxy ser.cfg: bug

[Giudice, Salvatore]

I was running SER 0.9.0 with mediaproxy and the default mediaproxy
ser.cfg. I tested two xten clients behind two 2wire 180hg firewalls.
Everything works perfectly if both clients use port 5060 for signaling.
However, if you change either or both to a different signaling port,
such as having each client listen on port 11111, then SER inserts
incorrect entries into the via and record route sets. It will list
itself as sip:ser.whatever.com:11111 when you call a t_relay. The call
can set up fine, but you end up losing the bye's and cancels. Has anyone
else noticed this problem?

 

Thank you, SG

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20050405/87475ecc/attachment.htm>