Hi Support Community
I have 2 queries 1 regarding Called number display on Cisco IP phones on calls destined for the ISDN. The 2nd relates to Calling number CLI for outbound PSTN calls. At this stage im not sure if it is a bug/fault, an issue with the telco, CUCM configuration or Gateway configuration.
Query 1 - Called Number Display
Globalisation is used for outbound calls. When a call is placed to an MGCP gateway a translation pattern manipulates the called number to E164 so 901234112233 is translated to +441234112233. This number is then displayed on the IP phone display whilst connecting and connected ( although number is localised at the gateway ) and this is what we want. However when the same is done with a H323 gateway when the number is dialled so 901234112233 the display immediatley changes to +441234112233 but as soon as ringback starts the display has the localised number as it would be sent out of the gateway so 01234112233.
Query 2 - Calling Number CLI
Globalisation is used for outbound calls in the UK. All calls are succesful and calling and called numbers are manipulated as expected except for 1 particular scenario. Most phones have a full UK 11 digit mask so for example 0123411XXXX. When a call is made a translation pattern is used to manipulate the calling number with settings 'use calling number external mask' , the mask is set to 10 wildcard digits XXXXXXXXXX and a prefix +44. So the calling number becomes +441234112233. This is correct and a 'calling party transformation mask' is used on the CUCM gateway config to match \+44.!. and localise the number back to 01234112233. The MGCP gateway is then set to restrict CLI on the port and the number is sent as unknown. All works exactly as we want it to work.
Now the issue is when an IP phone has a mask less than the 10 wildcard digits in the translation pattern ( public phones, non DDI phones etc us 5 digits with no mask so the mask will be the 5 digit extension ). We have a catch on 'calling party transformation mask' configured as \+! and this should translate all unknown calling numbers so the public phones etc to our main number 012345888888, the CLI is then restricted on the MGCP voice port. However what happens is the outbound call is sent with a CLI of our main billing number and what we see on the gateway is no calling number in the ISDN q931 messages ( see attched ). So it seems if an IP phone has a mask less then the 10 digits is causes weird results.
Any help is appreciated.
Thanks, Carl Ratcliffe
With H323 gateway, the h225 signalling is going to send some info back to the CUCM telling the CUCM about any digit manipulation it is doing. Hence the reason why you see the localised number on the gateway showing on the IP phone. To prevent this from happening use the ff command:
no supplementary-service h225-notify cid-update.
Can you send the CUCM traces for a call from a non ddi phone? You are correct, there is no calling number sent to the gateway