Route Pattern Question. Can a Route Pattern contain an astrick (*) in the middle of the dial string?

[jamize]

We are trying to connect a Call Manager 8.6.2SU3 with Vocera and Nurse Call systems via SIP Trunks.  The vendor has requested the following Route Pattern: 2051169760.!*!#

When we try to dial a number such as: 2051169760338*6678770# we hear "Your call can't be completed as dialed".

Can the Route Pattern contain a (*) in the middle of the dial string?

Thanks,

Jeff

[Nadeem Ahmed]

Hi Jeff,

I just tested in my lab with an environment CCM----SIPTRUNK----VGW and configured the same RP as mentioned call is being sent from CUCM to my VGW however it works as i was expecting to be. but crux was CUCM didn't override (*) and sent the call to next hop over a SIP trunk.

Here is trace collected on VGW

og Buffer (500000 bytes):

*Oct 21 22:31:59.438: %ENVMON-4-FAN_LOW_RPM: Fan 1 service recommended
*Oct 21 22:32:12.242: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Here INVITE Received from CUCM.

Received:
INVITE sip:2051169760388*6678770@XX.XX.XX.XX:5060 SIP/2.0
Via: SIP/2.0/UDP XX.XX.XX.XX:5060;branch=z9hG4bKa8aeeae7d
From: "Nadeem'Phone" <sip:5000@XX.XX.XX.XX>;tag=13126~eada4422-7620-4109-867b-63b7c5eb269c-39467100
To: <sip:2051169760388*6678770@XX.XX.XX.XX>
Date: Wed, 21 Oct 2015 15:45:31 GMT
Call-ID: c11ca500-6271b31b-45-cb64d0a@XX.XX.XX.XX
Supported: timer,resource-priority,replaces
Min-SE:  1800
User-Agent: Cisco-CUCM9.1
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Expires: 180
Allow-Events: presence, kpml
Supported: X-cisco-srtp-fallback,X-cisco-original-called
Call-Info: <sip:XX.XX.XX.XX:5060>;method="NOTIFY;Event=telephone-event;Duration=500"
Cisco-Guid: 3239879936-0000065536-0000000003-0213273866
Session-Expires:  1800
P-Asserted-Identity: "Nadeem'Phone" <sip:5000@XX.XX.XX.XX>
Remote-Party-ID: "Nadeem'Phone" <sip:5000@XX.XX.XX.XX>;party=calling;screen=yes;privacy=off
Contact: <sip:5000@XX.XX.XX.XX:5060>;video;audio;+u.sip!devicename.ccm.cisco.com="SEPD0C7891413E1";bfcp
Max-Forwards: 69
Content-Length: 0

*Oct 21 22:32:12.250: //72979/C11CA5000000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP XX.XX.XX.XX:5060;branch=z9hG4bKa8aeeae7d
From: "Nadeem'Phone" <sip:5000@XX.XX.XX.XX>;tag=13126~eada4422-7620-4109-867b-63b7c5eb269c-39467100
To: <sip:2051169760388*6678770@XX.XX.XX.XX>
Date: Wed, 21 Oct 2015 22:32:12 GMT
Call-ID: c11ca500-6271b31b-45-cb64d0a@XX.XX.XX.XX
CSeq: 101 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-12.x
Content-Length: 0

*Oct 21 22:32:12.250: //72979/C11CA5000000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP XX.XX.XX.XX:5060;branch=z9hG4bKa8aeeae7d
From: "Nadeem'Phone" <sip:5000@XX.XX.XX.XX>;tag=13126~eada4422-7620-4109-867b-63b7c5eb269c-39467100
To: <sip:2051169760388*6678770@XX.XX.XX.XX>;tag=1658B18-D2A
Date: Wed, 21 Oct 2015 22:32:12 GMT
Call-ID: c11ca500-6271b31b-45-cb64d0a@XX.XX.XX.XX
CSeq: 101 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-12.x
Reason: Q.850;cause=1
Content-Length: 0

*Oct 21 22:32:12.250: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:2051169760388*6678770@XX.XX.XX.XX:5060 SIP/2.0
Via: SIP/2.0/UDP XX.XX.XX.XX:5060;branch=z9hG4bKa8aeeae7d
From: "Nadeem'Phone" <sip:5000@XX.XX.XX.XX>;tag=13126~eada4422-7620-4109-867b-63b7c5eb269c-39467100
To: <sip:2051169760388*6678770@XX.XX.XX.XX>;tag=1658B18-D2A
Date: Wed, 21 Oct 2015 15:45:31 GMT
Call-ID: c11ca500-6271b31b-45-cb64d0a@XX.XX.XX.XX
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: presence, kpml
Content-Length: 0

Br,
nadeem

[jamize]

Thanks for testing Nadeem Ahmed. We were able to get it working.  It ended up being on the vendor side.  They weren't accepting the string.  Thank you for testing.

[Nadeem Ahmed · Accepted solution]

You are welcome Jeff, Glad issue found and isolated.

Br,
Nadeem

P.S Please rate for all useful Post.