topic Re: CuCM issue with Huntpiloturi String in Unified Communications Infrastructure

CuCM issue with Huntpiloturi String

michael.schenk — Wed, 19 Dec 2018 08:45:54 GMT

Hi all,

we have a customer with Cisco CUCM Version 11.5.1.15900-18.
Our System is the ascom IP-DECT. When we use a Hunt Group the Alerting Name contains wrong Information.

On the Display it's shown like this: "%22Test%22 (Test being a test name for Alerting Name).

But as you can see in the attached Image, in the "Alerting Name" Field it's only "Test" filled in.

With Wireshark, you can see the following String:
Huntpiloturi ="%22Test%22<sip:XXXXXXXXXX@IP.IP.IP.IP>"

Has anyone similar issues? What might cause this issue?

Best regards
Michael

Re: CuCM issue with Huntpiloturi String

Jonathan Schulenberg — Thu, 20 Dec 2018 00:55:34 GMT

Well, %22 is how you escape a double quotation mark, which would be necessary since the full value appears to be encapsulated in double quotes already. SIP headers are not normally formatted that way though. Can we see either a screenshot of the Wireshark protocol debug or a plain text version of the SIP message?

Re: CuCM issue with Huntpiloturi String

michael.schenk — Thu, 20 Dec 2018 07:59:40 GMT

First, thanks for that quick reply!

Here you can see a screenshot of the Message Header Part from the Wireshark protocol debug:

Is there anything else you ned? I tried to paint over the private data black.

/Michael

Re: CuCM issue with Huntpiloturi String

Jonathan Schulenberg — Fri, 21 Dec 2018 15:48:29 GMT

Ah ok, it's a parameter on the Call-Info header, not a header by itself. This appears to conform to RFC3261 section 25.1 which requires certain special characters - including DQUOTE - be escaped if they appear within a parameter value. I believe the errant behavior here is on the Ascom side of things, though I'll admit a bit of surprise that they're looking at this in the first place.

Re: CuCM issue with Huntpiloturi String

Jonathan Schulenberg — Sun, 20 Jan 2019 18:22:30 GMT

It appears Cisco decided to create a defect for this behavior:

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvn75533

Re: CuCM issue with Huntpiloturi String

michael.schenk — Mon, 21 Jan 2019 16:19:26 GMT

Thank you very much for your help!

It seems to be fixed now. Good News for our customer.