Hiut if you take a look at the second ACK, the Route statement reads
Route: sip:0044123456789@212.156.5.134:5060.
which is completely wrong , if what you are saying is correct. Is there anyway of swicthing on loose routing, or does anyone know if quintum accepts lr, or lr=on
Iqbal
B
On 9/7/2005, "Bogdan-Andrei Iancu" bogdan@voice-system.ro wrote:
Hi Iqbal,
considering 200 OK the Route Set: RR: sip:212.156.5.135;ftag=c3ac7b24-a;lr=on RR: sip:111.222.333.444;ftag=c3ac7b24-a;lr=on CT: sip:0044123456789@212.156.5.134:5060
the ACK should be: a)if loose router: RURI: sip:0044123456789@212.156.5.134:5060 R: sip:212.156.5.135;ftag=c3ac7b24-a;lr=on R: sip:111.222.333.444;ftag=c3ac7b24-a;lr=on b) if strict router: RURI: sip:212.156.5.135;ftag=c3ac7b24-a;lr=on R: sip:111.222.333.444;ftag=c3ac7b24-a;lr=on R: sip:0044123456789@212.156.5.134:5060
the ACK you posted looks like an unsuccessful attempt of a strict routing.
regards, bogdan
Iqbal wrote:
Hi
I have a strange looking dialogue, after sending a 200 OK to a quintum box, and get back an ACK, but the Route field seems to be wrong, can someone confirm this.
U 2005/09/06 15:23:16.613003 111.222.333.444:5060 -> 10.20.30.40:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP 10.20.30.40;branch=z9hG4bK-tenor-c3ac-7b24-0018. From: sip:046677@10.20.30.40;tag=c3ac7b24-a. To: sip:123456789@111.222.333.444;tag=1A4297F4-2C9. Date: Tue, 06 Sep 2005 14:07:59 gmt. Call-ID: call-00CC9E9D-4FBE-D311-0207-A@10.20.30.40. Server: Cisco-SIPGateway/IOS-12.x. CSeq: 1 INVITE. Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO. Allow-Events: telephone-event. Contact: sip:0044123456789@212.156.5.134:5060. Record-Route: sip:212.156.5.135;ftag=c3ac7b24-a;lr=on,sip:111.222.333.444;ftag=c3ac7b24-a;lr=on.
Content-Type: application/sdp. Content-Length: 206. . v=0. o=CiscoSystemsSIP-GW-UserAgent 7438 1091 IN IP4 212.156.5.134. s=SIP Call. c=IN IP4 212.156.5.134. t=0 0. m=audio 18590 RTP/AVP 18. c=IN IP4 212.156.5.134. a=rtpmap:18 G729/8000. a=fmtp:18 annexb=yes.
# U 2005/09/06 15:23:16.726095 10.20.30.40:5060 -> 111.222.333.444:5060 ACK sip:111.222.333.444;ftag=c3ac7b24-a;lr=on SIP/2.0. CSeq: 1 ACK. Call-ID: call-00CC9E9D-4FBE-D311-0207-A@10.20.30.40. Contact: sip:046677@10.20.30.40. From: sip:046677@10.20.30.40;tag=c3ac7b24-a. Route: sip:0044123456789@212.156.5.134:5060. Session-GUID: 859321956-876164920-926430820-875782963. To: sip:123456789@111.222.333.444;tag=1A4297F4-2C9. Via: SIP/2.0/UDP 10.20.30.40;branch=z9hG4bK-tenor-c3ac-7b24-0018. User-Agent: Quintum/1.0.0. Quintum: 0c01030b0232360501000715000000000000000d006c0a828180803034363637371301000f0b413031322d313033353941.
Max-Forwards: 70.
I thought the Route field should have the data which it pulls from the Record Route headers
tks
iqbal
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users