11-21-2018 03:40 PM - edited 03-17-2019 01:45 PM
Hi all,
We have a video chat solution where a caller can go to our website and initiate a video chat and it hooks up to our CUBE and PCCE environment and an agent with Finesse/Jabber can answer the call. This was working great until i upgraded the CUBE IOS and now the solution broke. Please HELP. The only difference I see in the old and the new config is
voice service voip
ip address trusted list
ipv4 0.0.0.0 0.0.0.0
allow-connections sip to sip
signaling forward unconditional
fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none
sip
bind control source-interface Loopback0
bind media source-interface Loopback0
rel1xx disable
min-se 360 (there was extra command here that the cube wont let me save anymore "session-expire 360")
header-passing
asymmetric payload full
midcall-signaling block
early-offer forced
pass-thru headers 10
sip-profiles inbound
video screening
Here are the debug logs:
000846: Nov 21 13:58:01: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:2504100784@10.85.211.235 SIP/2.0
Call-ID: bc716499c181faaef0816be6e3c9a46c@10.85.114.150
CSeq: 1 INVITE
From: <sip:assist-klo2a6kgt39q1mmbqcocfsj6r@t1cafex.maximusbc.ca>;tag=0-mobi-84895078_ada14cd5_37c5939f-b806-4f10-8021-3c7ba63cf0f9_2
To: <sip:2504100784@aaa.qaz>
Max-Forwards: 69
Contact: <sip:assist-klo2a6kgt39q1mmbqcocfsj6r@t1cafex.maximusbc.ca:5060>
Min-SE: 400
Session-Expires: 10800
Content-Type: application/sdp
Allow-Events: refer
Allow: NOTIFY,REFER,CANCEL,ACK,PRACK,UPDATE,INFO,INVITE,SUBSCRIBE
Supported: 100rel,timer
Route: <sip:10.85.211.235;lr>
Via: SIP/2.0/TCP 10.85.114.150:5080;branch=z9hG4bK63c98318-85bc-47c9-ba5d-f6b50b20be41_5_e897ac49_4075237035667374_0
Content-Length: 1672
v=0
o=- 5609666596 1 IN IP4 10.85.114.150
s=-
t=0 0
m=audio 17022 RTP/AVP 111 0 8 18 110 112 113 126
c=IN IP4 10.85.114.151
a=rtpmap:111 opus/48000/2
a=fmtp:111 minptime=10;useinbandfec=1
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000
a=rtpmap:110 telephone-event/48000
a=rtpmap:112 telephone-event/32000
a=rtpmap:113 telephone-event/16000
a=rtpmap:126 telephone-event/8000
a=sendrecv
m=video 17006 RTP/AVP 96 98 100 107
c=IN IP4 10.85.114.151
b=AS:4000
b=TIAS:4000000
a=rtpmap:96 VP8/90000
a=rtcp-fb:96 nack
a=rtcp-fb:96 ccm fir
a=rtcp-fb:96 nack pli
a=rtpmap:98 VP9/90000
a=rtpmap:100 H264/90000
a=fmtp:100 level-asymmetry-allowed=1;packetization-mode=1;profile-level-id=42e01f
a=rtcp-fb:100 nack
a=rtcp-fb:100 ccm fir
a=rtcp-fb:100 nack pli
a=rtpmap:107 H264/90000
a=fmtp:107 profile-level-id=42c01f;packetization-mode=0;level-asymmetry-allowed=1
a=rtcp-fb:107 nack
a=rtcp-fb:107 ccm fir
a=rtcp-fb:107 nack pli
a=sendrecv
a=imageattr:98 send [x=640,y=480] [x=320,y=240] [x=272,y=224] [x=224,y=176] [x=176,y=144] recv [x=640,y=480] [x=320,y=240] [x=272,y=224] [x=224,y=176] [x=176,y=144]
a=imageattr:96 send [x=640,y=480] [x=320,y=240] [x=272,y=224] [x=224,y=176] [x=176,y=144] recv [x=640,y=480] [x=320,y=240] [x=272,y=224] [x=224,y=176] [x=176,y=144]
a=imageattr:100 send [x=640,y=480] [x=320,y=240] [x=272,y=224] [x=224,y=176] [x=176,y=144] recv [x=640,y=480] [x=320,y=240] [x=272,y=224] [x=224,y=176] [x=176,y=144]
a=imageattr:107 send [x=640,y=480] [x=320,y=240] [x=272,y=224] [x=224,y=176] [x=176,y=144] recv [x=640,y=480] [x=320,y=240] [x=272,y=224] [x=224,y=176] [x=176,y=144]
a=content:main
a=label:11
000847: Nov 21 13:58:02: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 400 Bad Request
Via: SIP/2.0/TCP 10.85.114.150:5080;branch=z9hG4bK63c98318-85bc-47c9-ba5d-f6b50b20be41_5_e897ac49_4075237035667374_0
From: <sip:assist-klo2a6kgt39q1mmbqcocfsj6r@t1cafex.maximusbc.ca>;tag=0-mobi-84895078_ada14cd5_37c5939f-b806-4f10-8021-3c7ba63cf0f9_2
To: <sip:2504100784@aaa.qaz>;tag=3F6248-6C1
Date: Wed, 21 Nov 2018 21:58:01 GMT
Call-ID: bc716499c181faaef0816be6e3c9a46c@10.85.114.150
CSeq: 1 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.7.3.M3
Session-ID: 79e3eb4ca6db59e4ac70140748e1c449;remote=8df7590703e55052973e343af4c0ac83
Content-Length: 0
000848: Nov 21 13:58:02: //384/59B2909F81D0/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:2504100784@10.85.211.235 SIP/2.0
Call-ID: bc716499c181faaef0816be6e3c9a46c@10.85.114.150
Max-Forwards: 69
From: <sip:assist-klo2a6kgt39q1mmbqcocfsj6r@t1cafex.maximusbc.ca>;tag=0-mobi-84895078_ada14cd5_37c5939f-b806-4f10-8021-3c7ba63cf0f9_2
To: <sip:2504100784@aaa.qaz>;tag=3F6248-6C1
Via: SIP/2.0/TCP 10.85.114.150:5080;branch=z9hG4bK63c98318-85bc-47c9-ba5d-f6b50b20be41_5_e897ac49_4075237035667374_0
CSeq: 1 ACK
Route: <sip:10.85.211.235;lr>
Content-Length: 0
000849: Nov 21 13:58:02: //384/59B2909F81D0/SIP/Call/sipSPICallInfo:
The Call Setup Information is:
Call Control Block (CCB) : 0x0x423C8898
State of The Call : STATE_DEAD
TCP Sockets Used : YES
Calling Number : assist-klo2a6kgt39q1mmbqcocfsj6r
Called Number : 2504100784
Source IP Address (Sig ): 10.85.211.235
Destn SIP Req Addr:Port : 10.85.114.150:0
Destn SIP Resp Addr:Port : 10.85.114.150:48426
Destination Name : 10.85.114.150
000850: Nov 21 13:58:02: //384/59B2909F81D0/SIP/Call/sipSPICallInfo:
Disconnect Cause (CC) : 16
Disconnect Cause (SIP) : 400
Should I revert back to the old IOS?
Old IOS: c2900-universalk9-mz.SPA.154-3.M10.
New IOS: c2900-universalk9-mz.SPA.157-3.M3.bin
Solved! Go to Solution.
11-21-2018 08:52 PM
What about contacting TAC to check for relative bugs on this IOS?
G
11-21-2018 08:52 PM
What about contacting TAC to check for relative bugs on this IOS?
G
11-22-2018 08:57 AM
HI Geos, thank you for your reply. I have decided to roll back to the previous version and now everything is back to normal. Our environment is very busy and dont have much time to play around in the change window, but yes I will definitely contact TAC and schedule a change window to see if they can figure out what breaks it.
Thank you.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide