Hi,
I'm using SER with Sipura and VoIP GW.
When there is no line available from the VoIP GW, the VoIP GW replies with 486 Busy Here.
The Sipura receives this message and sends an ACK. The ACK has the IP addr. Of the SER. If it is ok, the ACK does not include the "Route" parameter, is it a problem from the Sipura? This cause the SIP to loop the ACK because there is no Route and with the following code, the packet becomes too big!!!
............
if (!method=="REGISTER") record_route();
# ------------------------------------------------------------------ # Loose Route Section # ------------------------------------------------------------------ # subsequent messages withing a dialog should take the # path determined by record-routing if (loose_route()) { append_hf("P-hint: rr-enforced\r\n"); t_relay(); break; }; ......................
Same configuration and same trace
192.168.20.155 is the SIP Proxy
192.168.20.105 is the VoIP GW
192.168.20.90 is the Sipura
312 54.858597 192.168.20.90 192.168.20.155 SIP/SDP Request: INVITE sip:3353@192.168.20.155, with session description 313 54.860243 192.168.20.155 192.168.20.90 SIP Status: 407 Proxy Authentication Required 314 54.877006 192.168.20.90 192.168.20.155 SIP Request: ACK sip:3353@192.168.20.155 315 54.886801 192.168.20.90 192.168.20.155 SIP/SDP Request: INVITE sip:3353@192.168.20.155, with session description 316 54.889720 192.168.20.155 192.168.20.105 SIP/SDP Request: INVITE sip:3353@192.168.20.105:5060, with session description 318 54.924666 192.168.20.105 192.168.20.155 SIP Status: 100 Trying 319 54.925866 192.168.20.155 192.168.20.90 SIP Status: 100 Trying 320 54.950257 192.168.20.105 192.168.20.155 SIP Status: 486 Busy Here 321 54.951442 192.168.20.155 192.168.20.90 SIP Status: 486 Busy Here 323 54.968942 192.168.20.90 192.168.20.155 SIP Request: ACK sip:3353@192.168.20.155 440 55.527290 192.168.20.105 192.168.20.155 SIP Status: 486 Busy Here 441 55.528528 192.168.20.155 192.168.20.90 SIP Status: 486 Busy Here 442 55.547237 192.168.20.90 192.168.20.155 SIP Request: ACK sip:3353@192.168.20.155 627 56.624649 192.168.20.105 192.168.20.155 SIP Status: 486 Busy Here 639 56.626924 192.168.20.155 192.168.20.90 SIP Status: 486 Busy Here 649 56.647321 192.168.20.90 192.168.20.155 SIP Request: ACK sip:3353@192.168.20.155 912 58.719683 192.168.20.105 192.168.20.155 SIP Status: 486 Busy Here 913 58.720967 192.168.20.155 192.168.20.90 SIP Status: 486 Busy Here 916 58.746851 192.168.20.90 192.168.20.155 SIP Request: ACK sip:3353@192.168.20.155 1192 62.806510 192.168.20.105 192.168.20.155 SIP Status: 486 Busy Here 1193 62.807741 192.168.20.155 192.168.20.90 SIP Status: 486 Busy Here 1194 62.827148 192.168.20.90 192.168.20.155 SIP Request: ACK sip:3353@192.168.20.155 1417 66.892115 192.168.20.105 192.168.20.155 SIP Status: 486 Busy Here 1418 66.893350 192.168.20.155 192.168.20.90 SIP Status: 486 Busy Here 1419 66.907704 192.168.20.90 192.168.20.155 SIP Request: ACK sip:3353@192.168.20.155 1628 68.143481 192.168.20.101 192.168.20.55 SIP
Thanks.
Micheline
_______________________________________________ Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Micheline, Sipura has plenty of parameters that can be tweaked, but the standard should work. ACK should be loose routed if the Route header is present, but maybe your GW hasn't record routed, its a UAS in a call from the PSTN. Thus you should also make sure that if its not, it will be looked up as INVITEs. g-)
----- Original Message ----- From: "Lambert, Micheline (Satnet)" Lambert.M@emssatnet.com To: serusers@lists.iptel.org Sent: Thursday, October 06, 2005 04:13 PM Subject: [Serusers] ACK loop in SER - Route missing problem ?
-
Greger V. Teigre -
Lambert, Micheline (Satnet)