Routing calls based on calling party number

[Rémi]

Hi !

Due to a change of attendant console solution I have (if it is possible) to route a call flow based on calling party number.

Actual call flow :
Fire alarm (call +32 4 1234567) > PSTN > ISR Cisco > Call Manager v12.0 > (old) attendant console Reception [general number]

New call flow :
Fire alarm (call +32 4 1234567) > PSTN > ISR Cisco > Call Manager v12.0 > (new) attendant console Reception [new queue number]

So the goal is to route the calls from fire alarms to a new internal number [queue in attendant console] without change the called party number in each fire alarm. 20 fire alarms involved in 20 differents remote site.

Thanks in advance

Rémi

[Rémi]

.

[Rémi]

.

[TONY SMITH]

Are you trying to do this within a CUBE, on CUCM or on CME?   

In CUCM you can use the "Route Next Hop By Calling Party Number" option within a translation pattern.  It's a bit fiddly but to summarise you create a translation to match the dialled number, then it's CSS looks for matches based on the Calling Number rather than dialled number. 

[Rémi · Accepted solution]

Thanks for your response TONY. That help me to find a new google search way :-)

Procedure that I did :

-0-
Create a Partition named "P_Internal"
Create a Calling Search space "CSS_Internal"
-> Assign "P_Internal" to "CSS_Internal"
-> Assign "P_Internal" to each end user's Directory Number

-1-
Create a Partition named "P_Accept_All"
Create a Calling Search Space named "CSS_SiteName_VGW"
-> Assign "P_Accept_All" to "CSS_SiteName_VGW"

-2-
Create a Partition named "P_route_calls_based_on_calling_party"
Creat a Calling Search Space named "CCS_route_calls_based_on_calling_party"
-> Assign "P_route_calls_based_on_calling_party" to "CCS_route_calls_based_on_calling_party"

/!\ Ensure that Gateway CSS should not have any other Partitions that is being used by Directory Numbers, else the calls will be routed to the Directory Numbers /!\
/!\ So in this exemple "CSS_SiteName_VGW" doesn't have "P_Internal" assigned /!\

-3-
Assign "CSS_SiteName_VGW" in Trunks and/or Gateways for Inboud Calls

-4-
Create a new Translation Pattern
* Translation Pattern : !
* Partition : P_Accept_All
* Description : Accept all calls from Voice Gateway
* Calling search space : "CCS_route_calls_based_on_calling_party"
* Route Next Hop By Calling Party : Check mark

-5-
Create a new Translation Pattern
* Translation Pattern : !
* Partition : P_route_calls_based_on_calling_party
* Description : Accept unspecified calls
* Calling search space : "CSS_Internal"
* Route Next Hop By Calling Party : Uncheck box

-6-
Create a new Translation Pattern
-> In this exemple, for a specific calling party number (e.g. 0032 123456)
* Translation Pattern : 0032123456
* Partition : P_route_calls_based_on_calling_party
* Description : Specific route for calling 0032123456
* Calling search space : "CSS_Internal"
* Route Next Hop By Calling Party : Uncheck box
* Prefix Digits (Outgoing Calls) : *99

-7-
Create a new Translation Pattern
-> In this exemple, to route call to 92555 only if calling party is 0032123456 and called party is 1111 (where 1111 is e.g. general number)
* Translation Pattern : *99.1111
* Partition : P_route_calls_based_on_calling_party
* Description : Specific route for calling 0032123456
* Calling search space : "CSS_Internal"
* Route Next Hop By Calling Party : Uncheck box
* Discard Digits : PreDot
* Called Party Transform Mask : 92555

-8-
Create a new Translation Pattern
-> In this exemple, to route via "normal way" all other call
* Translation Pattern : *99.!
* Partition : P_route_calls_based_on_calling_party
* Description : Normal way for specific route
* Calling search space : "CSS_Internal"
* Route Next Hop By Calling Party : Uncheck box
* Discard Digits : PreDot