cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2035
Views
0
Helpful
0
Replies

Call disconnect after SIP/2.0 491 Request Pending

kiranoddiraju
Level 1
Level 1

Hi guys,

I have a weird problem with pstn mobile calls going to voicemail. We have a CUBE between Telco SBC and Cisco CallManager. When Extension-A calls PSTN mobile and forwarded to voicemail, there is a 4-5 seconds silence and then the call is getting disconnected. The CUBE doesn't seem to be sending re-INVITE to the SBC. Any idea why?

PSTN <--> SBC <--> CUBE <--> CUCM <--> IP Phone

CUBE IOS: 153-3.M5.bin  -- 10.200.13.250

CUCM ver 10.5 -- 10.200.13.2

SBC - 62.59.xx.xx

Here's the trace:

JulJul 26 13:06:33.531 UTC: //79762/C2E33E000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP 10.200.13.250:5060;branch=z9hG4bK2AD226AD
From: "Reception" <sip:+31203334455@10.200.13.250>;tag=71AA2680-1555
To: <sip:+31651850000@62.59.xx.xx>;tag=SDr983999-db97140721724201672615629
Call-ID: 99F7A16E-526811E6-AA71F069-8F52818E@10.200.13.250
CSeq: 101 INVITE
Timestamp: 1469538389
Server: CS2000_NGSS/9.0
Require: 100rel
Allow: ACK,BYE,CANCEL,INVITE,OPTIONS,INFO,SUBSCRIBE,REFER,NOTIFY,PRACK,UPDATE
RSeq: 887
Contact: <sip:62.59.xx.xx:5060;transport=udp>
Supported: 100rel
Content-Type: application/sdp
Content-Length: 277

v=0
o=BroadWorks 1726841 1 IN IP4 62.59.xx.xx
s=-
c=IN IP4 62.59.xx.xx
t=0 0
a=sqn: 0
a=cdsc: 1 image udptl t38
a=cpar: a=T38FaxVersion:0
a=cpar: a=T38FaxUdpEC:t38UDPRedundancy
m=audio 18302 RTP/AVP 8 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20

Jul 26 13:06:33.531 UTC: //79762/C2E33E000000/SIP/Msg/ccsipDisplayMsg:
Sent:
PRACK sip:62.59.xx.xx:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 10.200.13.250:5060;branch=z9hG4bK2AD31705
From: "Reception" <sip:+31203334455@10.200.13.250>;tag=71AA2680-1555
To: <sip:+31651850000@62.59.xx.xx>;tag=SDr983999-db97140721724201672615629
Date: Tue, 26 Jul 2016 13:06:29 GMT
Call-ID: 99F7A16E-526811E6-AA71F069-8F52818E@10.200.13.250
CSeq: 102 PRACK
RAck: 887 101 INVITE
Allow-Events: telephone-event
Max-Forwards: 70
Content-Length: 0


Jul 26 13:06:33.535 UTC: //79761/C2E33E000000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 183 Session Progress
Via: SIP/2.0/TCP 10.200.13.2:5060;branch=z9hG4bK38525219b322
From: "Reception" <sip:0205405555@10.200.13.2>;tag=170370~48710706-bbf c-f92d-c90a-b436a404d943-73672003
To: <sip:0651850000@10.200.13.250>;tag=71AA366C-8BD
Date: Tue, 26 Jul 2016 13:06:29 GMT
Call-ID: c2e33e00-79716055-19b5-20dc80a@10.200.13.2
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIF Y, INFO, REGISTER
Allow-Events: telephone-event
Remote-Party-ID: <sip:+31651850000@10.200.13.250>;party=called;screen=yes;privac y=off
Contact: <sip:0651850000@10.200.13.250:5060;transport=tcp>
Supported: sdp-anat
Server: Cisco-SIPGateway/IOS-15.3.3.M5
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 250

v=0
o=CiscoSystemsSIP-GW-UserAgent 3316 7780 IN IP4 10.200.13.250
s=SIP Call
c=IN IP4 10.200.13.250
t=0 0
m=audio 28086 RTP/AVP 8 101
c=IN IP4 10.200.13.250
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20

Jul 26 13:06:33.539 UTC: //79762/C2E33E000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.200.13.250:5060;branch=z9hG4bK2AD31705
From: "Reception" <sip:+31203334455@10.200.13.250>;tag=71AA2680-1555
To: <sip:+31651850000@62.59.xx.xx>;tag=SDr983999-db97140721724201672615629
Call-ID: 99F7A16E-526811E6-AA71F069-8F52818E@10.200.13.250
CSeq: 102 PRACK
Server: CS2000_NGSS/9.0
Supported: 100rel
Allow: ACK,BYE,CANCEL,INVITE,OPTIONS,INFO,SUBSCRIBE,REFER,NOTIFY,PRACK,UPDATE
Content-Length: 0


Jul 26 13:06:40.823 UTC: //79764/A0BDA5DDAA73/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 62.59.xx.xx:5060;branch=z9hG4bKa8nb1d207obgtd10i660
From: <sip:ping@62.59.xx.xx>;tag=f3fab17aba13bf367662b03ed6852edb0g085u3
To: sip:ping@10.200.13.250;tag=71AA52E4-196E
Date: Tue, 26 Jul 2016 13:06:40 GMT
Call-ID: 0d7166012aa28ed6c3272bd4f5c4694a0g085u3@62.59.xx.xx
Server: Cisco-SIPGateway/IOS-15.3.3.M5
CSeq: 152828 OPTIONS
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Accept: application/sdp
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Content-Type: application/sdp
Content-Length: 375

v=0
o=CiscoSystemsSIP-GW-UserAgent 2086 7445 IN IP4 10.200.13.250
s=SIP Call
c=IN IP4 10.200.13.250
t=0 0
m=audio 0 RTP/AVP 18 0 8 9 4 2 15
c=IN IP4 10.200.13.250
m=image 0 udptl t38
c=IN IP4 10.200.13.250
a=T38FaxVersion:0
a=T38MaxBitRate:9600
a=T38FaxRateManagement:transferredTCF
a=T38FaxMaxBuffer:200
a=T38FaxMaxDatagram:320
a=T38FaxUdpEC:t38UDPRedundancy

Jul 26 13:06:54.091 UTC: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
UPDATE sip:+31203334455@10.200.13.250:5060 SIP/2.0
Via: SIP/2.0/UDP 62.59.xx.xx:5060;branch=z9hG4bKbc53qa20bghgr9thi711.1
From: <sip:+31651850000@voip.tele2.nl>;tag=SDr983999-db97140721724201672615629
To: "Reception" <sip:205405555@10.200.13.250>;tag=71AA2680-1555
Call-ID: 99F7A16E-526811E6-AA71F069-8F52818E@10.200.13.250
CSeq: 1 UPDATE
User-agent: CS2000_NGSS/9.0
Max-Forwards: 69
Allow: ACK,BYE,CANCEL,INVITE,OPTIONS,INFO,SUBSCRIBE,REFER,NOTIFY,PRACK,UPDATE
Contact: <sip:62.59.xx.xx:5060;transport=udp>
Supported: 100rel
Content-Type: application/sdp
Content-Length: 207

v=0
o=BroadWorks 1726841 2 IN IP4 62.59.xx.xx
s=-
c=IN IP4 62.59.xx.xx
t=0 0
a=sendrecv
m=audio 18302 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=ptime:20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

Jul 26 13:06:54.095 UTC: //79762/C2E33E000000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 491 Request Pending
Via: SIP/2.0/UDP 62.59.xx.xx:5060;branch=z9hG4bKbc53qa20bghgr9thi711.1
From: <sip:+31651850000@62.59.xx.xx>;tag=SDr983999-db97140721724201672615629
To: "Reception" <sip:+31203334455@10.200.13.250>;tag=71AA2680-1555
Date: Tue, 26 Jul 2016 13:06:54 GMT
Call-ID: 99F7A16E-526811E6-AA71F069-8F52818E@10.200.13.250
Server: Cisco-SIPGateway/IOS-15.3.3.M5
CSeq: 1 UPDATE
Allow-Events: telephone-event
Content-Length: 0


Jul 26 13:07:07.888 UTC: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
CANCEL sip:0651850000@10.200.13.250:5060 SIP/2.0
Via: SIP/2.0/TCP 10.200.13.2:5060;branch=z9hG4bK38525219b322
From: "Reception" <sip:0205405555@10.200.13.2>;tag=170370~48710706-bbfc-f92d-c90a-b436a404d943-73672003
To: <sip:0651850000@10.200.13.250>
Date: Tue, 26 Jul 2016 13:06:29 GMT
Call-ID: c2e33e00-79716055-19b5-20dc80a@10.200.13.2
User-Agent: Cisco-CUCM10.5
CSeq: 101 CANCEL
Max-Forwards: 70
Content-Length: 0


Jul 26 13:07:07.888 UTC: //79761/C2E33E000000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/TCP 10.200.13.2:5060;branch=z9hG4bK38525219b322
From: "Reception" <sip:0205405555@10.200.13.2>;tag=170370~48710706-bbfc-f92d-c90a-b436a404d943-73672003
To: <sip:0651850000@10.200.13.250>
Date: Tue, 26 Jul 2016 13:07:07 GMT
Call-ID: c2e33e00-79716055-19b5-20dc80a@10.200.13.2
CSeq: 101 CANCEL
Content-Length: 0


Jul 26 13:07:07.892 UTC: //79762/C2E33E000000/SIP/Msg/ccsipDisplayMsg:
Sent:
CANCEL sip:+31651850000@62.59.xx.xx:5060 SIP/2.0
Via: SIP/2.0/UDP 10.200.13.250:5060;branch=z9hG4bK2AD226AD
From: "Reception" <sip:+31203334455@10.200.13.250>;tag=71AA2680-1555
To: <sip:+31651850000@62.59.xx.xx>
Date: Tue, 26 Jul 2016 13:06:54 GMT
Call-ID: 99F7A16E-526811E6-AA71F069-8F52818E@10.200.13.250
CSeq: 101 CANCEL
Max-Forwards: 70
Timestamp: 1469538427
Reason: Q.850;cause=16
Content-Length: 0


Jul 26 13:07:07.892 UTC: //79761/C2E33E000000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 487 Request Cancelled
Via: SIP/2.0/TCP 10.200.13.2:5060;branch=z9hG4bK38525219b322
From: "Reception" <sip:0205405555@10.200.13.2>;tag=170370~48710706-bbfc-f92d-c90a-b436a404d943-73672003
To: <sip:0651850000@10.200.13.250>;tag=71AA366C-8BD
Date: Tue, 26 Jul 2016 13:07:07 GMT
Call-ID: c2e33e00-79716055-19b5-20dc80a@10.200.13.2
CSeq: 101 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.3.3.M5
Reason: Q.850;cause=16
Content-Length: 0


Jul 26 13:07:07.892 UTC: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:0651850000@10.200.13.250:5060 SIP/2.0
Via: SIP/2.0/TCP 10.200.13.2:5060;branch=z9hG4bK38525219b322
From: "Reception" <sip:0205405555@10.200.13.2>;tag=170370~48710706-bbfc-f92d-c90a-b436a404d943-73672003
To: <sip:0651850000@10.200.13.250>;tag=71AA366C-8BD
Date: Tue, 26 Jul 2016 13:06:29 GMT
Call-ID: c2e33e00-79716055-19b5-20dc80a@10.200.13.2
User-Agent: Cisco-CUCM10.5
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: presence, kpml
Content-Length: 0


Jul 26 13:07:07.900 UTC: //79762/C2E33E000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.200.13.250:5060;branch=z9hG4bK2AD226AD
From: "Reception" <sip:+31203334455@10.200.13.250>;tag=71AA2680-1555
To: <sip:+31651850000@62.59.xx.xx>;tag=SDr983999-db97140721724201672615629
Call-ID: 99F7A16E-526811E6-AA71F069-8F52818E@10.200.13.250
CSeq: 101 CANCEL
Timestamp: 1469538427


Jul 26 13:07:07.908 UTC: //79762/C2E33E000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 487 Request Terminated
Via: SIP/2.0/UDP 10.200.13.250:5060;branch=z9hG4bK2AD226AD
From: "Reception" <sip:+31203334455@10.200.13.250>;tag=71AA2680-1555
To: <sip:+31651850000@62.59.xx.xx>;tag=SDr983999-db97140721724201672615629
Call-ID: 99F7A16E-526811E6-AA71F069-8F52818E@10.200.13.250
CSeq: 101 INVITE
Timestamp: 1469538389
Server: CS2000_NGSS/9.0
Supported: 100rel
Allow: ACK,BYE,CANCEL,INVITE,OPTIONS,INFO,SUBSCRIBE,REFER,NOTIFY,PRACK,UPDATE
Content-Length: 0


Jul 26 13:07:07.908 UTC: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:+31651850000@62.59.xx.xx:5060 SIP/2.0
Via: SIP/2.0/UDP 10.200.13.250:5060;branch=z9hG4bK2AD226AD
From: "Reception" <sip:+31203334455@10.200.13.250>;tag=71AA2680-1555
To: <sip:+31651850000@62.59.xx.xx>;tag=SDr983999-db97140721724201672615629
Date: Tue, 26 Jul 2016 13:06:54 GMT
Call-ID: 99F7A16E-526811E6-AA71F069-8F52818E@10.200.13.250
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Content-Length: 0



Any help would be much appreciated.

Thanks,

KO

0 Replies 0
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: