Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Create a new article
282
Views
0
Helpful
0
Comments

VOIP communication problem

cn_gelare
Level 1
Level 1

‎10-22-2013 05:39 PM - edited ‎03-12-2019 10:05 AM

there is a HuaWei U2990 Communicated with Cisco 2821 throuth sip,here are sip message collected from 2821 router,

the problem is some Invite from U2990,Cisco 2821 did not give the correct response,anybody can give some suggestion?

please see the explain below which mark with color

Oct 22 12:03:54.498 HKT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:888001@192.168.1.1:5060;user=phone SIP/2.0
Via: SIP/2.0/UDP 192.168.2.27:5062;branch=z9hG4bK6y4e44vz0g05gez2x3nx01x9v;X-DispMsg=216
Call-ID: 2e36e2z3zry5y62xg2z146z21445101e@UAP6600
From: <sip:9001@192.168.2.27;user=phone>;tag=2xggg0ge-CC-57
To: <sip:888001@192.168.1.1;user=phone>
CSeq: 1 INVITE
Contact: <sip:9001@192.168.2.27:5060>
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,REGISTER,INFO,PRACK,SUBSCRIBE,NOTIFY,UPDATE,MESSAGE,REFER
User-Agent: Huawei eSpace U2990 V200R0
Supported: 100rel
Max-Forwards: 70
Content-Length: 474
Content-Type: application/sdp

v=0
o=HuaWeiUAP6600 478150935 478150935 IN IP4 192.168.3.17
s=Sip Call
c=IN IP4 192.168.2.38
t=0 0
m=audio 1104 RTP/AVP 8 0 125 122 18 9 124 4
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:125 iLBC/8000
a=rtpmap:122 AMR-WB/16000
a=rtpmap:18 G729/8000
a=rtpmap:9 G722/8000
a=rtpmap:124 G7221/16000
a=rtpmap:4 G723/8000
a=ptime:20
a=fmtp:125 mode=20
a=fmtp:122 mode-set=0,1,2,3,4,5,6,7,8
a=fmtp:124 bitrate=24000
a=fmtp:18 annexb=no
a=fmtp:4 annexa=no

Oct 22 12:03:54.506 HKT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.2.27:5062;branch=z9hG4bK6y4e44vz0g05gez2x3nx01x9v;X-DispMsg=216
From: <sip:9001@192.168.2.27;user=phone>;tag=2xggg0ge-CC-57
To: <sip:888001@192.168.1.1;user=phone>;tag=A5E20104-1631
Date: Tue, 22 Oct 2013 04:03:54 GMT
Call-ID: 2e36e2z3zry5y62xg2z146z21445101e@UAP6600
Server: Cisco-SIPGateway/IOS-12.x
CSeq: 1 INVITE
Allow-Events: telephone-event
Content-Length: 0

Oct 22 12:03:56.090 HKT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP 192.168.2.27:5062;branch=z9hG4bK6y4e44vz0g05gez2x3nx01x9v;X-DispMsg=216
From: <sip:9001@192.168.2.27;user=phone>;tag=2xggg0ge-CC-57
To: <sip:888001@192.168.1.1;user=phone>;tag=A5E20104-1631
Date: Tue, 22 Oct 2013 04:03:54 GMT
Call-ID: 2e36e2z3zry5y62xg2z146z21445101e@UAP6600
Server: Cisco-SIPGateway/IOS-12.x
CSeq: 1 INVITE
Require: 100rel
RSeq: 2791
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTER
Allow-Events: telephone-event
Contact: <sip:888001@192.168.1.1:5060>
Content-Disposition: session;handling=required
Content-Type: application/sdp
Content-Length: 191

v=0
o=CiscoSystemsSIP-GW-UserAgent 8094 2363 IN IP4 192.168.1.1
s=SIP Call
c=IN IP4 192.168.1.1
t=0 0
m=audio 16892 RTP/AVP 8
c=IN IP4 192.168.1.1
a=rtpmap:8 PCMA/8000
a=ptime:20

Oct 22 12:03:56.110 HKT: %ISDN-6-CONNECT: Interface Serial1/0:0 is now connected to 63119001 N/A
Oct 22 12:03:56.114 HKT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.2.27:5062;branch=z9hG4bK6y4e44vz0g05gez2x3nx01x9v;X-DispMsg=216
From: <sip:9001@192.168.2.27;user=phone>;tag=2xggg0ge-CC-57
To: <sip:888001@192.168.1.1;user=phone>;tag=A5E20104-1631
Date: Tue, 22 Oct 2013 04:03:54 GMT
Call-ID: 2e36e2z3zry5y62xg2z146z21445101e@UAP6600
Server: Cisco-SIPGateway/IOS-12.x
CSeq: 1 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTER
Allow-Events: telephone-event
Contact: <sip:888001@192.168.1.1:5060>
Content-Type: application/sdp
Content-Length: 191

v=0
o=CiscoSystemsSIP-GW-UserAgent 8094 2363 IN IP4 192.168.1.1
s=SIP Call
c=IN IP4 192.168.1.1
t=0 0
m=audio 16892 RTP/AVP 8
c=IN IP4 192.168.1.1
a=rtpmap:8 PCMA/8000
a=ptime:20

Oct 22 12:03:56.138 HKT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
PRACK sip:888001@192.168.1.1:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.27:5064;branch=z9hG4bKn145z24rnnyyx63n3ggyz0014;X-DispMsg=218
Call-ID: 2e36e2z3zry5y62xg2z146z21445101e@UAP6600
From: <sip:9001@192.168.2.27;user=phone>;tag=2xggg0ge-CC-57
To: <sip:888001@192.168.1.1;user=phone>;tag=A5E20104-1631
CSeq: 2 PRACK
Max-Forwards: 70
RAck: 2791 1 INVITE
Content-Length: 0

Oct 22 12:03:56.142 HKT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.2.27:5064;branch=z9hG4bKn145z24rnnyyx63n3ggyz0014;X-DispMsg=218
From: <sip:9001@192.168.2.27;user=phone>;tag=2xggg0ge-CC-57
To: <sip:888001@192.168.1.1;user=phone>;tag=A5E20104-1631
Date: Tue, 22 Oct 2013 04:03:56 GMT
Call-ID: 2e36e2z3zry5y62xg2z146z21445101e@UAP6600
Server: Cisco-SIPGateway/IOS-12.x
CSeq: 2 PRACK
Content-Length: 0

Oct 22 12:03:56.210 HKT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:888001@192.168.1.1:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.27:5060;branch=z9hG4bK49ynyr0x3xz0yzgggyx0x1v5x
Call-ID: 2e36e2z3zry5y62xg2z146z21445101e@UAP6600
From: <sip:9001@192.168.2.27;user=phone>;tag=2xggg0ge-CC-57
To: <sip:888001@192.168.1.1;user=phone>;tag=A5E20104-1631
CSeq: 1 ACK
Max-Forwards: 70
Content-Length: 0

Oct 22 12:03:56.210 HKT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
OPTIONS sip:888001@192.168.1.1:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.27:5065;branch=z9hG4bKrzryygzn693ne6035zr54zrn3;X-DispMsg=219
Call-ID: 2e36e2z3zry5y62xg2z146z21445101e@UAP6600
From: <sip:9001@192.168.2.27;user=phone>;tag=2xggg0ge-CC-57
To: <sip:888001@192.168.1.1;user=phone>;tag=A5E20104-1631
CSeq: 3 OPTIONS
Max-Forwards: 70
Content-Length: 0

Oct 22 12:03:56.214 HKT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.2.27:5065;branch=z9hG4bKrzryygzn693ne6035zr54zrn3;X-DispMsg=219
From: <sip:9001@192.168.2.27;user=phone>;tag=2xggg0ge-CC-57
To: <sip:888001@192.168.1.1;user=phone>;tag=A5E20104-1631
Date: Tue, 22 Oct 2013 04:03:56 GMT
Call-ID: 2e36e2z3zry5y62xg2z146z21445101e@UAP6600
Server: Cisco-SIPGateway/IOS-12.x
CSeq: 3 OPTIONS
Supported: 100rel,replaces
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTER
Accept: application/sdp
Allow-Events: telephone-event
Content-Length: 191
Content-Type: application/sdp

v=0
o=CiscoSystemsSIP-GW-UserAgent 8094 2363 IN IP4 192.168.1.1
s=SIP Call
c=IN IP4 192.168.1.1
t=0 0
m=audio 16892 RTP/AVP 8
c=IN IP4 192.168.1.1
a=rtpmap:8 PCMA/8000
a=ptime:20

Oct 22 12:03:56.378 HKT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:888001@192.168.1.1:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.27:5062;branch=z9hG4bKn04yyr0gr3xy3g4xegyrn61rx;X-DispMsg=216
Call-ID: 2e36e2z3zry5y62xg2z146z21445101e@UAP6600
From: <sip:9001@192.168.2.27;user=phone>;tag=2xggg0ge-CC-57
To: <sip:888001@192.168.1.1;user=phone>;tag=A5E20104-1631
CSeq: 4 INVITE
Contact: <sip:192.168.2.27:5060>
Max-Forwards: 70
Content-Length: 187
Content-Type: application/sdp

v=0
o=HuaWeiUAP6600 478150935 478150936 IN IP4 192.168.3.17
s=Sip Call
c=IN IP4 192.168.8.200
t=0 0
m=audio 10500 RTP/AVP 8 0
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=ptime:20

Oct 22 12:03:56.382 HKT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.2.27:5062;branch=z9hG4bKn04yyr0gr3xy3g4xegyrn61rx;X-DispMsg=216
From: <sip:9001@192.168.2.27;user=phone>;tag=2xggg0ge-CC-57
To: <sip:888001@192.168.1.1;user=phone>;tag=A5E20104-1631
Date: Tue, 22 Oct 2013 04:03:56 GMT
Call-ID: 2e36e2z3zry5y62xg2z146z21445101e@UAP6600
Server: Cisco-SIPGateway/IOS-12.x
CSeq: 4 INVITE
Allow-Events: telephone-event
Content-Length: 0

Oct 22 12:03:56.386 HKT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.2.27:5062;branch=z9hG4bKn04yyr0gr3xy3g4xegyrn61rx;X-DispMsg=216
From: <sip:9001@192.168.2.27;user=phone>;tag=2xggg0ge-CC-57
To: <sip:888001@192.168.1.1;user=phone>;tag=A5E20104-1631
Date: Tue, 22 Oct 2013 04:03:56 GMT
Call-ID: 2e36e2z3zry5y62xg2z146z21445101e@UAP6600
Server: Cisco-SIPGateway/IOS-12.x
CSeq: 4 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTER
Allow-Events: telephone-event
Contact: <sip:888001@192.168.1.1:5060>
Content-Type: application/sdp
Content-Length: 191

v=0
o=CiscoSystemsSIP-GW-UserAgent 8094 2364 IN IP4 192.168.1.1
s=SIP Call
c=IN IP4 192.168.1.1
t=0 0
m=audio 16892 RTP/AVP 8
c=IN IP4 192.168.1.1
a=rtpmap:8 PCMA/8000
a=ptime:20

Oct 22 12:03:56.450 HKT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
OPTIONS sip:888001@192.168.1.1:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.27:5063;branch=z9hG4bK5nv61e15eevze5rvnvrgn4g9z;X-DispMsg=217
Call-ID: 2e36e2z3zry5y62xg2z146z21445101e@UAP6600
From: <sip:9001@192.168.2.27;user=phone>;tag=2xggg0ge-CC-57
To: <sip:888001@192.168.1.1;user=phone>;tag=A5E20104-1631
CSeq: 5 OPTIONS
Max-Forwards: 70
Content-Length: 0

Oct 22 12:03:56.450 HKT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 491 Request Pending
Via: SIP/2.0/UDP 192.168.2.27:5063;branch=z9hG4bK5nv61e15eevze5rvnvrgn4g9z;X-DispMsg=217
From: <sip:9001@192.168.2.27;user=phone>;tag=2xggg0ge-CC-57
To: <sip:888001@192.168.1.1;user=phone>;tag=A5E20104-1631
Call-ID: 2e36e2z3zry5y62xg2z146z21445101e@UAP6600
CSeq: 5 OPTIONS
Content-Length: 0

Oct 22 12:03:56.454 HKT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:888001@192.168.1.1:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.27:5060;branch=z9hG4bK32r00vn61ry2re103303454ev
Call-ID: 2e36e2z3zry5y62xg2z146z21445101e@UAP6600
From: <sip:9001@192.168.2.27;user=phone>;tag=2xggg0ge-CC-57
To: <sip:888001@192.168.1.1;user=phone>;tag=A5E20104-1631
CSeq: 4 ACK
Max-Forwards: 70
Content-Length: 0

before has send this 200 ok message,here send again,up has recive the ack message,why send again.

Oct 22 12:03:56.882 HKT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.2.27:5062;branch=z9hG4bKn04yyr0gr3xy3g4xegyrn61rx;X-DispMsg=216
From: <sip:9001@192.168.2.27;user=phone>;tag=2xggg0ge-CC-57
To: <sip:888001@192.168.1.1;user=phone>;tag=A5E20104-1631
Date: Tue, 22 Oct 2013 04:03:56 GMT
Call-ID: 2e36e2z3zry5y62xg2z146z21445101e@UAP6600
Server: Cisco-SIPGateway/IOS-12.x
CSeq: 4 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTER
Allow-Events: telephone-event
Contact: <sip:888001@192.168.1.1:5060>
Content-Type: application/sdp
Content-Length: 191

v=0
o=CiscoSystemsSIP-GW-UserAgent 8094 2364 IN IP4 192.168.1.1
s=SIP Call
c=IN IP4 192.168.1.1
t=0 0
m=audio 16892 RTP/AVP 8
c=IN IP4 192.168.1.1
a=rtpmap:8 PCMA/8000
a=ptime:20

Oct 22 12:03:56.894 HKT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:888001@192.168.1.1:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.27:5064;branch=z9hG4bKnny21zy4xn931x03n1r19z9zr;X-DispMsg=218
Call-ID: 2e36e2z3zry5y62xg2z146z21445101e@UAP6600
From: <sip:9001@192.168.2.27;user=phone>;tag=2xggg0ge-CC-57
To: <sip:888001@192.168.1.1;user=phone>;tag=A5E20104-1631
CSeq: 6 INVITE
Contact: <sip:192.168.2.27:5060>
Max-Forwards: 70
Content-Length: 161
Content-Type: application/sdp

v=0
o=HuaWeiUAP6600 478150935 478150937 IN IP4 192.168.3.17
s=Sip Call
c=IN IP4 192.168.2.34
t=0 0
m=audio 1160 RTP/AVP 8
a=rtpmap:8 PCMA/8000
a=ptime:20

Oct 22 12:03:56.898 HKT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

here X-DispMsg should be 218,response to up invite,but 2821 router still made it 216 which made the u2990 drop it.

Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.2.27:5062;branch=z9hG4bKn04yyr0gr3xy3g4xegyrn61rx;X-DispMsg=216
From: <sip:9001@192.168.2.27;user=phone>;tag=2xggg0ge-CC-57
To: <sip:888001@192.168.1.1;user=phone>;tag=A5E20104-1631
Date: Tue, 22 Oct 2013 04:03:56 GMT
Call-ID: 2e36e2z3zry5y62xg2z146z21445101e@UAP6600
Server: Cisco-SIPGateway/IOS-12.x
CSeq: 6 INVITE
Allow-Events: telephone-event
Content-Length: 0

Oct 22 12:03:56.942 HKT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:888001@192.168.1.1:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.27:5060;branch=z9hG4bK32r00vn61ry2re103303454ev
Call-ID: 2e36e2z3zry5y62xg2z146z21445101e@UAP6600
From: <sip:9001@192.168.2.27;user=phone>;tag=2xggg0ge-CC-57
To: <sip:888001@192.168.1.1;user=phone>;tag=A5E20104-1631
CSeq: 4 ACK
Max-Forwards: 70
Content-Length: 0

Oct 22 12:03:57.398 HKT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:888001@192.168.1.1:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.27:5064;branch=z9hG4bKnny21zy4xn931x03n1r19z9zr;X-DispMsg=218
Call-ID: 2e36e2z3zry5y62xg2z146z21445101e@UAP6600
From: <sip:9001@192.168.2.27;user=phone>;tag=2xggg0ge-CC-57
To: <sip:888001@192.168.1.1;user=phone>;tag=A5E20104-1631
CSeq: 6 INVITE
Contact: <sip:192.168.2.27:5060>
Max-Forwards: 70
Content-Length: 161
Content-Type: application/sdp

v=0
o=HuaWeiUAP6600 478150935 478150937 IN IP4 192.168.3.17
s=Sip Call
c=IN IP4 192.168.2.34
t=0 0
m=audio 1160 RTP/AVP 8
a=rtpmap:8 PCMA/8000
a=ptime:20

here the same situation made again,X-DispMsg should be 218,but it made 216

Oct 22 12:03:57.402 HKT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.2.27:5062;branch=z9hG4bKn04yyr0gr3xy3g4xegyrn61rx;X-DispMsg=216
From: <sip:9001@192.168.2.27;user=phone>;tag=2xggg0ge-CC-57
To: <sip:888001@192.168.1.1;user=phone>;tag=A5E20104-1631
Date: Tue, 22 Oct 2013 04:03:57 GMT
Call-ID: 2e36e2z3zry5y62xg2z146z21445101e@UAP6600
Server: Cisco-SIPGateway/IOS-12.x
CSeq: 6 INVITE
Allow-Events: telephone-event
Content-Length: 0

Oct 22 12:03:57.882 HKT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.2.27:5062;branch=z9hG4bKn04yyr0gr3xy3g4xegyrn61rx;X-DispMsg=216
From: <sip:9001@192.168.2.27;user=phone>;tag=2xggg0ge-CC-57
To: <sip:888001@192.168.1.1;user=phone>;tag=A5E20104-1631
Date: Tue, 22 Oct 2013 04:03:57 GMT
Call-ID: 2e36e2z3zry5y62xg2z146z21445101e@UAP6600
Server: Cisco-SIPGateway/IOS-12.x
CSeq: 6 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTER
Allow-Events: telephone-event
Contact: <sip:888001@192.168.1.1:5060>
Content-Type: application/sdp
Content-Length: 191

v=0
o=CiscoSystemsSIP-GW-UserAgent 8094 2364 IN IP4 192.168.1.1
s=SIP Call
c=IN IP4 192.168.1.1
t=0 0
m=audio 16892 RTP/AVP 8
c=IN IP4 192.168.1.1
a=rtpmap:8 PCMA/8000
a=ptime:20

Oct 22 12:03:57.938 HKT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
OPTIONS sip:888001@192.168.1.1:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.27:5063;branch=z9hG4bK005y656rv4n3y9xx92g3r4yn4;X-DispMsg=217
Call-ID: 2e36e2z3zry5y62xg2z146z21445101e@UAP6600
From: <sip:9001@192.168.2.27;user=phone>;tag=2xggg0ge-CC-57
To: <sip:888001@192.168.1.1;user=phone>;tag=A5E20104-1631
CSeq: 7 OPTIONS
Max-Forwards: 70
Content-Length: 0

Oct 22 12:03:57.942 HKT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 491 Request Pending
Via: SIP/2.0/UDP 192.168.2.27:5063;branch=z9hG4bK005y656rv4n3y9xx92g3r4yn4;X-DispMsg=217
From: <sip:9001@192.168.2.27;user=phone>;tag=2xggg0ge-CC-57
To: <sip:888001@192.168.1.1;user=phone>;tag=A5E20104-1631
Call-ID: 2e36e2z3zry5y62xg2z146z21445101e@UAP6600
CSeq: 7 OPTIONS
Content-Length: 0

Oct 22 12:03:57.942 HKT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:888001@192.168.1.1:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.27:5060;branch=z9hG4bK2gx5ny4r0g2z1302y9v6r6yrx
Call-ID: 2e36e2z3zry5y62xg2z146z21445101e@UAP6600
From: <sip:9001@192.168.2.27;user=phone>;tag=2xggg0ge-CC-57
To: <sip:888001@192.168.1.1;user=phone>;tag=A5E20104-1631
CSeq: 6 ACK
Max-Forwards: 70
Content-Length: 0

Oct 22 12:03:58.238 HKT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:888001@192.168.1.1:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.27:5065;branch=z9hG4bK6n10e0exe6gn9e6xy9gvvz9x0;X-DispMsg=219
Call-ID: 2e36e2z3zry5y62xg2z146z21445101e@UAP6600
From: <sip:9001@192.168.2.27;user=phone>;tag=2xggg0ge-CC-57
To: <sip:888001@192.168.1.1;user=phone>;tag=A5E20104-1631
CSeq: 8 INVITE
Contact: <sip:192.168.2.27:5060>
Max-Forwards: 70
Content-Length: 161
Content-Type: application/sdp

v=0
o=HuaWeiUAP6600 478150935 478150938 IN IP4 192.168.3.17
s=Sip Call
c=IN IP4 192.168.2.37
t=0 0
m=audio 1090 RTP/AVP 8
a=rtpmap:8 PCMA/8000
a=ptime:20

here the same situation made again,X-DispMsg should be 219,but it made 216

Oct 22 12:03:58.242 HKT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.2.27:5062;branch=z9hG4bKn04yyr0gr3xy3g4xegyrn61rx;X-DispMsg=216
From: <sip:9001@192.168.2.27;user=phone>;tag=2xggg0ge-CC-57
To: <sip:888001@192.168.1.1;user=phone>;tag=A5E20104-1631
Date: Tue, 22 Oct 2013 04:03:58 GMT
Call-ID: 2e36e2z3zry5y62xg2z146z21445101e@UAP6600
Server: Cisco-SIPGateway/IOS-12.x
CSeq: 8 INVITE
Allow-Events: telephone-event
Content-Length: 0

U2990 did not recive the correct response,it send the Internal Server Error message,after that send the bye message

Oct 22 12:03:58.406 HKT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:888001@192.168.1.1:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.27:5064;branch=z9hG4bKnny21zy4xn931x03n1r19z9zr;X-DispMsg=218
Call-ID: 2e36e2z3zry5y62xg2z146z21445101e@UAP6600
From: <sip:9001@192.168.2.27;user=phone>;tag=2xggg0ge-CC-57
To: <sip:888001@192.168.1.1;user=phone>;tag=A5E20104-1631
CSeq: 6 INVITE
Contact: <sip:192.168.2.27:5060>
Max-Forwards: 70
Content-Length: 161
Content-Type: application/sdp

v=0
o=HuaWeiUAP6600 478150935 478150937 IN IP4 192.168.3.17
s=Sip Call
c=IN IP4 192.168.2.34
t=0 0
m=audio 1160 RTP/AVP 8
a=rtpmap:8 PCMA/8000
a=ptime:20

Oct 22 12:03:58.410 HKT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 500 Internal Server Error
Via: SIP/2.0/UDP 192.168.2.27:5064;branch=z9hG4bKnny21zy4xn931x03n1r19z9zr;X-DispMsg=218
From: <sip:9001@192.168.2.27;user=phone>;tag=2xggg0ge-CC-57
To: <sip:888001@192.168.1.1;user=phone>;tag=A5E20104-1631
Call-ID: 2e36e2z3zry5y62xg2z146z21445101e@UAP6600
CSeq: 6 INVITE
Content-Length: 0

Oct 22 12:03:58.454 HKT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:888001@192.168.1.1:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.27:5064;branch=z9hG4bKnny21zy4xn931x03n1r19z9zr;X-DispMsg=218
Call-ID: 2e36e2z3zry5y62xg2z146z21445101e@UAP6600
From: <sip:9001@192.168.2.27;user=phone>;tag=2xggg0ge-CC-57
To: <sip:888001@192.168.1.1;user=phone>;tag=A5E20104-1631
CSeq: 6 ACK
Max-Forwards: 70
Content-Length: 0

Oct 22 12:03:58.466 HKT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
OPTIONS sip:888001@192.168.1.1:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.27:5062;branch=z9hG4bK3r5xx32rn31n09zz2g30y9nyn;X-DispMsg=216
Call-ID: 2e36e2z3zry5y62xg2z146z21445101e@UAP6600
From: <sip:9001@192.168.2.27;user=phone>;tag=2xggg0ge-CC-57
To: <sip:888001@192.168.1.1;user=phone>;tag=A5E20104-1631
CSeq: 9 OPTIONS
Max-Forwards: 70
Content-Length: 0

Oct 22 12:03:58.466 HKT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 491 Request Pending
Via: SIP/2.0/UDP 192.168.2.27:5062;branch=z9hG4bK3r5xx32rn31n09zz2g30y9nyn;X-DispMsg=216
From: <sip:9001@192.168.2.27;user=phone>;tag=2xggg0ge-CC-57
To: <sip:888001@192.168.1.1;user=phone>;tag=A5E20104-1631
Call-ID: 2e36e2z3zry5y62xg2z146z21445101e@UAP6600
CSeq: 9 OPTIONS
Content-Length: 0

Oct 22 12:03:58.470 HKT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
BYE sip:888001@192.168.1.1:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.27:5064;branch=z9hG4bK39934zxez4r3zxve9xe9nz26x;X-DispMsg=218
Call-ID: 2e36e2z3zry5y62xg2z146z21445101e@UAP6600
From: <sip:9001@192.168.2.27;user=phone>;tag=2xggg0ge-CC-57
To: <sip:888001@192.168.1.1;user=phone>;tag=A5E20104-1631
CSeq: 10 BYE
Max-Forwards: 70
Content-Length: 0

Oct 22 12:03:58.474 HKT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.2.27:5064;branch=z9hG4bK39934zxez4r3zxve9xe9nz26x;X-DispMsg=218
From: <sip:9001@192.168.2.27;user=phone>;tag=2xggg0ge-CC-57
To: <sip:888001@192.168.1.1;user=phone>;tag=A5E20104-1631
Date: Tue, 22 Oct 2013 04:03:58 GMT
Call-ID: 2e36e2z3zry5y62xg2z146z21445101e@UAP6600
Server: Cisco-SIPGateway/IOS-12.x
Content-Length: 0
CSeq: 10 BYE

0 Helpful
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Customers Also Viewed These Support Documents