Digital interface selection based for outgoing dial-peer
I've been googling a lot but can't find anymore a solution to this problem (even if I already solved it in the past but can't remember how).
Scenario: two entities are using the same CUCM (8.0) and the same gateway. They both use 0 to dial out. But depending of the entities, one has to go out through a PRI and one has to go out through a BRI (both attached to the unique gateway).
I created 2 CSS (customer1_css and customer2_css) and
4 partitions (customer1_inside_partition, customer1_outgoing_partition, customer2_inside_partition and customer2_outgoing_partition).
In CSS customer1_css, I added customer1_inside_partition, customer1_outgoing_partition, customer2_inside_partition
In CSS customer2_css, I added customer1_inside_partition, customer2_inside_partition and customer2_outgoing_partition.
I have two route pattern that starts with 0 (to dial out):
- one is on partition customer1_outgoing_partition and add 888 prefix
- one is on partition customer2_outgoing_partition and add 999 prefix
When the gateway receives 8880xxxxx, it forwards it to the PRI and when it receives 9990xxxxx it forwards it to BRI. Looks like good.
But, people on CSS1 can call people on CSS2 but not the opposite. Is there anything wrong with this setup of is there an easier way to proceed?
There is nothing wrong with it, and this is a method I have used.
As to the internal partition/CSS, is it a requirement to block phones from calling each other as well? If it is not and you want to allow them to dial each other simply assign all phones to common partition which is listed under both CSSes.
Les stations de radio en ligne sont devenues l'une des formes de partage des médias les plus populaires dans la ecouter radio en ligne société d'aujourd'hui. La radio Internet est maintenant disponible sur tous les principaux modems de câbles et sans fil ...
This document describes the details about the Cisco Collaboration Endpoint software upgrade error “File too large”, and guides through the possible workarounds to upgrade the endpoint to the desired version.
we have recently announced a new Webex Events service with a best-in-class virtual event experience that is video-centric, intelligent, and simple to use.
Some highlights (features of new Webex Events that were not there with existing/c...
The purpose of this document is to present the different troubleshooting steps to take when some service from the Cisco IM & Presence Service Server have not started gracefully.
The States of a service
The IM&P ...
This event had place on Tuesday 20th, April 2021 at 10hrs PDT
What is the Real-Time Monitoring Tool (RTMT) and how do I use it? In addition to an overview of the components of the tool and the interface, attendees learned how to use ...