[cisco-voip] CM routing calls based on facility IE

Schlotterer, Tommy tschlotterer at presidio.com
Fri May 24 15:15:36 EDT 2019


You could use a sip profile if you are using sip:

voice class sip-profiles 100
rule 1 request INVITE sip-header Diversion copy "<(..............)" u01
 rule 2 request INVITE sip-header To modify "sip:44085551234(.*)" "\u01\1"
 rule 3 request INVITE sip-header SIP-Req-URI modify "sip: 44085551234(.*)" "\u01\1"
 rule 4 request INVITE sip-header Diversion remove

Thanks

Tommy

From: cisco-voip <cisco-voip-bounces at puck.nether.net> On Behalf Of Ovidiu Popa
Sent: Friday, May 24, 2019 2:53 PM
To: cisco-voip <cisco-voip at puck.nether.net>
Subject: [cisco-voip] CM routing calls based on facility IE

EXTERNAL EMAIL




Hello everyone

Does anyone know if CUCM is capable of routing calls based on the information in the ISDN Facility IE ?

We tested our provider's call failover scenario and we have the following issue :
- The operator enables the failover
- All calls from our primary site A to our secondary site B
- All calls received on site B have the same value in the Called Party Number field - the unique number identifying the site B. The number that was initially dialed on site A is now placed in the facility IE.

According to  ETS 300 196-1 the Facility Element is used only for supplementary services not for routing calls.

11.2.2.1 Facility
The purpose of the Facility information element is to carry components. For the purposes of this ETS these components are used to control supplementary services.

So my question is: can CUCM route calls based on the Facility IE ?

Thanks for any assistance.

Ovidiu



Tommy Schlotterer | Systems Engineer - Collaboration
Presidio (NASDAQ: PSDO) | presidio.com<http://presidio.com>
20 N Saint Clair 3rd Floor, Toledo, OH 43604
D: 419.214.1415 | C: 419.706.0259 | tschlotterer at presidio.com<mailto:tschlotterer at presidio.com>





This message w/attachments (message) is intended solely for the use of the intended recipient(s) and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments. Please be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20190524/cf8ba6f2/attachment.htm>


More information about the cisco-voip mailing list