I guess the admin guide is not popular.....

You can explicitely say the next hop where SER has to send the message by adding a new line between the Req-URI and the first dot...

:t_uac_dlg:cc_reply BYE sip:00111111111111@11.12.13.134:5060 ->11.12.13.135<- maybe with a sip: prefix... .. Via: SIP/2.0/UDP 31.32.33.34:25972;branch=z9hG4bKdb61c97f9cba17c1

Hope it helps,

Samuel.

Unclassified.

...

...

"Stuart Kirkwood - Jubilee Consutancy Limited" stuart@jubileeconsultancy.com 06/28/05 03:45PM >>>

Hi

I have a problem with the FIFO request below. The SIP request should route through 11.12.13.135 which guards the gateway at 11.12.13.134. The IP packet containing the SIP message that SER generates is good but SER sets the destination IP address of the packet as 11.12.13.134 and not 11.12.13.135. Is there something wrong with my request or is this a bug? Any help appreciated.

:t_uac_dlg:cc_reply BYE sip:00111111111111@11.12.13.134:5060 .. Via: SIP/2.0/UDP 31.32.33.34:25972;branch=z9hG4bKdb61c97f9cba17c1 From: sip:1000@xsipserver.com;tag=c53a53516c552844 To: sip:11111111111@xsipserver.com;tag=3ADD9EA0-1EC0 Call-ID: 7c70b0b24a053e37@192.168.7.21 CSeq: 52779 BYE Route: sip:11.12.13.135;ftag=c53a53516c552844;lr=on Max-Forwards: 69 .. ..

I'm running SER 0.8.14 on Fedora Core 3.

Thank you.

Stuart

_______________________________________________ Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers