Hi,
I am still stuck with the Cisco gateway (SIP-PSTN) disconnecting the call. Bellow is the call trace from ethereal, the problem is that the Cisco gateway (for some reason I don't know) sends a BYE. Does this have anything to do with the ACKS?
I have tested the same scenario with the UA being Windows Messenger and the Cisco Gateway, and there are no problems.
Any advice on troubleshooting this?
Thanks in advance, Hamid
PS: 192.168.11.102 = UA 10.30.30.18 = OpenSER 10.30.30.19 = Cisco Gateway
---------------------------------------------------------------------------- ------------------------------------------- |Time | 192.168.11.102 | 10.30.30.18 | 10.30.30.19 | ---------------------------------------------------------------------------- ------------------------------------------- |9.739 | INVITE SDP ( g729 g711U g711A telephone-event) | |SIP From: sip:102@mydomain.com To:sip:0098146@mydomain.com | |(5060) ------------------> (5060) | | |9.743 | | INVITE SDP ( g729 g711U g711A telephone-event) |SIP Request | | |(5060) ------------------> (5060) | |9.743 | 100 trying -- your call is important to us | |SIP Status | |(5060) <------------------ (5060) | | |9.752 | | 100 Trying| |SIP Status | | |(5060) <------------------ (5060) | |9.932 | 100 Trying| | |SIP Status | |(5060) <------------------ (5060) | | |11.668 | | 183 Session Progress SDP ( g729 telephone-event) |SIP Status | | |(5060) <------------------ (5060) | |11.670 | 183 Session Progress SDP ( g729 telephone-event) | |SIP Status | |(5060) <------------------ (5060) | | |11.671 | | 200 OK SDP ( g729 telephone-event) |SIP Status | | |(5060) <------------------ (5060) | |11.673 | 200 OK SDP ( g729 telephone-event) | |SIP Status | |(5060) <------------------ (5060) | | |11.687 | RTP (g729) | |RTP Num packets:1634 Duration:19.469s ssrc:126289683 | |(6000) <-------------------------------------- (16400) | |11.735 | ACK | | |SIP Request | |(5060) ------------------> (5060) | | |12.003 | RTP (g729) | |RTP Num packets:18 Duration:0.161s ssrc:3634 | |(6000) --------------------------------------> (16400) | |12.169 | | 200 OK SDP ( g729 telephone-event) |SIP Status | | |(5060) <------------------ (5060) | |12.171 | 200 OK SDP ( g729 telephone-event) | |SIP Status | |(5060) <------------------ (5060) | | |12.184 | RTP (g729) | |RTP Num packets:100 Duration:0.979s ssrc:3634 | |(6000) --------------------------------------> (16400) | |12.254 | ACK | | |SIP Request | |(5060) ------------------> (5060) | | |13.169 | | 200 OK SDP ( g729 telephone-event) |SIP Status | | |(5060) <------------------ (5060) | |13.172 | 200 OK SDP ( g729 telephone-event) | |SIP Status | |(5060) <------------------ (5060) | | |13.183 | RTP (g729) | |RTP Num packets:200 Duration:1.980s ssrc:3634 | |(6000) --------------------------------------> (16400) | |13.240 | ACK | | |SIP Request | |(5060) ------------------> (5060) | | |15.169 | | 200 OK SDP ( g729 telephone-event) |SIP Status | | |(5060) <------------------ (5060) | |15.171 | 200 OK SDP ( g729 telephone-event) | |SIP Status | |(5060) <------------------ (5060) | | |15.183 | RTP (g729) | |RTP Num packets:400 Duration:3.980s ssrc:3634 | |(6000) --------------------------------------> (16400) | |15.235 | ACK | | |SIP Request | |(5060) ------------------> (5060) | | |19.169 | | 200 OK SDP ( g729 telephone-event) |SIP Status | | |(5060) <------------------ (5060) | |19.172 | 200 OK SDP ( g729 telephone-event) | |SIP Status | |(5060) <------------------ (5060) | | |19.183 | RTP (g729) | |RTP Num packets:400 Duration:3.980s ssrc:3634 | |(6000) --------------------------------------> (16400) | |19.245 | ACK | | |SIP Request | |(5060) ------------------> (5060) | | |23.169 | | 200 OK SDP ( g729 telephone-event) |SIP Status | | |(5060) <------------------ (5060) | |23.172 | 200 OK SDP ( g729 telephone-event) | |SIP Status | |(5060) <------------------ (5060) | | |23.183 | RTP (g729) | |RTP Num packets:400 Duration:3.980s ssrc:3634 | |(6000) --------------------------------------> (16400) | |23.256 | ACK | | |SIP Request | |(5060) ------------------> (5060) | | |27.169 | | 200 OK SDP ( g729 telephone-event) |SIP Status | | |(5060) <------------------ (5060) | |27.172 | 200 OK SDP ( g729 telephone-event) | |SIP Status | |(5060) <------------------ (5060) | | |27.211 | ACK | | |SIP Request | |(5060) ------------------> (5060) | | |27.212 | RTP (g729) | |RTP Num packets:402 Duration:3.971s ssrc:3634 | |(6000) --------------------------------------> (16400) | |31.170 | | BYE | |SIP Request | | |(5060) <------------------ (55584) | |31.174 | BYE | | |SIP Request | |(5060) <------------------ (5060) | | |31.221 | 200 OK | | |SIP Status | |(5060) ------------------> (5060) | | |31.223 | | 200 OK | |SIP Status | | |(5060) ------------------> (5060) | |39.683 | 408 Request Timeout | |SIP Status | |(5060) <------------------ (5060) | | |39.751 | ACK | | |SIP Request | |(5060) ------------------> (5060) | | |39.752 | | ACK | |SIP Request | | |(5060) ------------------> (5060) |
Hi,
your trace is a little bit unreadable (format is messed up), but on a first view the problem looks to be related to ACK (I see several 200/ACK retransmissions) - so either the ACK is not correctly routed to the GW, either the ACK is buggy and is not accepted by the GW.
regards, bogdan
Hamid Ali Asgari wrote:
Hi,
I am still stuck with the Cisco gateway (SIP-PSTN) disconnecting the call. Bellow is the call trace from ethereal, the problem is that the Cisco gateway (for some reason I don't know) sends a BYE. Does this have anything to do with the ACKS?
I have tested the same scenario with the UA being Windows Messenger and the Cisco Gateway, and there are no problems.
Any advice on troubleshooting this?
Thanks in advance, Hamid
PS: 192.168.11.102 = UA 10.30.30.18 = OpenSER 10.30.30.19 = Cisco Gateway
|Time | 192.168.11.102 | 10.30.30.18 | 10.30.30.19 |
|9.739 | INVITE SDP ( g729 g711U g711A telephone-event) | |SIP From: sip:102@mydomain.com To:sip:0098146@mydomain.com | |(5060) ------------------> (5060) | | |9.743 | | INVITE SDP ( g729 g711U g711A telephone-event) |SIP Request | | |(5060) ------------------> (5060) | |9.743 | 100 trying -- your call is important to us | |SIP Status | |(5060) <------------------ (5060) | | |9.752 | | 100 Trying| |SIP Status | | |(5060) <------------------ (5060) | |9.932 | 100 Trying| | |SIP Status | |(5060) <------------------ (5060) | | |11.668 | | 183 Session Progress SDP ( g729 telephone-event) |SIP Status | | |(5060) <------------------ (5060) | |11.670 | 183 Session Progress SDP ( g729 telephone-event) | |SIP Status | |(5060) <------------------ (5060) | | |11.671 | | 200 OK SDP ( g729 telephone-event) |SIP Status | | |(5060) <------------------ (5060) | |11.673 | 200 OK SDP ( g729 telephone-event) | |SIP Status | |(5060) <------------------ (5060) | | |11.687 | RTP (g729) | |RTP Num packets:1634 Duration:19.469s ssrc:126289683 | |(6000) <-------------------------------------- (16400) | |11.735 | ACK | | |SIP Request | |(5060) ------------------> (5060) | | |12.003 | RTP (g729) | |RTP Num packets:18 Duration:0.161s ssrc:3634 | |(6000) --------------------------------------> (16400) | |12.169 | | 200 OK SDP ( g729 telephone-event) |SIP Status | | |(5060) <------------------ (5060) | |12.171 | 200 OK SDP ( g729 telephone-event) | |SIP Status | |(5060) <------------------ (5060) | | |12.184 | RTP (g729) | |RTP Num packets:100 Duration:0.979s ssrc:3634 | |(6000) --------------------------------------> (16400) | |12.254 | ACK | | |SIP Request | |(5060) ------------------> (5060) | | |13.169 | | 200 OK SDP ( g729 telephone-event) |SIP Status | | |(5060) <------------------ (5060) | |13.172 | 200 OK SDP ( g729 telephone-event) | |SIP Status | |(5060) <------------------ (5060) | | |13.183 | RTP (g729) | |RTP Num packets:200 Duration:1.980s ssrc:3634 | |(6000) --------------------------------------> (16400) | |13.240 | ACK | | |SIP Request | |(5060) ------------------> (5060) | | |15.169 | | 200 OK SDP ( g729 telephone-event) |SIP Status | | |(5060) <------------------ (5060) | |15.171 | 200 OK SDP ( g729 telephone-event) | |SIP Status | |(5060) <------------------ (5060) | | |15.183 | RTP (g729) | |RTP Num packets:400 Duration:3.980s ssrc:3634 | |(6000) --------------------------------------> (16400) | |15.235 | ACK | | |SIP Request | |(5060) ------------------> (5060) | | |19.169 | | 200 OK SDP ( g729 telephone-event) |SIP Status | | |(5060) <------------------ (5060) | |19.172 | 200 OK SDP ( g729 telephone-event) | |SIP Status | |(5060) <------------------ (5060) | | |19.183 | RTP (g729) | |RTP Num packets:400 Duration:3.980s ssrc:3634 | |(6000) --------------------------------------> (16400) | |19.245 | ACK | | |SIP Request | |(5060) ------------------> (5060) | | |23.169 | | 200 OK SDP ( g729 telephone-event) |SIP Status | | |(5060) <------------------ (5060) | |23.172 | 200 OK SDP ( g729 telephone-event) | |SIP Status | |(5060) <------------------ (5060) | | |23.183 | RTP (g729) | |RTP Num packets:400 Duration:3.980s ssrc:3634 | |(6000) --------------------------------------> (16400) | |23.256 | ACK | | |SIP Request | |(5060) ------------------> (5060) | | |27.169 | | 200 OK SDP ( g729 telephone-event) |SIP Status | | |(5060) <------------------ (5060) | |27.172 | 200 OK SDP ( g729 telephone-event) | |SIP Status | |(5060) <------------------ (5060) | | |27.211 | ACK | | |SIP Request | |(5060) ------------------> (5060) | | |27.212 | RTP (g729) | |RTP Num packets:402 Duration:3.971s ssrc:3634 | |(6000) --------------------------------------> (16400) | |31.170 | | BYE | |SIP Request | | |(5060) <------------------ (55584) | |31.174 | BYE | | |SIP Request | |(5060) <------------------ (5060) | | |31.221 | 200 OK | | |SIP Status | |(5060) ------------------> (5060) | | |31.223 | | 200 OK | |SIP Status | | |(5060) ------------------> (5060) | |39.683 | 408 Request Timeout | |SIP Status | |(5060) <------------------ (5060) | | |39.751 | ACK | | |SIP Request | |(5060) ------------------> (5060) | | |39.752 | | ACK | |SIP Request | | |(5060) ------------------> (5060) |
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Hi,
Thnaks for the reply.
I do aslo guess that the problem is something related to the ACKs, but the problem is that OPENSER gets the ACK from the UA, but doesn't pass the ACKS to the gateway, something like bellow:
UA OpenSER Cisco Gateway ------------------------------------------------------- | Invite | | | -------------> | | | | Invite | | | ---------------> | | | 100 Trying | | |<--------------- | | 100 Trying | | | <------------ | | | | 183 Session Progress | | | <--------------- | |183 Session Progress | | | <------------- | | | | 200 OK | | | <--------------- | | 200 OK | | |<-------------- | | | | | | ACK | | | --------------> | | | | | RTP Traffic from now on ..... | | ------------------------------------------> | | | | | 200 OK | | | <--------------- | | 200 OK | | |<-------------- | | | | | | ACK | | | --------------> | | | | 200 OK | | | <--------------- | | 200 OK | | |<-------------- | | | ACK | | | --------------> | | | | 200 OK | | | <--------------- | | 200 OK | | |<-------------- | | ... ... ... ... ... ...
| | BYE | | |<--------------- | | BYE | | | <------------ | |
From what I see, OpenSER doesn't pass the ACK from the UA to the gateway,
and the Cisco gateway give up after a couple of retries. As you see above OpenSER recives the ACK from the UA but doesn't pass along the ACKs to the Cisco gateway.
I have taken a look at the OpenSER debugs; there some lines which I guess (not sure) are related to this:
0(7989) Warning: sl_send_reply: I won't send a reply for ACK!!
The number of the ACKs sent by the UA matches the number of times I see the above line in OpenSER debugs. Also, that is not observed in calls from Windows Messenger to the Cisco gateway.
Any clues?
Thanks, Hamid
0(7989) Warning: sl_send_reply: I won't send a reply for ACK!!
This usually means that you route ACK wrong. They should be routed by the loose_route() block (or it is a bad formatted ACK).
This is my ACK handling:
if (loose_route()) { # loose route requests are not authenticated xlog("L_INFO","$ci beginning loose_route processing...\n"); route(32); # handle in-dialog requests exit; } if ( is_method("ACK") ) { if ( t_check_trans() ) { # non loose-route, but stateful ACK; must be an ACK after a 487 xlog("L_INFO","$ci local end-to-end ACK for an existent INVITE transaction detected ...t_relay()\n"); t_relay(); } else { xlog("L_WARN","$ci ACK without matching transaction ... ignore and discard.\n"); } exit; }
regards klaus
I don't guess it is bad ACK routing, since the ACK routing works fine if the UA is Windows Messenger.
But it may be a bad formated ACK (not sure). Bellow are the ACKS from both UAs, one difference is in the RequestLine; the one form Wmessenger has "lr=on" but the other one from the my UA sets only "lr". Alothough I am not sure if this would be the case.
Hope SIP gurus and openser pros could shine a light on this.
Thanks, Hamid
ACK from Windows Messenger -------------------------- Session Initiation Protocol RequestLine: ACK sip:85.15.7.18;ftag=27ccb8cd605f40e7bb41568eaec3a335;lr=on SIP/2.0 Method: ACK Resent Packet: False Message Header Via: SIP/2.0/UDP 192.168.11.136:9560 MaxForwards: 70 From: "103@shatel.ir" sip:103@shatel.ir; tag=27ccb8cd605f40e7bb41568eaec3a335; epid=9998c5a301 SIP Display info: "103@shatel.ir" SIP from address: sip:103@shatel.ir SIP tag: 27ccb8cd605f40e7bb41568eaec3a335 To: sip:0098146@shatel.ir;tag=22FA78219D SIP to address: sip:0098146@shatel.ir SIP tag: 22FA78219D CallID: d253f8dd0d6546819347b0ba28986e24 CSeq: 1 ACK Route: sip:0098146@85.15.7.19:5060 UserAgent: RTC/1.3 ContentLength: 0
ACK from my UA --------------------------------- Session Initiation Protocol RequestLine: ACK sip:85.15.7.18;ftag=analogsip28734;lr SIP/2.0 Method: ACK Resent Packet: False Message Header Via: SIP/2.0/UDP 192.168.11.102:5060;branch=z9hG4bK9072 To: 0098146 sip:0098146@shatel.ir;tag=9A65C1F0E SIP Display info: 0098146 SIP to address: sip:0098146@shatel.ir SIP tag: 9A65C1F0E From: 102@shatel.ir sip:102@shatel.ir;tag=analogsip28734 SIP Display info: 102@shatel.ir SIP from address: sip:102@shatel.ir SIP tag: analogsip28734 CallID: 32268@192.168.11.102 CSeq: 101 ACK Route:sip:0098146@shatel.ir Contact: sip:102@192.168.11.102:5060 Contact Binding: sip:102@192.168.11.102:5060 URI: sip:102@192.168.11.102:5060 SIP contact address: sip:102@192.168.11.102:5060 MaxForwards: 70 ContentLength: 0
Hi Hamid!
Please send also the 200 OK received be the SIP client - to verify if the ACK is correct. Further, please use ngrep as the SIP dumps are more readable:
ngrep -W byline port 5060
regards klaus
Hamid Ali Asgari wrote:
I don't guess it is bad ACK routing, since the ACK routing works fine if the UA is Windows Messenger.
But it may be a bad formated ACK (not sure). Bellow are the ACKS from both UAs, one difference is in the RequestLine; the one form Wmessenger has "lr=on" but the other one from the my UA sets only "lr". Alothough I am not sure if this would be the case.
Hope SIP gurus and openser pros could shine a light on this.
Thanks, Hamid
ACK from Windows Messenger
Session Initiation Protocol RequestLine: ACK sip:85.15.7.18;ftag=27ccb8cd605f40e7bb41568eaec3a335;lr=on SIP/2.0 Method: ACK Resent Packet: False Message Header Via: SIP/2.0/UDP 192.168.11.136:9560 MaxForwards: 70 From: "103@shatel.ir" sip:103@shatel.ir; tag=27ccb8cd605f40e7bb41568eaec3a335; epid=9998c5a301 SIP Display info: "103@shatel.ir" SIP from address: sip:103@shatel.ir SIP tag: 27ccb8cd605f40e7bb41568eaec3a335 To: sip:0098146@shatel.ir;tag=22FA78219D SIP to address: sip:0098146@shatel.ir SIP tag: 22FA78219D CallID: d253f8dd0d6546819347b0ba28986e24 CSeq: 1 ACK Route: sip:0098146@85.15.7.19:5060 UserAgent: RTC/1.3 ContentLength: 0
ACK from my UA
Session Initiation Protocol RequestLine: ACK sip:85.15.7.18;ftag=analogsip28734;lr SIP/2.0 Method: ACK Resent Packet: False Message Header Via: SIP/2.0/UDP 192.168.11.102:5060;branch=z9hG4bK9072 To: 0098146 sip:0098146@shatel.ir;tag=9A65C1F0E SIP Display info: 0098146 SIP to address: sip:0098146@shatel.ir SIP tag: 9A65C1F0E From: 102@shatel.ir sip:102@shatel.ir;tag=analogsip28734 SIP Display info: 102@shatel.ir SIP from address: sip:102@shatel.ir SIP tag: analogsip28734 CallID: 32268@192.168.11.102 CSeq: 101 ACK Route:sip:0098146@shatel.ir Contact: sip:102@192.168.11.102:5060 Contact Binding: sip:102@192.168.11.102:5060 URI: sip:102@192.168.11.102:5060 SIP contact address: sip:102@192.168.11.102:5060 MaxForwards: 70 ContentLength: 0
Hi,
Here comes the dump from ngrep for a sample call.
Any idea what's wrong?
Thanks,
Hamid
input: 102-to-C3660.sip.cap
#
U 192.168.11.102:5060 -> 85.15.7.18:5060
INVITE sip:0098146@shatel.ir SIP/2.0..Via: SIP/2.0/UDP 192.168.11.102:5060;
branch=z9hG4bK10145..To: 0098146 sip:0098146@shatel.ir..From: 102@shatel.
ir sip:102@shatel.ir;tag=analog-sip28734..Call-ID: 32268@192.168.11.102..
CSeq: 101 INVITE..Contact: sip:102@192.168.11.102:5060..Max-Forwards: 70.
.Allow: INVITE, BYE, CANCEL, ACK, OPTIONS, REFER, NOTIFY..Supported: replac
es..Content-Type: application/sdp..Content-Length: 251....v=0..o=adiPhone 3
2268 32268 IN IP4 192.168.11.102..s=Phone Call..c=IN IP4 192.168.11.102..t=
0 0..m=audio 6000 RTP/AVP 18 0 8 103..a=rtpmap:18 G729/8000/1..a=rtpmap:0 P
CMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:103 telephone-event/8000..a=fmtp:1
03 0-15..
#
U 85.15.7.18:5060 -> 85.15.7.19:5060
INVITE sip:0098146@shatel.ir SIP/2.0..Record-Route: <sip:85.15.7.18;ftag=an
alog-sip28734;lr=on>..Via: SIP/2.0/UDP 85.15.7.18;branch=0..Via: SIP/2.0/UD
P 192.168.11.102:5060;branch=z9hG4bK10145..To: 0098146 <sip:0098146@shatel.
ir>..From: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..Call-ID:
32268@192.168.11.102..CSeq: 101 INVITE..Contact: <sip:102@192.168.11.102:50
60>..Max-Forwards: 69..Allow: INVITE, BYE, CANCEL, ACK, OPTIONS, REFER, NOT
IFY..Supported: replaces..Content-Type: application/sdp..Content-Length: 25
1....v=0..o=adiPhone 32268 32268 IN IP4 192.168.11.102..s=Phone Call..c=IN
IP4 192.168.11.102..t=0 0..m=audio 6000 RTP/AVP 18 0 8 103..a=rtpmap:18 G72
9/8000/1..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:103 telephon
e-event/8000..a=fmtp:103 0-15..
#
U 85.15.7.18:5060 -> 192.168.11.102:5060
SIP/2.0 100 trying -- your call is important to us..Via: SIP/2.0/UDP 192.16
8.11.102:5060;branch=z9hG4bK10145..To: 0098146 sip:0098146@shatel.ir..Fro
m: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..Call-ID: 32268@19
2.168.11.102..CSeq: 101 INVITE..Server: OpenSer (1.0.1 (i386/linux))..Conte
nt-Length: 0..Warning: 392 85.15.7.18:5060 "Noisy feedback tells: pid=6514
req_src_ip=192.168.11.102 req_src_port=5060 in_uri=sip:0098146@shatel.ir o
ut_uri=sip:0098146@shatel.ir via_cnt==1"....
#
U 85.15.7.19:5060 -> 85.15.7.18:5060
SIP/2.0 100 Trying..Via: SIP/2.0/UDP 85.15.7.18;branch=0,SIP/2.0/UDP 192.16
8.11.102:5060;branch=z9hG4bK10145..From: 102@shatel.ir sip:102@shatel.ir;
tag=analog-sip28734..To: 0098146 sip:0098146@shatel.ir;tag=9A65C-1F0E..Da
te: Fri, 01 Mar 2002 00:10:32 GMT..Call-ID: 32268@192.168.11.102..Server: C
isco-SIPGateway/IOS-12.x..CSeq: 101 INVITE..Allow-Events: telephone-event..
Content-Length: 0....
#
U 85.15.7.18:5060 -> 192.168.11.102:5060
SIP/2.0 100 Trying..Via: SIP/2.0/UDP 192.168.11.102:5060;branch=z9hG4bK1014
5..From: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..To: 0098146
sip:0098146@shatel.ir;tag=9A65C-1F0E..Date: Fri, 01 Mar 2002 00:10:32 GM
T..Call-ID: 32268@192.168.11.102..Server: Cisco-SIPGateway/IOS-12.x..CSeq:
101 INVITE..Allow-Events: telephone-event..Content-Length: 0....
#
U 85.15.7.19:5060 -> 85.15.7.18:5060
SIP/2.0 183 Session Progress..Via: SIP/2.0/UDP 85.15.7.18;branch=0,SIP/2.0/
UDP 192.168.11.102:5060;branch=z9hG4bK10145..From: 102@shatel.ir <sip:102@s
hatel.ir>;tag=analog-sip28734..To: 0098146 sip:0098146@shatel.ir;tag=9A65
C-1F0E..Date: Fri, 01 Mar 2002 00:10:32 GMT..Call-ID: 32268@192.168.11.102.
.Server: Cisco-SIPGateway/IOS-12.x..CSeq: 101 INVITE..Allow: INVITE, OPTION
S, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE,
REGISTER..Allow-Events: telephone-event..Contact: <sip:0098146@85.15.7.19:5
060>..Record-Route: sip:85.15.7.18;ftag=analog-sip28734;lr=on..Content-Di
sposition: session;handling=required..Content-Type: application/sdp..Conten
t-Length: 252....v=0..o=CiscoSystemsSIP-GW-UserAgent 6865 4884 IN IP4 85.15
.7.19..s=SIP Call..c=IN IP4 85.15.7.19..t=0 0..m=audio 16400 RTP/AVP 18 103
..c=IN IP4 85.15.7.19..a=rtpmap:18 G729/8000..a=fmtp:18 annexb=no..a=rtpmap
:103 telephone-event/8000..a=fmtp:103 0-15..
#
U 85.15.7.18:5060 -> 192.168.11.102:5060
SIP/2.0 183 Session Progress..Via: SIP/2.0/UDP 192.168.11.102:5060;branch=z
9hG4bK10145..From: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..T
o: 0098146 sip:0098146@shatel.ir;tag=9A65C-1F0E..Date: Fri, 01 Mar 2002 0
0:10:32 GMT..Call-ID: 32268@192.168.11.102..Server: Cisco-SIPGateway/IOS-12
.x..CSeq: 101 INVITE..Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COME
T, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTER..Allow-Events: telephon
e-event..Contact: sip:0098146@85.15.7.19:5060..Record-Route: <sip:85.15.7
.18;ftag=analog-sip28734;lr=on>..Content-Disposition: session;handling=requ
ired..Content-Type: application/sdp..Content-Length: 252....v=0..o=CiscoSys
temsSIP-GW-UserAgent 6865 4884 IN IP4 85.15.7.19..s=SIP Call..c=IN IP4 85.1
5.7.19..t=0 0..m=audio 16400 RTP/AVP 18 103..c=IN IP4 85.15.7.19..a=rtpmap:
18 G729/8000..a=fmtp:18 annexb=no..a=rtpmap:103 telephone-event/8000..a=fmt
p:103 0-15..
#
U 85.15.7.19:5060 -> 85.15.7.18:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 85.15.7.18;branch=0,SIP/2.0/UDP 192.168.11
.102:5060;branch=z9hG4bK10145..From: 102@shatel.ir sip:102@shatel.ir;tag=
analog-sip28734..To: 0098146 sip:0098146@shatel.ir;tag=9A65C-1F0E..Date:
Fri, 01 Mar 2002 00:10:32 GMT..Call-ID: 32268@192.168.11.102..Server: Cisco
-SIPGateway/IOS-12.x..CSeq: 101 INVITE..Allow: INVITE, OPTIONS, BYE, CANCEL
, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTER..Allo
w-Events: telephone-event..Contact: sip:0098146@85.15.7.19:5060..Record-R
oute: sip:85.15.7.18;ftag=analog-sip28734;lr=on..Content-Type: applicatio
n/sdp..Content-Length: 252....v=0..o=CiscoSystemsSIP-GW-UserAgent 6865 4884
IN IP4 85.15.7.19..s=SIP Call..c=IN IP4 85.15.7.19..t=0 0..m=audio 16400 R
TP/AVP 18 103..c=IN IP4 85.15.7.19..a=rtpmap:18 G729/8000..a=fmtp:18 annexb
=no..a=rtpmap:103 telephone-event/8000..a=fmtp:103 0-15..
#
U 85.15.7.18:5060 -> 192.168.11.102:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 192.168.11.102:5060;branch=z9hG4bK10145..F
rom: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..To: 0098146 <si
p:0098146@shatel.ir>;tag=9A65C-1F0E..Date: Fri, 01 Mar 2002 00:10:32 GMT..C
all-ID: 32268@192.168.11.102..Server: Cisco-SIPGateway/IOS-12.x..CSeq: 101
INVITE..Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBS
CRIBE, NOTIFY, INFO, UPDATE, REGISTER..Allow-Events: telephone-event..Conta
ct: sip:0098146@85.15.7.19:5060..Record-Route: <sip:85.15.7.18;ftag=analo
g-sip28734;lr=on>..Content-Type: application/sdp..Content-Length: 252....v=
0..o=CiscoSystemsSIP-GW-UserAgent 6865 4884 IN IP4 85.15.7.19..s=SIP Call..
c=IN IP4 85.15.7.19..t=0 0..m=audio 16400 RTP/AVP 18 103..c=IN IP4 85.15.7.
19..a=rtpmap:18 G729/8000..a=fmtp:18 annexb=no..a=rtpmap:103 telephone-even
t/8000..a=fmtp:103 0-15..
#
U 192.168.11.102:5060 -> 85.15.7.18:5060
ACK sip:85.15.7.18;ftag=analog-sip28734;lr SIP/2.0..Via: SIP/2.0/UDP 192.16
8.11.102:5060;branch=z9hG4bK9072..To: 0098146 sip:0098146@shatel.ir;tag=9
A65C-1F0E..From: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..Cal
l-ID: 32268@192.168.11.102..CSeq: 101 ACK..Route:sip:0098146@shatel.ir..C
ontact: sip:102@192.168.11.102:5060..Max-Forwards: 70..Content-Length: 0.
...
#
U 85.15.7.19:5060 -> 85.15.7.18:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 85.15.7.18;branch=0,SIP/2.0/UDP 192.168.11
.102:5060;branch=z9hG4bK10145..From: 102@shatel.ir sip:102@shatel.ir;tag=
analog-sip28734..To: 0098146 sip:0098146@shatel.ir;tag=9A65C-1F0E..Date:
Fri, 01 Mar 2002 00:10:32 GMT..Call-ID: 32268@192.168.11.102..Server: Cisco
-SIPGateway/IOS-12.x..CSeq: 101 INVITE..Allow: INVITE, OPTIONS, BYE, CANCEL
, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTER..Allo
w-Events: telephone-event..Contact: sip:0098146@85.15.7.19:5060..Record-R
oute: sip:85.15.7.18;ftag=analog-sip28734;lr=on..Content-Type: applicatio
n/sdp..Content-Length: 252....v=0..o=CiscoSystemsSIP-GW-UserAgent 6865 4884
IN IP4 85.15.7.19..s=SIP Call..c=IN IP4 85.15.7.19..t=0 0..m=audio 16400 R
TP/AVP 18 103..c=IN IP4 85.15.7.19..a=rtpmap:18 G729/8000..a=fmtp:18 annexb
=no..a=rtpmap:103 telephone-event/8000..a=fmtp:103 0-15..
#
U 85.15.7.18:5060 -> 192.168.11.102:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 192.168.11.102:5060;branch=z9hG4bK10145..F
rom: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..To: 0098146 <si
p:0098146@shatel.ir>;tag=9A65C-1F0E..Date: Fri, 01 Mar 2002 00:10:32 GMT..C
all-ID: 32268@192.168.11.102..Server: Cisco-SIPGateway/IOS-12.x..CSeq: 101
INVITE..Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBS
CRIBE, NOTIFY, INFO, UPDATE, REGISTER..Allow-Events: telephone-event..Conta
ct: sip:0098146@85.15.7.19:5060..Record-Route: <sip:85.15.7.18;ftag=analo
g-sip28734;lr=on>..Content-Type: application/sdp..Content-Length: 252....v=
0..o=CiscoSystemsSIP-GW-UserAgent 6865 4884 IN IP4 85.15.7.19..s=SIP Call..
c=IN IP4 85.15.7.19..t=0 0..m=audio 16400 RTP/AVP 18 103..c=IN IP4 85.15.7.
19..a=rtpmap:18 G729/8000..a=fmtp:18 annexb=no..a=rtpmap:103 telephone-even
t/8000..a=fmtp:103 0-15..
#
U 192.168.11.102:5060 -> 85.15.7.18:5060
ACK sip:85.15.7.18;ftag=analog-sip28734;lr SIP/2.0..Via: SIP/2.0/UDP 192.16
8.11.102:5060;branch=z9hG4bK10994..To: 0098146 sip:0098146@shatel.ir;tag=
9A65C-1F0E..From: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..Ca
ll-ID: 32268@192.168.11.102..CSeq: 101 ACK..Route:sip:0098146@shatel.ir..
Contact: sip:102@192.168.11.102:5060..Max-Forwards: 70..Content-Length: 0
....
#
U 85.15.7.19:5060 -> 85.15.7.18:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 85.15.7.18;branch=0,SIP/2.0/UDP 192.168.11
.102:5060;branch=z9hG4bK10145..From: 102@shatel.ir sip:102@shatel.ir;tag=
analog-sip28734..To: 0098146 sip:0098146@shatel.ir;tag=9A65C-1F0E..Date:
Fri, 01 Mar 2002 00:10:32 GMT..Call-ID: 32268@192.168.11.102..Server: Cisco
-SIPGateway/IOS-12.x..CSeq: 101 INVITE..Allow: INVITE, OPTIONS, BYE, CANCEL
, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTER..Allo
w-Events: telephone-event..Contact: sip:0098146@85.15.7.19:5060..Record-R
oute: sip:85.15.7.18;ftag=analog-sip28734;lr=on..Content-Type: applicatio
n/sdp..Content-Length: 252....v=0..o=CiscoSystemsSIP-GW-UserAgent 6865 4884
IN IP4 85.15.7.19..s=SIP Call..c=IN IP4 85.15.7.19..t=0 0..m=audio 16400 R
TP/AVP 18 103..c=IN IP4 85.15.7.19..a=rtpmap:18 G729/8000..a=fmtp:18 annexb
=no..a=rtpmap:103 telephone-event/8000..a=fmtp:103 0-15..
#
U 85.15.7.18:5060 -> 192.168.11.102:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 192.168.11.102:5060;branch=z9hG4bK10145..F
rom: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..To: 0098146 <si
p:0098146@shatel.ir>;tag=9A65C-1F0E..Date: Fri, 01 Mar 2002 00:10:32 GMT..C
all-ID: 32268@192.168.11.102..Server: Cisco-SIPGateway/IOS-12.x..CSeq: 101
INVITE..Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBS
CRIBE, NOTIFY, INFO, UPDATE, REGISTER..Allow-Events: telephone-event..Conta
ct: sip:0098146@85.15.7.19:5060..Record-Route: <sip:85.15.7.18;ftag=analo
g-sip28734;lr=on>..Content-Type: application/sdp..Content-Length: 252....v=
0..o=CiscoSystemsSIP-GW-UserAgent 6865 4884 IN IP4 85.15.7.19..s=SIP Call..
c=IN IP4 85.15.7.19..t=0 0..m=audio 16400 RTP/AVP 18 103..c=IN IP4 85.15.7.
19..a=rtpmap:18 G729/8000..a=fmtp:18 annexb=no..a=rtpmap:103 telephone-even
t/8000..a=fmtp:103 0-15..
#
U 192.168.11.102:5060 -> 85.15.7.18:5060
ACK sip:85.15.7.18;ftag=analog-sip28734;lr SIP/2.0..Via: SIP/2.0/UDP 192.16
8.11.102:5060;branch=z9hG4bK24833..To: 0098146 sip:0098146@shatel.ir;tag=
9A65C-1F0E..From: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..Ca
ll-ID: 32268@192.168.11.102..CSeq: 101 ACK..Route:sip:0098146@shatel.ir..
Contact: sip:102@192.168.11.102:5060..Max-Forwards: 70..Content-Length: 0
....
#
U 85.15.7.19:5060 -> 85.15.7.18:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 85.15.7.18;branch=0,SIP/2.0/UDP 192.168.11
.102:5060;branch=z9hG4bK10145..From: 102@shatel.ir sip:102@shatel.ir;tag=
analog-sip28734..To: 0098146 sip:0098146@shatel.ir;tag=9A65C-1F0E..Date:
Fri, 01 Mar 2002 00:10:32 GMT..Call-ID: 32268@192.168.11.102..Server: Cisco
-SIPGateway/IOS-12.x..CSeq: 101 INVITE..Allow: INVITE, OPTIONS, BYE, CANCEL
, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTER..Allo
w-Events: telephone-event..Contact: sip:0098146@85.15.7.19:5060..Record-R
oute: sip:85.15.7.18;ftag=analog-sip28734;lr=on..Content-Type: applicatio
n/sdp..Content-Length: 252....v=0..o=CiscoSystemsSIP-GW-UserAgent 6865 4884
IN IP4 85.15.7.19..s=SIP Call..c=IN IP4 85.15.7.19..t=0 0..m=audio 16400 R
TP/AVP 18 103..c=IN IP4 85.15.7.19..a=rtpmap:18 G729/8000..a=fmtp:18 annexb
=no..a=rtpmap:103 telephone-event/8000..a=fmtp:103 0-15..
#
U 85.15.7.18:5060 -> 192.168.11.102:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 192.168.11.102:5060;branch=z9hG4bK10145..F
rom: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..To: 0098146 <si
p:0098146@shatel.ir>;tag=9A65C-1F0E..Date: Fri, 01 Mar 2002 00:10:32 GMT..C
all-ID: 32268@192.168.11.102..Server: Cisco-SIPGateway/IOS-12.x..CSeq: 101
INVITE..Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBS
CRIBE, NOTIFY, INFO, UPDATE, REGISTER..Allow-Events: telephone-event..Conta
ct: sip:0098146@85.15.7.19:5060..Record-Route: <sip:85.15.7.18;ftag=analo
g-sip28734;lr=on>..Content-Type: application/sdp..Content-Length: 252....v=
0..o=CiscoSystemsSIP-GW-UserAgent 6865 4884 IN IP4 85.15.7.19..s=SIP Call..
c=IN IP4 85.15.7.19..t=0 0..m=audio 16400 RTP/AVP 18 103..c=IN IP4 85.15.7.
19..a=rtpmap:18 G729/8000..a=fmtp:18 annexb=no..a=rtpmap:103 telephone-even
t/8000..a=fmtp:103 0-15..
#
U 192.168.11.102:5060 -> 85.15.7.18:5060
ACK sip:85.15.7.18;ftag=analog-sip28734;lr SIP/2.0..Via: SIP/2.0/UDP 192.16
8.11.102:5060;branch=z9hG4bK1701..To: 0098146 sip:0098146@shatel.ir;tag=9
A65C-1F0E..From: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..Cal
l-ID: 32268@192.168.11.102..CSeq: 101 ACK..Route:sip:0098146@shatel.ir..C
ontact: sip:102@192.168.11.102:5060..Max-Forwards: 70..Content-Length: 0.
...
#
U 85.15.7.19:5060 -> 85.15.7.18:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 85.15.7.18;branch=0,SIP/2.0/UDP 192.168.11
.102:5060;branch=z9hG4bK10145..From: 102@shatel.ir sip:102@shatel.ir;tag=
analog-sip28734..To: 0098146 sip:0098146@shatel.ir;tag=9A65C-1F0E..Date:
Fri, 01 Mar 2002 00:10:32 GMT..Call-ID: 32268@192.168.11.102..Server: Cisco
-SIPGateway/IOS-12.x..CSeq: 101 INVITE..Allow: INVITE, OPTIONS, BYE, CANCEL
, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTER..Allo
w-Events: telephone-event..Contact: sip:0098146@85.15.7.19:5060..Record-R
oute: sip:85.15.7.18;ftag=analog-sip28734;lr=on..Content-Type: applicatio
n/sdp..Content-Length: 252....v=0..o=CiscoSystemsSIP-GW-UserAgent 6865 4884
IN IP4 85.15.7.19..s=SIP Call..c=IN IP4 85.15.7.19..t=0 0..m=audio 16400 R
TP/AVP 18 103..c=IN IP4 85.15.7.19..a=rtpmap:18 G729/8000..a=fmtp:18 annexb
=no..a=rtpmap:103 telephone-event/8000..a=fmtp:103 0-15..
#
U 85.15.7.18:5060 -> 192.168.11.102:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 192.168.11.102:5060;branch=z9hG4bK10145..F
rom: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..To: 0098146 <si
p:0098146@shatel.ir>;tag=9A65C-1F0E..Date: Fri, 01 Mar 2002 00:10:32 GMT..C
all-ID: 32268@192.168.11.102..Server: Cisco-SIPGateway/IOS-12.x..CSeq: 101
INVITE..Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBS
CRIBE, NOTIFY, INFO, UPDATE, REGISTER..Allow-Events: telephone-event..Conta
ct: sip:0098146@85.15.7.19:5060..Record-Route: <sip:85.15.7.18;ftag=analo
g-sip28734;lr=on>..Content-Type: application/sdp..Content-Length: 252....v=
0..o=CiscoSystemsSIP-GW-UserAgent 6865 4884 IN IP4 85.15.7.19..s=SIP Call..
c=IN IP4 85.15.7.19..t=0 0..m=audio 16400 RTP/AVP 18 103..c=IN IP4 85.15.7.
19..a=rtpmap:18 G729/8000..a=fmtp:18 annexb=no..a=rtpmap:103 telephone-even
t/8000..a=fmtp:103 0-15..
#
U 192.168.11.102:5060 -> 85.15.7.18:5060
ACK sip:85.15.7.18;ftag=analog-sip28734;lr SIP/2.0..Via: SIP/2.0/UDP 192.16
8.11.102:5060;branch=z9hG4bK15365..To: 0098146 sip:0098146@shatel.ir;tag=
9A65C-1F0E..From: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..Ca
ll-ID: 32268@192.168.11.102..CSeq: 101 ACK..Route:sip:0098146@shatel.ir..
Contact: sip:102@192.168.11.102:5060..Max-Forwards: 70..Content-Length: 0
....
#
U 85.15.7.19:5060 -> 85.15.7.18:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 85.15.7.18;branch=0,SIP/2.0/UDP 192.168.11
.102:5060;branch=z9hG4bK10145..From: 102@shatel.ir sip:102@shatel.ir;tag=
analog-sip28734..To: 0098146 sip:0098146@shatel.ir;tag=9A65C-1F0E..Date:
Fri, 01 Mar 2002 00:10:32 GMT..Call-ID: 32268@192.168.11.102..Server: Cisco
-SIPGateway/IOS-12.x..CSeq: 101 INVITE..Allow: INVITE, OPTIONS, BYE, CANCEL
, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTER..Allo
w-Events: telephone-event..Contact: sip:0098146@85.15.7.19:5060..Record-R
oute: sip:85.15.7.18;ftag=analog-sip28734;lr=on..Content-Type: applicatio
n/sdp..Content-Length: 252....v=0..o=CiscoSystemsSIP-GW-UserAgent 6865 4884
IN IP4 85.15.7.19..s=SIP Call..c=IN IP4 85.15.7.19..t=0 0..m=audio 16400 R
TP/AVP 18 103..c=IN IP4 85.15.7.19..a=rtpmap:18 G729/8000..a=fmtp:18 annexb
=no..a=rtpmap:103 telephone-event/8000..a=fmtp:103 0-15..
#
U 85.15.7.18:5060 -> 192.168.11.102:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 192.168.11.102:5060;branch=z9hG4bK10145..F
rom: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..To: 0098146 <si
p:0098146@shatel.ir>;tag=9A65C-1F0E..Date: Fri, 01 Mar 2002 00:10:32 GMT..C
all-ID: 32268@192.168.11.102..Server: Cisco-SIPGateway/IOS-12.x..CSeq: 101
INVITE..Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBS
CRIBE, NOTIFY, INFO, UPDATE, REGISTER..Allow-Events: telephone-event..Conta
ct: sip:0098146@85.15.7.19:5060..Record-Route: <sip:85.15.7.18;ftag=analo
g-sip28734;lr=on>..Content-Type: application/sdp..Content-Length: 252....v=
0..o=CiscoSystemsSIP-GW-UserAgent 6865 4884 IN IP4 85.15.7.19..s=SIP Call..
c=IN IP4 85.15.7.19..t=0 0..m=audio 16400 RTP/AVP 18 103..c=IN IP4 85.15.7.
19..a=rtpmap:18 G729/8000..a=fmtp:18 annexb=no..a=rtpmap:103 telephone-even
t/8000..a=fmtp:103 0-15..
#
U 192.168.11.102:5060 -> 85.15.7.18:5060
ACK sip:85.15.7.18;ftag=analog-sip28734;lr SIP/2.0..Via: SIP/2.0/UDP 192.16
8.11.102:5060;branch=z9hG4bK22111..To: 0098146 sip:0098146@shatel.ir;tag=
9A65C-1F0E..From: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..Ca
ll-ID: 32268@192.168.11.102..CSeq: 101 ACK..Route:sip:0098146@shatel.ir..
Contact: sip:102@192.168.11.102:5060..Max-Forwards: 70..Content-Length: 0
....
#
U 85.15.7.19:5060 -> 85.15.7.18:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 85.15.7.18;branch=0,SIP/2.0/UDP 192.168.11
.102:5060;branch=z9hG4bK10145..From: 102@shatel.ir sip:102@shatel.ir;tag=
analog-sip28734..To: 0098146 sip:0098146@shatel.ir;tag=9A65C-1F0E..Date:
Fri, 01 Mar 2002 00:10:32 GMT..Call-ID: 32268@192.168.11.102..Server: Cisco
-SIPGateway/IOS-12.x..CSeq: 101 INVITE..Allow: INVITE, OPTIONS, BYE, CANCEL
, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTER..Allo
w-Events: telephone-event..Contact: sip:0098146@85.15.7.19:5060..Record-R
oute: sip:85.15.7.18;ftag=analog-sip28734;lr=on..Content-Type: applicatio
n/sdp..Content-Length: 252....v=0..o=CiscoSystemsSIP-GW-UserAgent 6865 4884
IN IP4 85.15.7.19..s=SIP Call..c=IN IP4 85.15.7.19..t=0 0..m=audio 16400 R
TP/AVP 18 103..c=IN IP4 85.15.7.19..a=rtpmap:18 G729/8000..a=fmtp:18 annexb
=no..a=rtpmap:103 telephone-event/8000..a=fmtp:103 0-15..
#
U 85.15.7.18:5060 -> 192.168.11.102:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 192.168.11.102:5060;branch=z9hG4bK10145..F
rom: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..To: 0098146 <si
p:0098146@shatel.ir>;tag=9A65C-1F0E..Date: Fri, 01 Mar 2002 00:10:32 GMT..C
all-ID: 32268@192.168.11.102..Server: Cisco-SIPGateway/IOS-12.x..CSeq: 101
INVITE..Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBS
CRIBE, NOTIFY, INFO, UPDATE, REGISTER..Allow-Events: telephone-event..Conta
ct: sip:0098146@85.15.7.19:5060..Record-Route: <sip:85.15.7.18;ftag=analo
g-sip28734;lr=on>..Content-Type: application/sdp..Content-Length: 252....v=
0..o=CiscoSystemsSIP-GW-UserAgent 6865 4884 IN IP4 85.15.7.19..s=SIP Call..
c=IN IP4 85.15.7.19..t=0 0..m=audio 16400 RTP/AVP 18 103..c=IN IP4 85.15.7.
19..a=rtpmap:18 G729/8000..a=fmtp:18 annexb=no..a=rtpmap:103 telephone-even
t/8000..a=fmtp:103 0-15..
#
U 192.168.11.102:5060 -> 85.15.7.18:5060
ACK sip:85.15.7.18;ftag=analog-sip28734;lr SIP/2.0..Via: SIP/2.0/UDP 192.16
8.11.102:5060;branch=z9hG4bK2061..To: 0098146 sip:0098146@shatel.ir;tag=9
A65C-1F0E..From: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..Cal
l-ID: 32268@192.168.11.102..CSeq: 101 ACK..Route:sip:0098146@shatel.ir..C
ontact: sip:102@192.168.11.102:5060..Max-Forwards: 70..Content-Length: 0.
...
#
U 85.15.7.19:55584 -> 85.15.7.18:5060
BYE sip:102@192.168.11.102:5060 SIP/2.0..Via: SIP/2.0/UDP 85.15.7.19:5060;
branch=z9hG4bK11BD8..From: 0098146 sip:0098146@shatel.ir;tag=9A65C-1F0E..
To: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..Date: Fri, 01 Ma
r 2002 00:10:32 GMT..Call-ID: 32268@192.168.11.102..User-Agent: Cisco-SIPGa
teway/IOS-12.x..Max-Forwards: 70..Route: <sip:85.15.7.18;ftag=analog-sip287
34;lr=on>..Timestamp: 1014941453..CSeq: 101 BYE..Content-Length: 0....
#
U 85.15.7.18:5060 -> 192.168.11.102:5060
BYE sip:102@192.168.11.102:5060 SIP/2.0..Record-Route: <sip:85.15.7.18;ftag
=9A65C-1F0E;lr=on>..Via: SIP/2.0/UDP 85.15.7.18;branch=z9hG4bK6b5f.4db3aed2
.0..Via: SIP/2.0/UDP 85.15.7.19:5060;branch=z9hG4bK11BD8..From: 0098146 <s
ip:0098146@shatel.ir>;tag=9A65C-1F0E..To: 102@shatel.ir sip:102@shatel.ir
;tag=analog-sip28734..Date: Fri, 01 Mar 2002 00:10:32 GMT..Call-ID: 32268@1
92.168.11.102..User-Agent: Cisco-SIPGateway/IOS-12.x..Max-Forwards: 69..Tim
estamp: 1014941453..CSeq: 101 BYE..Content-Length: 0..P-hint: rr-enforced..
..
#
U 192.168.11.102:5060 -> 85.15.7.18:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 85.15.7.18;branch=z9hG4bK6b5f.4db3aed2.0,S
IP/2.0/UDP 85.15.7.19:5060;branch=z9hG4bK11BD8..To: 102@shatel.ir <sip:102@
shatel.ir>;tag=analog-sip28734..From: 0098146 sip:0098146@shatel.ir;tag=9
A65C-1F0E..Call-ID: 32268@192.168.11.102..CSeq: 101 BYE..Record-Route:<sip:
85.15.7.18;ftag=9A65C-1F0E;lr>..Content-Length: 0....
#
U 85.15.7.18:5060 -> 85.15.7.19:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 85.15.7.19:5060;branch=z9hG4bK11BD8..To: 1
02@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..From: 0098146 <sip:00
98146@shatel.ir>;tag=9A65C-1F0E..Call-ID: 32268@192.168.11.102..CSeq: 101 B
YE..Record-Route:sip:85.15.7.18;ftag=9A65C-1F0E;lr..Content-Length: 0....
#
U 85.15.7.18:5060 -> 192.168.11.102:5060
SIP/2.0 408 Request Timeout..Via: SIP/2.0/UDP 192.168.11.102:5060;branch=z9
hG4bK10145..To: 0098146 sip:0098146@shatel.ir;tag=3d932da19f2bc0936ad76a2
d09ced739-edc2..From: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734
..Call-ID: 32268@192.168.11.102..CSeq: 101 INVITE..Server: OpenSer (1.0.1 (
i386/linux))..Content-Length: 0..Warning: 392 85.15.7.18:5060 "Noisy feedba
ck tells: pid=6517 req_src_ip=192.168.11.102 req_src_port=5060 in_uri=sip:
0098146@shatel.ir out_uri=sip:0098146@shatel.ir via_cnt==0"....
#
U 192.168.11.102:5060 -> 85.15.7.18:5060
ACK sip:0098146@shatel.ir SIP/2.0..Via: SIP/2.0/UDP 192.168.11.102:5060;bra
nch=z9hG4bK10145..To: 0098146 sip:0098146@shatel.ir;tag=3d932da19f2bc0936
ad76a2d09ced739-edc2..From: 102@shatel.ir sip:102@shatel.ir;tag=analog-si
p28734..Call-ID: 32268@192.168.11.102..CSeq: 101 ACK..Content-Length: 0....
#
U 85.15.7.18:5060 -> 85.15.7.19:5060
ACK sip:0098146@shatel.ir SIP/2.0..Max-Forwards: 10..Record-Route: <sip:85.
15.7.18;ftag=analog-sip28734;lr=on>..Via: SIP/2.0/UDP 85.15.7.18;branch=0..
Via: SIP/2.0/UDP 192.168.11.102:5060;branch=z9hG4bK10145..To: 0098146 <sip:
0098146@shatel.ir>;tag=3d932da19f2bc0936ad76a2d09ced739-edc2..From: 102@sha
tel.ir sip:102@shatel.ir;tag=analog-sip28734..Call-ID: 32268@192.168.11.1
02..CSeq: 101 ACK..Content-Length: 0....
exit
Hi!
next time, please use the "-W byline" switch of ngrep.
The problem is the ACK - it is totally wrong - the request URI and the Route header is bad
If your client is RFC3261 complient, it should put the URI from the Contact of the 200 OK into the request URI, not the URI of the Record-Route header (this is the old SIP RFC behaviour).
Also if your client uses the old way (strict router), it has to put the complete Contact URI of the 200 Ok into the Route header.
Which client are you use?
regards klaus
Hamid Ali Asgari wrote:
Hi,
Here comes the dump from ngrep for a sample call.
Any idea what’s wrong?
Thanks,
Hamid
input: 102-to-C3660.sip.cap
#
U 192.168.11.102:5060 -> 85.15.7.18:5060
INVITE sip:0098146@shatel.ir SIP/2.0..Via: SIP/2.0/UDP 192.168.11.102:5060;
branch=z9hG4bK10145..To: 0098146 sip:0098146@shatel.ir..From: 102@shatel.
ir sip:102@shatel.ir;tag=analog-sip28734..Call-ID: 32268@192.168.11.102..
CSeq: 101 INVITE..Contact: sip:102@192.168.11.102:5060..Max-Forwards: 70.
.Allow: INVITE, BYE, CANCEL, ACK, OPTIONS, REFER, NOTIFY..Supported: replac
es..Content-Type: application/sdp..Content-Length: 251....v=0..o=adiPhone 3
2268 32268 IN IP4 192.168.11.102..s=Phone Call..c=IN IP4 192.168.11.102..t=
0 0..m=audio 6000 RTP/AVP 18 0 8 103..a=rtpmap:18 G729/8000/1..a=rtpmap:0 P
CMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:103 telephone-event/8000..a=fmtp:1
03 0-15..
#
U 85.15.7.18:5060 -> 85.15.7.19:5060
INVITE sip:0098146@shatel.ir SIP/2.0..Record-Route: <sip:85.15.7.18;ftag=an
alog-sip28734;lr=on>..Via: SIP/2.0/UDP 85.15.7.18;branch=0..Via: SIP/2.0/UD
P 192.168.11.102:5060;branch=z9hG4bK10145..To: 0098146 <sip:0098146@shatel.
ir>..From: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..Call-ID:
32268@192.168.11.102..CSeq: 101 INVITE..Contact: <sip:102@192.168.11.102:50
60>..Max-Forwards: 69..Allow: INVITE, BYE, CANCEL, ACK, OPTIONS, REFER, NOT
IFY..Supported: replaces..Content-Type: application/sdp..Content-Length: 25
1....v=0..o=adiPhone 32268 32268 IN IP4 192.168.11.102..s=Phone Call..c=IN
IP4 192.168.11.102..t=0 0..m=audio 6000 RTP/AVP 18 0 8 103..a=rtpmap:18 G72
9/8000/1..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:103 telephon
e-event/8000..a=fmtp:103 0-15..
#
U 85.15.7.18:5060 -> 192.168.11.102:5060
SIP/2.0 100 trying -- your call is important to us..Via: SIP/2.0/UDP 192.16
8.11.102:5060;branch=z9hG4bK10145..To: 0098146 sip:0098146@shatel.ir..Fro
m: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..Call-ID: 32268@19
2.168.11.102..CSeq: 101 INVITE..Server: OpenSer (1.0.1 (i386/linux))..Conte
nt-Length: 0..Warning: 392 85.15.7.18:5060 "Noisy feedback tells: pid=6514
req_src_ip=192.168.11.102 req_src_port=5060 in_uri=sip:0098146@shatel.ir o
ut_uri=sip:0098146@shatel.ir via_cnt==1"....
#
U 85.15.7.19:5060 -> 85.15.7.18:5060
SIP/2.0 100 Trying..Via: SIP/2.0/UDP 85.15.7.18;branch=0,SIP/2.0/UDP 192.16
8.11.102:5060;branch=z9hG4bK10145..From: 102@shatel.ir sip:102@shatel.ir;
tag=analog-sip28734..To: 0098146 sip:0098146@shatel.ir;tag=9A65C-1F0E..Da
te: Fri, 01 Mar 2002 00:10:32 GMT..Call-ID: 32268@192.168.11.102..Server: C
isco-SIPGateway/IOS-12.x..CSeq: 101 INVITE..Allow-Events: telephone-event..
Content-Length: 0....
#
U 85.15.7.18:5060 -> 192.168.11.102:5060
SIP/2.0 100 Trying..Via: SIP/2.0/UDP 192.168.11.102:5060;branch=z9hG4bK1014
5..From: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..To: 0098146
sip:0098146@shatel.ir;tag=9A65C-1F0E..Date: Fri, 01 Mar 2002 00:10:32 GM
T..Call-ID: 32268@192.168.11.102..Server: Cisco-SIPGateway/IOS-12.x..CSeq:
101 INVITE..Allow-Events: telephone-event..Content-Length: 0....
#
U 85.15.7.19:5060 -> 85.15.7.18:5060
SIP/2.0 183 Session Progress..Via: SIP/2.0/UDP 85.15.7.18;branch=0,SIP/2.0/
UDP 192.168.11.102:5060;branch=z9hG4bK10145..From: 102@shatel.ir <sip:102@s
hatel.ir>;tag=analog-sip28734..To: 0098146 sip:0098146@shatel.ir;tag=9A65
C-1F0E..Date: Fri, 01 Mar 2002 00:10:32 GMT..Call-ID: 32268@192.168.11.102.
.Server: Cisco-SIPGateway/IOS-12.x..CSeq: 101 INVITE..Allow: INVITE, OPTION
S, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE,
REGISTER..Allow-Events: telephone-event..Contact: <sip:0098146@85.15.7.19:5
060>..Record-Route: sip:85.15.7.18;ftag=analog-sip28734;lr=on..Content-Di
sposition: session;handling=required..Content-Type: application/sdp..Conten
t-Length: 252....v=0..o=CiscoSystemsSIP-GW-UserAgent 6865 4884 IN IP4 85.15
.7.19..s=SIP Call..c=IN IP4 85.15.7.19..t=0 0..m=audio 16400 RTP/AVP 18 103
..c=IN IP4 85.15.7.19..a=rtpmap:18 G729/8000..a=fmtp:18 annexb=no..a=rtpmap
:103 telephone-event/8000..a=fmtp:103 0-15..
#
U 85.15.7.18:5060 -> 192.168.11.102:5060
SIP/2.0 183 Session Progress..Via: SIP/2.0/UDP 192.168.11.102:5060;branch=z
9hG4bK10145..From: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..T
o: 0098146 sip:0098146@shatel.ir;tag=9A65C-1F0E..Date: Fri, 01 Mar 2002 0
0:10:32 GMT..Call-ID: 32268@192.168.11.102..Server: Cisco-SIPGateway/IOS-12
.x..CSeq: 101 INVITE..Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COME
T, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTER..Allow-Events: telephon
e-event..Contact: sip:0098146@85.15.7.19:5060..Record-Route: <sip:85.15.7
.18;ftag=analog-sip28734;lr=on>..Content-Disposition: session;handling=requ
ired..Content-Type: application/sdp..Content-Length: 252....v=0..o=CiscoSys
temsSIP-GW-UserAgent 6865 4884 IN IP4 85.15.7.19..s=SIP Call..c=IN IP4 85.1
5.7.19..t=0 0..m=audio 16400 RTP/AVP 18 103..c=IN IP4 85.15.7.19..a=rtpmap:
18 G729/8000..a=fmtp:18 annexb=no..a=rtpmap:103 telephone-event/8000..a=fmt
p:103 0-15..
#
U 85.15.7.19:5060 -> 85.15.7.18:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 85.15.7.18;branch=0,SIP/2.0/UDP 192.168.11
.102:5060;branch=z9hG4bK10145..From: 102@shatel.ir sip:102@shatel.ir;tag=
analog-sip28734..To: 0098146 sip:0098146@shatel.ir;tag=9A65C-1F0E..Date:
Fri, 01 Mar 2002 00:10:32 GMT..Call-ID: 32268@192.168.11.102..Server: Cisco
-SIPGateway/IOS-12.x..CSeq: 101 INVITE..Allow: INVITE, OPTIONS, BYE, CANCEL
, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTER..Allo
w-Events: telephone-event..Contact: sip:0098146@85.15.7.19:5060..Record-R
oute: sip:85.15.7.18;ftag=analog-sip28734;lr=on..Content-Type: applicatio
n/sdp..Content-Length: 252....v=0..o=CiscoSystemsSIP-GW-UserAgent 6865 4884
IN IP4 85.15.7.19..s=SIP Call..c=IN IP4 85.15.7.19..t=0 0..m=audio 16400 R
TP/AVP 18 103..c=IN IP4 85.15.7.19..a=rtpmap:18 G729/8000..a=fmtp:18 annexb
=no..a=rtpmap:103 telephone-event/8000..a=fmtp:103 0-15..
#
U 85.15.7.18:5060 -> 192.168.11.102:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 192.168.11.102:5060;branch=z9hG4bK10145..F
rom: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..To: 0098146 <si
p:0098146@shatel.ir>;tag=9A65C-1F0E..Date: Fri, 01 Mar 2002 00:10:32 GMT..C
all-ID: 32268@192.168.11.102..Server: Cisco-SIPGateway/IOS-12.x..CSeq: 101
INVITE..Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBS
CRIBE, NOTIFY, INFO, UPDATE, REGISTER..Allow-Events: telephone-event..Conta
ct: sip:0098146@85.15.7.19:5060..Record-Route: <sip:85.15.7.18;ftag=analo
g-sip28734;lr=on>..Content-Type: application/sdp..Content-Length: 252....v=
0..o=CiscoSystemsSIP-GW-UserAgent 6865 4884 IN IP4 85.15.7.19..s=SIP Call..
c=IN IP4 85.15.7.19..t=0 0..m=audio 16400 RTP/AVP 18 103..c=IN IP4 85.15.7.
19..a=rtpmap:18 G729/8000..a=fmtp:18 annexb=no..a=rtpmap:103 telephone-even
t/8000..a=fmtp:103 0-15..
#
U 192.168.11.102:5060 -> 85.15.7.18:5060
ACK sip:85.15.7.18;ftag=analog-sip28734;lr SIP/2.0..Via: SIP/2.0/UDP 192.16
8.11.102:5060;branch=z9hG4bK9072..To: 0098146 sip:0098146@shatel.ir;tag=9
A65C-1F0E..From: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..Cal
l-ID: 32268@192.168.11.102..CSeq: 101 ACK..Route:sip:0098146@shatel.ir..C
ontact: sip:102@192.168.11.102:5060..Max-Forwards: 70..Content-Length: 0.
...
#
U 85.15.7.19:5060 -> 85.15.7.18:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 85.15.7.18;branch=0,SIP/2.0/UDP 192.168.11
.102:5060;branch=z9hG4bK10145..From: 102@shatel.ir sip:102@shatel.ir;tag=
analog-sip28734..To: 0098146 sip:0098146@shatel.ir;tag=9A65C-1F0E..Date:
Fri, 01 Mar 2002 00:10:32 GMT..Call-ID: 32268@192.168.11.102..Server: Cisco
-SIPGateway/IOS-12.x..CSeq: 101 INVITE..Allow: INVITE, OPTIONS, BYE, CANCEL
, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTER..Allo
w-Events: telephone-event..Contact: sip:0098146@85.15.7.19:5060..Record-R
oute: sip:85.15.7.18;ftag=analog-sip28734;lr=on..Content-Type: applicatio
n/sdp..Content-Length: 252....v=0..o=CiscoSystemsSIP-GW-UserAgent 6865 4884
IN IP4 85.15.7.19..s=SIP Call..c=IN IP4 85.15.7.19..t=0 0..m=audio 16400 R
TP/AVP 18 103..c=IN IP4 85.15.7.19..a=rtpmap:18 G729/8000..a=fmtp:18 annexb
=no..a=rtpmap:103 telephone-event/8000..a=fmtp:103 0-15..
#
U 85.15.7.18:5060 -> 192.168.11.102:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 192.168.11.102:5060;branch=z9hG4bK10145..F
rom: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..To: 0098146 <si
p:0098146@shatel.ir>;tag=9A65C-1F0E..Date: Fri, 01 Mar 2002 00:10:32 GMT..C
all-ID: 32268@192.168.11.102..Server: Cisco-SIPGateway/IOS-12.x..CSeq: 101
INVITE..Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBS
CRIBE, NOTIFY, INFO, UPDATE, REGISTER..Allow-Events: telephone-event..Conta
ct: sip:0098146@85.15.7.19:5060..Record-Route: <sip:85.15.7.18;ftag=analo
g-sip28734;lr=on>..Content-Type: application/sdp..Content-Length: 252....v=
0..o=CiscoSystemsSIP-GW-UserAgent 6865 4884 IN IP4 85.15.7.19..s=SIP Call..
c=IN IP4 85.15.7.19..t=0 0..m=audio 16400 RTP/AVP 18 103..c=IN IP4 85.15.7.
19..a=rtpmap:18 G729/8000..a=fmtp:18 annexb=no..a=rtpmap:103 telephone-even
t/8000..a=fmtp:103 0-15..
#
U 192.168.11.102:5060 -> 85.15.7.18:5060
ACK sip:85.15.7.18;ftag=analog-sip28734;lr SIP/2.0..Via: SIP/2.0/UDP 192.16
8.11.102:5060;branch=z9hG4bK10994..To: 0098146 sip:0098146@shatel.ir;tag=
9A65C-1F0E..From: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..Ca
ll-ID: 32268@192.168.11.102..CSeq: 101 ACK..Route:sip:0098146@shatel.ir..
Contact: sip:102@192.168.11.102:5060..Max-Forwards: 70..Content-Length: 0
....
#
U 85.15.7.19:5060 -> 85.15.7.18:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 85.15.7.18;branch=0,SIP/2.0/UDP 192.168.11
.102:5060;branch=z9hG4bK10145..From: 102@shatel.ir sip:102@shatel.ir;tag=
analog-sip28734..To: 0098146 sip:0098146@shatel.ir;tag=9A65C-1F0E..Date:
Fri, 01 Mar 2002 00:10:32 GMT..Call-ID: 32268@192.168.11.102..Server: Cisco
-SIPGateway/IOS-12.x..CSeq: 101 INVITE..Allow: INVITE, OPTIONS, BYE, CANCEL
, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTER..Allo
w-Events: telephone-event..Contact: sip:0098146@85.15.7.19:5060..Record-R
oute: sip:85.15.7.18;ftag=analog-sip28734;lr=on..Content-Type: applicatio
n/sdp..Content-Length: 252....v=0..o=CiscoSystemsSIP-GW-UserAgent 6865 4884
IN IP4 85.15.7.19..s=SIP Call..c=IN IP4 85.15.7.19..t=0 0..m=audio 16400 R
TP/AVP 18 103..c=IN IP4 85.15.7.19..a=rtpmap:18 G729/8000..a=fmtp:18 annexb
=no..a=rtpmap:103 telephone-event/8000..a=fmtp:103 0-15..
#
U 85.15.7.18:5060 -> 192.168.11.102:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 192.168.11.102:5060;branch=z9hG4bK10145..F
rom: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..To: 0098146 <si
p:0098146@shatel.ir>;tag=9A65C-1F0E..Date: Fri, 01 Mar 2002 00:10:32 GMT..C
all-ID: 32268@192.168.11.102..Server: Cisco-SIPGateway/IOS-12.x..CSeq: 101
INVITE..Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBS
CRIBE, NOTIFY, INFO, UPDATE, REGISTER..Allow-Events: telephone-event..Conta
ct: sip:0098146@85.15.7.19:5060..Record-Route: <sip:85.15.7.18;ftag=analo
g-sip28734;lr=on>..Content-Type: application/sdp..Content-Length: 252....v=
0..o=CiscoSystemsSIP-GW-UserAgent 6865 4884 IN IP4 85.15.7.19..s=SIP Call..
c=IN IP4 85.15.7.19..t=0 0..m=audio 16400 RTP/AVP 18 103..c=IN IP4 85.15.7.
19..a=rtpmap:18 G729/8000..a=fmtp:18 annexb=no..a=rtpmap:103 telephone-even
t/8000..a=fmtp:103 0-15..
#
U 192.168.11.102:5060 -> 85.15.7.18:5060
ACK sip:85.15.7.18;ftag=analog-sip28734;lr SIP/2.0..Via: SIP/2.0/UDP 192.16
8.11.102:5060;branch=z9hG4bK24833..To: 0098146 sip:0098146@shatel.ir;tag=
9A65C-1F0E..From: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..Ca
ll-ID: 32268@192.168.11.102..CSeq: 101 ACK..Route:sip:0098146@shatel.ir..
Contact: sip:102@192.168.11.102:5060..Max-Forwards: 70..Content-Length: 0
....
#
U 85.15.7.19:5060 -> 85.15.7.18:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 85.15.7.18;branch=0,SIP/2.0/UDP 192.168.11
.102:5060;branch=z9hG4bK10145..From: 102@shatel.ir sip:102@shatel.ir;tag=
analog-sip28734..To: 0098146 sip:0098146@shatel.ir;tag=9A65C-1F0E..Date:
Fri, 01 Mar 2002 00:10:32 GMT..Call-ID: 32268@192.168.11.102..Server: Cisco
-SIPGateway/IOS-12.x..CSeq: 101 INVITE..Allow: INVITE, OPTIONS, BYE, CANCEL
, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTER..Allo
w-Events: telephone-event..Contact: sip:0098146@85.15.7.19:5060..Record-R
oute: sip:85.15.7.18;ftag=analog-sip28734;lr=on..Content-Type: applicatio
n/sdp..Content-Length: 252....v=0..o=CiscoSystemsSIP-GW-UserAgent 6865 4884
IN IP4 85.15.7.19..s=SIP Call..c=IN IP4 85.15.7.19..t=0 0..m=audio 16400 R
TP/AVP 18 103..c=IN IP4 85.15.7.19..a=rtpmap:18 G729/8000..a=fmtp:18 annexb
=no..a=rtpmap:103 telephone-event/8000..a=fmtp:103 0-15..
#
U 85.15.7.18:5060 -> 192.168.11.102:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 192.168.11.102:5060;branch=z9hG4bK10145..F
rom: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..To: 0098146 <si
p:0098146@shatel.ir>;tag=9A65C-1F0E..Date: Fri, 01 Mar 2002 00:10:32 GMT..C
all-ID: 32268@192.168.11.102..Server: Cisco-SIPGateway/IOS-12.x..CSeq: 101
INVITE..Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBS
CRIBE, NOTIFY, INFO, UPDATE, REGISTER..Allow-Events: telephone-event..Conta
ct: sip:0098146@85.15.7.19:5060..Record-Route: <sip:85.15.7.18;ftag=analo
g-sip28734;lr=on>..Content-Type: application/sdp..Content-Length: 252....v=
0..o=CiscoSystemsSIP-GW-UserAgent 6865 4884 IN IP4 85.15.7.19..s=SIP Call..
c=IN IP4 85.15.7.19..t=0 0..m=audio 16400 RTP/AVP 18 103..c=IN IP4 85.15.7.
19..a=rtpmap:18 G729/8000..a=fmtp:18 annexb=no..a=rtpmap:103 telephone-even
t/8000..a=fmtp:103 0-15..
#
U 192.168.11.102:5060 -> 85.15.7.18:5060
ACK sip:85.15.7.18;ftag=analog-sip28734;lr SIP/2.0..Via: SIP/2.0/UDP 192.16
8.11.102:5060;branch=z9hG4bK1701..To: 0098146 sip:0098146@shatel.ir;tag=9
A65C-1F0E..From: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..Cal
l-ID: 32268@192.168.11.102..CSeq: 101 ACK..Route:sip:0098146@shatel.ir..C
ontact: sip:102@192.168.11.102:5060..Max-Forwards: 70..Content-Length: 0.
...
#
U 85.15.7.19:5060 -> 85.15.7.18:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 85.15.7.18;branch=0,SIP/2.0/UDP 192.168.11
.102:5060;branch=z9hG4bK10145..From: 102@shatel.ir sip:102@shatel.ir;tag=
analog-sip28734..To: 0098146 sip:0098146@shatel.ir;tag=9A65C-1F0E..Date:
Fri, 01 Mar 2002 00:10:32 GMT..Call-ID: 32268@192.168.11.102..Server: Cisco
-SIPGateway/IOS-12.x..CSeq: 101 INVITE..Allow: INVITE, OPTIONS, BYE, CANCEL
, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTER..Allo
w-Events: telephone-event..Contact: sip:0098146@85.15.7.19:5060..Record-R
oute: sip:85.15.7.18;ftag=analog-sip28734;lr=on..Content-Type: applicatio
n/sdp..Content-Length: 252....v=0..o=CiscoSystemsSIP-GW-UserAgent 6865 4884
IN IP4 85.15.7.19..s=SIP Call..c=IN IP4 85.15.7.19..t=0 0..m=audio 16400 R
TP/AVP 18 103..c=IN IP4 85.15.7.19..a=rtpmap:18 G729/8000..a=fmtp:18 annexb
=no..a=rtpmap:103 telephone-event/8000..a=fmtp:103 0-15..
#
U 85.15.7.18:5060 -> 192.168.11.102:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 192.168.11.102:5060;branch=z9hG4bK10145..F
rom: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..To: 0098146 <si
p:0098146@shatel.ir>;tag=9A65C-1F0E..Date: Fri, 01 Mar 2002 00:10:32 GMT..C
all-ID: 32268@192.168.11.102..Server: Cisco-SIPGateway/IOS-12.x..CSeq: 101
INVITE..Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBS
CRIBE, NOTIFY, INFO, UPDATE, REGISTER..Allow-Events: telephone-event..Conta
ct: sip:0098146@85.15.7.19:5060..Record-Route: <sip:85.15.7.18;ftag=analo
g-sip28734;lr=on>..Content-Type: application/sdp..Content-Length: 252....v=
0..o=CiscoSystemsSIP-GW-UserAgent 6865 4884 IN IP4 85.15.7.19..s=SIP Call..
c=IN IP4 85.15.7.19..t=0 0..m=audio 16400 RTP/AVP 18 103..c=IN IP4 85.15.7.
19..a=rtpmap:18 G729/8000..a=fmtp:18 annexb=no..a=rtpmap:103 telephone-even
t/8000..a=fmtp:103 0-15..
#
U 192.168.11.102:5060 -> 85.15.7.18:5060
ACK sip:85.15.7.18;ftag=analog-sip28734;lr SIP/2.0..Via: SIP/2.0/UDP 192.16
8.11.102:5060;branch=z9hG4bK15365..To: 0098146 sip:0098146@shatel.ir;tag=
9A65C-1F0E..From: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..Ca
ll-ID: 32268@192.168.11.102..CSeq: 101 ACK..Route:sip:0098146@shatel.ir..
Contact: sip:102@192.168.11.102:5060..Max-Forwards: 70..Content-Length: 0
....
#
U 85.15.7.19:5060 -> 85.15.7.18:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 85.15.7.18;branch=0,SIP/2.0/UDP 192.168.11
.102:5060;branch=z9hG4bK10145..From: 102@shatel.ir sip:102@shatel.ir;tag=
analog-sip28734..To: 0098146 sip:0098146@shatel.ir;tag=9A65C-1F0E..Date:
Fri, 01 Mar 2002 00:10:32 GMT..Call-ID: 32268@192.168.11.102..Server: Cisco
-SIPGateway/IOS-12.x..CSeq: 101 INVITE..Allow: INVITE, OPTIONS, BYE, CANCEL
, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTER..Allo
w-Events: telephone-event..Contact: sip:0098146@85.15.7.19:5060..Record-R
oute: sip:85.15.7.18;ftag=analog-sip28734;lr=on..Content-Type: applicatio
n/sdp..Content-Length: 252....v=0..o=CiscoSystemsSIP-GW-UserAgent 6865 4884
IN IP4 85.15.7.19..s=SIP Call..c=IN IP4 85.15.7.19..t=0 0..m=audio 16400 R
TP/AVP 18 103..c=IN IP4 85.15.7.19..a=rtpmap:18 G729/8000..a=fmtp:18 annexb
=no..a=rtpmap:103 telephone-event/8000..a=fmtp:103 0-15..
#
U 85.15.7.18:5060 -> 192.168.11.102:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 192.168.11.102:5060;branch=z9hG4bK10145..F
rom: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..To: 0098146 <si
p:0098146@shatel.ir>;tag=9A65C-1F0E..Date: Fri, 01 Mar 2002 00:10:32 GMT..C
all-ID: 32268@192.168.11.102..Server: Cisco-SIPGateway/IOS-12.x..CSeq: 101
INVITE..Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBS
CRIBE, NOTIFY, INFO, UPDATE, REGISTER..Allow-Events: telephone-event..Conta
ct: sip:0098146@85.15.7.19:5060..Record-Route: <sip:85.15.7.18;ftag=analo
g-sip28734;lr=on>..Content-Type: application/sdp..Content-Length: 252....v=
0..o=CiscoSystemsSIP-GW-UserAgent 6865 4884 IN IP4 85.15.7.19..s=SIP Call..
c=IN IP4 85.15.7.19..t=0 0..m=audio 16400 RTP/AVP 18 103..c=IN IP4 85.15.7.
19..a=rtpmap:18 G729/8000..a=fmtp:18 annexb=no..a=rtpmap:103 telephone-even
t/8000..a=fmtp:103 0-15..
#
U 192.168.11.102:5060 -> 85.15.7.18:5060
ACK sip:85.15.7.18;ftag=analog-sip28734;lr SIP/2.0..Via: SIP/2.0/UDP 192.16
8.11.102:5060;branch=z9hG4bK22111..To: 0098146 sip:0098146@shatel.ir;tag=
9A65C-1F0E..From: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..Ca
ll-ID: 32268@192.168.11.102..CSeq: 101 ACK..Route:sip:0098146@shatel.ir..
Contact: sip:102@192.168.11.102:5060..Max-Forwards: 70..Content-Length: 0
....
#
U 85.15.7.19:5060 -> 85.15.7.18:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 85.15.7.18;branch=0,SIP/2.0/UDP 192.168.11
.102:5060;branch=z9hG4bK10145..From: 102@shatel.ir sip:102@shatel.ir;tag=
analog-sip28734..To: 0098146 sip:0098146@shatel.ir;tag=9A65C-1F0E..Date:
Fri, 01 Mar 2002 00:10:32 GMT..Call-ID: 32268@192.168.11.102..Server: Cisco
-SIPGateway/IOS-12.x..CSeq: 101 INVITE..Allow: INVITE, OPTIONS, BYE, CANCEL
, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTER..Allo
w-Events: telephone-event..Contact: sip:0098146@85.15.7.19:5060..Record-R
oute: sip:85.15.7.18;ftag=analog-sip28734;lr=on..Content-Type: applicatio
n/sdp..Content-Length: 252....v=0..o=CiscoSystemsSIP-GW-UserAgent 6865 4884
IN IP4 85.15.7.19..s=SIP Call..c=IN IP4 85.15.7.19..t=0 0..m=audio 16400 R
TP/AVP 18 103..c=IN IP4 85.15.7.19..a=rtpmap:18 G729/8000..a=fmtp:18 annexb
=no..a=rtpmap:103 telephone-event/8000..a=fmtp:103 0-15..
#
U 85.15.7.18:5060 -> 192.168.11.102:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 192.168.11.102:5060;branch=z9hG4bK10145..F
rom: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..To: 0098146 <si
p:0098146@shatel.ir>;tag=9A65C-1F0E..Date: Fri, 01 Mar 2002 00:10:32 GMT..C
all-ID: 32268@192.168.11.102..Server: Cisco-SIPGateway/IOS-12.x..CSeq: 101
INVITE..Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBS
CRIBE, NOTIFY, INFO, UPDATE, REGISTER..Allow-Events: telephone-event..Conta
ct: sip:0098146@85.15.7.19:5060..Record-Route: <sip:85.15.7.18;ftag=analo
g-sip28734;lr=on>..Content-Type: application/sdp..Content-Length: 252....v=
0..o=CiscoSystemsSIP-GW-UserAgent 6865 4884 IN IP4 85.15.7.19..s=SIP Call..
c=IN IP4 85.15.7.19..t=0 0..m=audio 16400 RTP/AVP 18 103..c=IN IP4 85.15.7.
19..a=rtpmap:18 G729/8000..a=fmtp:18 annexb=no..a=rtpmap:103 telephone-even
t/8000..a=fmtp:103 0-15..
#
U 192.168.11.102:5060 -> 85.15.7.18:5060
ACK sip:85.15.7.18;ftag=analog-sip28734;lr SIP/2.0..Via: SIP/2.0/UDP 192.16
8.11.102:5060;branch=z9hG4bK2061..To: 0098146 sip:0098146@shatel.ir;tag=9
A65C-1F0E..From: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..Cal
l-ID: 32268@192.168.11.102..CSeq: 101 ACK..Route:sip:0098146@shatel.ir..C
ontact: sip:102@192.168.11.102:5060..Max-Forwards: 70..Content-Length: 0.
...
#
U 85.15.7.19:55584 -> 85.15.7.18:5060
BYE sip:102@192.168.11.102:5060 SIP/2.0..Via: SIP/2.0/UDP 85.15.7.19:5060;
branch=z9hG4bK11BD8..From: 0098146 sip:0098146@shatel.ir;tag=9A65C-1F0E..
To: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..Date: Fri, 01 Ma
r 2002 00:10:32 GMT..Call-ID: 32268@192.168.11.102..User-Agent: Cisco-SIPGa
teway/IOS-12.x..Max-Forwards: 70..Route: <sip:85.15.7.18;ftag=analog-sip287
34;lr=on>..Timestamp: 1014941453..CSeq: 101 BYE..Content-Length: 0....
#
U 85.15.7.18:5060 -> 192.168.11.102:5060
BYE sip:102@192.168.11.102:5060 SIP/2.0..Record-Route: <sip:85.15.7.18;ftag
=9A65C-1F0E;lr=on>..Via: SIP/2.0/UDP 85.15.7.18;branch=z9hG4bK6b5f.4db3aed2
.0..Via: SIP/2.0/UDP 85.15.7.19:5060;branch=z9hG4bK11BD8..From: 0098146 <s
ip:0098146@shatel.ir>;tag=9A65C-1F0E..To: 102@shatel.ir sip:102@shatel.ir
;tag=analog-sip28734..Date: Fri, 01 Mar 2002 00:10:32 GMT..Call-ID: 32268@1
92.168.11.102..User-Agent: Cisco-SIPGateway/IOS-12.x..Max-Forwards: 69..Tim
estamp: 1014941453..CSeq: 101 BYE..Content-Length: 0..P-hint: rr-enforced..
..
#
U 192.168.11.102:5060 -> 85.15.7.18:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 85.15.7.18;branch=z9hG4bK6b5f.4db3aed2.0,S
IP/2.0/UDP 85.15.7.19:5060;branch=z9hG4bK11BD8..To: 102@shatel.ir <sip:102@
shatel.ir>;tag=analog-sip28734..From: 0098146 sip:0098146@shatel.ir;tag=9
A65C-1F0E..Call-ID: 32268@192.168.11.102..CSeq: 101 BYE..Record-Route:<sip:
85.15.7.18;ftag=9A65C-1F0E;lr>..Content-Length: 0....
#
U 85.15.7.18:5060 -> 85.15.7.19:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 85.15.7.19:5060;branch=z9hG4bK11BD8..To: 1
02@shatel.ir sip:102@shatel.ir;tag=analog-sip28734..From: 0098146 <sip:00
98146@shatel.ir>;tag=9A65C-1F0E..Call-ID: 32268@192.168.11.102..CSeq: 101 B
YE..Record-Route:sip:85.15.7.18;ftag=9A65C-1F0E;lr..Content-Length: 0....
#
U 85.15.7.18:5060 -> 192.168.11.102:5060
SIP/2.0 408 Request Timeout..Via: SIP/2.0/UDP 192.168.11.102:5060;branch=z9
hG4bK10145..To: 0098146 sip:0098146@shatel.ir;tag=3d932da19f2bc0936ad76a2
d09ced739-edc2..From: 102@shatel.ir sip:102@shatel.ir;tag=analog-sip28734
..Call-ID: 32268@192.168.11.102..CSeq: 101 INVITE..Server: OpenSer (1.0.1 (
i386/linux))..Content-Length: 0..Warning: 392 85.15.7.18:5060 "Noisy feedba
ck tells: pid=6517 req_src_ip=192.168.11.102 req_src_port=5060 in_uri=sip:
0098146@shatel.ir out_uri=sip:0098146@shatel.ir via_cnt==0"....
#
U 192.168.11.102:5060 -> 85.15.7.18:5060
ACK sip:0098146@shatel.ir SIP/2.0..Via: SIP/2.0/UDP 192.168.11.102:5060;bra
nch=z9hG4bK10145..To: 0098146 sip:0098146@shatel.ir;tag=3d932da19f2bc0936
ad76a2d09ced739-edc2..From: 102@shatel.ir sip:102@shatel.ir;tag=analog-si
p28734..Call-ID: 32268@192.168.11.102..CSeq: 101 ACK..Content-Length: 0....
#
U 85.15.7.18:5060 -> 85.15.7.19:5060
ACK sip:0098146@shatel.ir SIP/2.0..Max-Forwards: 10..Record-Route: <sip:85.
15.7.18;ftag=analog-sip28734;lr=on>..Via: SIP/2.0/UDP 85.15.7.18;branch=0..
Via: SIP/2.0/UDP 192.168.11.102:5060;branch=z9hG4bK10145..To: 0098146 <sip:
0098146@shatel.ir>;tag=3d932da19f2bc0936ad76a2d09ced739-edc2..From: 102@sha
tel.ir sip:102@shatel.ir;tag=analog-sip28734..Call-ID: 32268@192.168.11.1
02..CSeq: 101 ACK..Content-Length: 0....
exit