02-26-2025 08:24 AM
Our SBC provider for our SIP Trunks is now allowing us to pass "any" 10 digits through their network. In the past we could only pass 10 digit DIDs that we owned within the SBC. We are a govt agency and for some departments we use multiple common DIDs as an External Mask and which we have a translation pattern in place to point to a recording that the number cannot be reached.
For instance my DN 12345 has an External mask or 310-331-1000 and internal calls still display all correct information cluster wide when making an ONnet call.
Currently if we have to forward a call, we have to use a Forwarding CSS to allow the call to go through and pass and insert an allowed number that will pass through the SBC network. What I have learned so far is that in order to make the External mask to work we have to change the Route lists setting from default to ON for the outbound calls that we forward off net to allow the call to complete. Now in doing this we can pass any digits. The issue we are running into is now on internal calls we are seeing the External caller mask instead of the DN info. When we change the forward all CSS setting to our normal outbound CSS the caller ID that is presented is only 5 digits to the far end customer for example they see +1 (123)45.
Our system consists of 3 clusters and each cluster has 3 nodes. CUCM Version 12.5.1.21900-29 Yes we plan on upgrading to 15 soon.
02-26-2025 10:30 AM
The CSS used for call forward has no function in relation to calls from the phone. To better understand your setup it would be useful if you could do a DNA with the respective CSS set to be used and take some screenshots from your setup that pertains to this.
02-26-2025 11:49 AM
When the call is set up like with the Forward all CSS set to CSS SIP 3 Nationwide we only receive +1(747)76 as the caller ID on the receiving end.
When the Forwarding all CSS is changed to this Forward & SNR CSS the Caller ID works as it should. Where the RL inserts DID to allow call through network.
02-26-2025 12:13 PM - edited 02-26-2025 01:00 PM
When you say internal calls are affected by EPNM do you mean that they are also going via the call forward, ie it’s not a direct call? Also is it intra cluster calls or inter cluster where you’re seeing EPNM applied on internal calls?
02-26-2025 02:12 PM - edited 02-26-2025 02:17 PM
Roger,
It happens when we change the route list Calling Party Transformation EPNM from default to on for our InterCluster Trunks ICT.
02-26-2025 09:36 PM
Why are you changing that on the ICT RL/RG? You’d normally have this set on the RL/RG level for the connection(s) to the PSTN. Is there something in your system landscape that requires you to do that?
02-26-2025 11:54 AM
sorry this one didnt upload for some reason
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide