I have configured a SIP Trunk between Cisco VCS-Control and CUCM V7.1.3 (1 Publisher, 2 Subscribers):
SIP: On / 5060 / TCP
Publisher: Failed to connect on 5060
Subscriber1: Active on 5060
Subscriber2: Active on 5060
(All CUCM Nodes are on the same subnet)
Relevant Search rules and transforms have been configured on VCS, Route Pattern and SIP Trunk have been configured on CUCM Pub, pattern confirmed using Dialled Digit Analyser.
Outstanding Issues are:
Dial Plan details:
IPT - #1XXXX
Video - 2XXXX
The video endpoints are SIP so i have had to base my search rules using %23 as opposed to # as it isn't a valid SIP character, not sure if this has any effect when presented to CUCM?
Check Device Pool in cucm and make sure your SIP trunk contains CUCM publisher in your CUCM call manager group.
and make sure CUCM service in pub is running, if not no need to use it in your rules.
the %23 is #, so thats normal.
I managed to resolve this issue with the assistance with Cisco TAC.
The issue was that Cisco VCS does not support the handling of the # character, this needs to be encoded to hexadecimal format of %23.
The IPT phone was registered to CUCM with a #, this meant the # character was being sent to the VCS in the SIP message headers and VCS was not decoding it.
I managed to find a 'workaround' for this, by disabling both 'remote-party-ID' and 'asserted-identity' on the CUCM SIP trunk pointing at Cisco VCS.
TAC also reported that an internal bug had been reported based on this:
(SIP Stack needs to escape # in SIP URI as per RFC 3261)
Resolved in following revisions: