Re: [Serusers] Max Forward Problem.

Hello. I have been experimenting a weird problem in SER. I'm using a SIP-H323 protocol translator from SipQuest. All my callf from SER are going to the SIP-H323. When i made a call and the remote user (in SipQuest) sends a BYE message to SER i get the following answer. U sipquest.mydomain.com:5060 -> sersip.mydomain.com:5060 BYE sip:1111234567@sersip.mydomain.com;ftag=60425286a4;lr=on SIP/2.0 Via: SIP/2.0/UDP sipquest.magenta.cl:5060; branch=z9hG4bKsKpiQfXRAwAFAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA_ From: <sip:1111234567@sersip.mydomain.com>;tag=3896741524 To: <sip:5555832351@sersip.mydomain.com>;tag=60425286a4 CSeq: 1 BYE Call-ID: 60ce9b42-4559-5298-8186-0002a400f1e9(a)64.76.148.242 Contact: <sip:1111234567@sipquest.magenta.cl> Route: <sip:5555832351@sersip.mydomain.com> Max-Forwards: 69 Content-Length: 0 # U sipquest.mydomain.com:5060 -> sersip.mydomain.com:5060 BYE sip:1111234567@sersip.mydomain.com;ftag=60425286a4;lr=on SIP/2.0 Via: SIP/2.0/UDP sipquest.magenta.cl:5060; branch=z9hG4bKsKpiQfXRAwAFAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA_ From: <sip:1111234567@sersip.mydomain.com>;tag=3896741524 To: <sip:5555832351@sersip.mydomain.com>;tag=60425286a4 CSeq: 1 BYE Call-ID: 60ce9b42-4559-5298-8186-0002a400f1e9(a)64.76.148.242 Contact: <sip:1111234567@sipquest.magenta.cl> Route: <sip:5555832351@sersip.mydomain.com> Max-Forwards: 69 Content-Length: 0 # U sersip.mydomain.com:5060 -> sipquest.mydomain.com:5060 SIP/2.0 483 Too Many Hops Via: SIP/2.0/UDP sipquest.magenta.cl:5060;received=sipquest.mydomain.com; branch=z9hG4bKsKpiQfXRAwAFAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA_ From: <sip:1111234567@sersip.mydomain.com>;tag=3896741524 To: <sip:5555832351@sersip.mydomain.com>;tag=60425286a4 CSeq: 1 BYE Call-ID: 60ce9b42-4559-5298-8186-0002a400f1e9(a)64.76.148.242 Server: Sip EXpress router (0.8.14 (i386/linux)) Content-Length: 0 Warning: 392 sersip.mydomain.com:5060 "Noisy feedback tells: pid=14202 req_src_ip=sersip.mydomain.com req_src_port=5060in_uri=sip:1111234567@sersip.mydomain.com;ftag=60425286a4;l r=on out_uri=sip:1111234567@sersip.mydomain.com;ftag=60425286a4;lr=on via_cnt==70" But when the SER user sent yhe BYE message the call is procesed OK. Here is the BYE 64.76.148.242:5060 -> sersip.mydomain.com:5060 BYE sip:1111234567@sipquest.magenta.cl SIP/2.0 Via: SIP/2.0/UDP 64.76.148.242:5060;branch=z9hG4bK2c423483a4283 From: <sip:5555832351@sersip.mydomain.com>;tag=2c423483a4 To: <sip:1111234567@sersip.mydomain.com>;tag=3896741524 Call-ID: 2cce9b42-1f88-34fd-8183-0002a400f1e9(a)64.76.148.242 CSeq: 283 BYE Route: <sip:1111234567@sersip.mydomain.com;ftag=2c423483a4;lr=on> Date: Tue, 31 May 2005 02:39:19 GMT User-Agent: AddPac SIP Gateway Contact: <sip:5555832351@64.76.148.242> Content-Length: 0 Max-Forwards: 70 I'm using RADIUS and this problem is generating at least a 50 radius stop messages. I can send you the SER debug. I hope that someone can help me. Ricardo.- _______________________________________________ Serusers mailing list serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers