We are trying to fixup ANI in the Directories (Missed, Received). It should be possible to prepend [9,91,9011] to ANI with transformation patterns applied at the CM gateway based on the area code and country code (if call is local it gets 9 other get 91, 0 gets 9011). This is working on a softphone but not ip phones.
The next step would be to localize the ANI presentation to the display (strip the 9) if possible but not affect the call logs.
Does someone have this or something similar working? We are a mixed mgcp/h323 environment so we are looking to keep this in the CM.
Yes this is possible; however, most people who do this loc/glob configuration are using an E.164 dial plan instead. In your case, you can likely set the incoming call transformation masks at the service parameter level since it should apply equally at all ingress gateways. After that you add a partition, CSS, and Calling Party Transformation Patterns that strip the 9. Apply that CSS to the device pool or manually to the device.
yeah I know Globalization usually refers to the use of E.164. we are not prepared to moved to that quite yet. You refered to a service parameter that needs to be set? Have this working on a softphone but does not work on the ip phones. Is this parameter related to this?
The Incoming Calling Party Prefix values exist at a service parameter (advanced), device pool, and gateway level. You can set it at any of the three. These will prefix digits to an incoming call from a gateway.
These patterns rely's on the Carrier sending the correct ISDN. For remote sites calls are coming over Analog FXO so there is no isdn information. To address this I was thinking on doing this with Transformation Patterns/CSS apllied at the gw and then using different transformations applied at the phone.
for local area codes (954XXXXXXX) transform to prefix 9
for [2-9]xx[2-9]xxxxxx prefix 91 (all other national numbers)
for local area codes (9.954XXXXXXX) transform to strip 9
for 9.1[2-9]xx[2-9]xxxxxx strip 9 (all other national numbers)
I am just curious to why this would present correct on softphone and not an IP Phone.
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...