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

[Lelio Fulgenzi]

MGCP  For EVER!

---
Lelio Fulgenzi, B.A. | Senior Analyst
Computing and Communications Services | University of Guelph
Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1
519-824-4120 Ext. 56354 | lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>

www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> | @UofGCCS on Instagram, Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

From: cisco-voip <cisco-voip-bounces at puck.nether.net> On Behalf Of NateCCIE
Sent: Friday, May 24, 2019 3:46 PM
To: Ovidiu Popa <ovi.popa at gmail.com>
Cc: cisco-voip <cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] CM routing calls based on facility IE

Friends don’t let friends use MGCP.  You can still use PRI and use SIP between the GW and CUCM.

Sent from my iPhone

On May 24, 2019, at 1:24 PM, Ovidiu Popa <ovi.popa at gmail.com<mailto:ovi.popa at gmail.com>> wrote:
Hi Tommy

Good suggestion but I forgot to mention that we are using MGCP.

Thanks,
Ovidiu

On Fri, May 24, 2019 at 9:15 PM Schlotterer, Tommy <tschlotterer at presidio.com<mailto:tschlotterer at presidio.com>> wrote:
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<mailto: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<mailto: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.
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20190524/521ce2a5/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 1297 bytes
Desc: image001.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20190524/521ce2a5/attachment.png>