- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-27-2018 02:02 PM - edited 03-19-2019 01:18 PM
Hi, I'm having problems with Call pickup in a brand new set up:
+CUCM has a sip trunk against a Huawei SBC
+Cisco phones are configured in SIP.
A->PSTN->SBC->CUCM->B
When A calls comes from the outside and some member from the line group tries to pick up the call (B) the caller keeps it ringing and the line that picked up the call has a dead air until the call drops for both.
If someone calls from another extension, call pick up works fine.
Call traces pics are attached.
I've founded something strange in the call trace regarding the contact that shows some "sip:xxxxxstrangenumberxxxx@CUCM-IP", which is extracted from the UPDATE message sent from the CUCM to the SBC, and a part of it is below:
User-Agent: Cisco-CP8865/12.0.1
Max-Forwards: 70
Supported: timer,resource-priority,replaces
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 UPDATE
Session-ID: 62733c4f00105000a000002790816281;remote=c5deb4a39e22a61749aa7abfaab47357
Call-Info: <urn:x-cisco-remotecc:callinfo>;x-cisco-video-traffic-class=DESKTOP;x-cisco-qos-tcl=true
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Min-SE: 1800
Contact: <sip:b42b69e0-2ce7-b8d3-1928-bd4b10617df4@10.190.0.69:5060>;video;audio;+u.sip!devicename.ccm.cisco.com="SEP002790816281"
Contact URI: sip:b42b69e0-2ce7-b8d3-1928-bd4b10617df4@10.190.0.69:5060
Contact parameter: video
Contact parameter: audio
Contact parameter: +u.sip!devicename.ccm.cisco.com="SEP002790816281"\r\n
Content-Length: 0
When the SBC receives it answers with a 491 Request Pending ( I assume because it doesn't understand the hostname)
Help needed.
Thank you in advance.
Solved! Go to Solution.
- Labels:
-
Other Unified Communications
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-30-2018 09:57 AM
Hi Franklin, yes we managed by creating a Sip Normalization Script and bind it in the Trunk Configuration in order to remove the contact id.
1. Device>Device Settings>Sip Normalization Script>Add New
And paste the following script:
M = {}
function M.inbound_INVITE(msg)
msg:removeHeaderValue("Allow", "UPDATE")
end
return M
Save it!
2. Device>Trunk and select the trunk with the problem
Then go to the Normalization Script area and select the script created before.
Save it!
And that did the job.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-30-2018 08:42 AM
Hi nicolp_ar,
I have the same problem whit a CUCM 11.5. We have sip trunk whit several ITSP and this only happens whit one of them. User started reporting it 2 days ago. Could you solve the problem?
Regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-30-2018 09:57 AM
Hi Franklin, yes we managed by creating a Sip Normalization Script and bind it in the Trunk Configuration in order to remove the contact id.
1. Device>Device Settings>Sip Normalization Script>Add New
And paste the following script:
M = {}
function M.inbound_INVITE(msg)
msg:removeHeaderValue("Allow", "UPDATE")
end
return M
Save it!
2. Device>Trunk and select the trunk with the problem
Then go to the Normalization Script area and select the script created before.
Save it!
And that did the job.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-30-2018 11:11 AM
