3) On the H.323 MUM_GW registered in CUCM, navigate to the Inbound Calls and set the Inbound Significant Digits to 4 (instead of All), now this would enable the call to get routed and the HQ_MUM_PH1 (EXt. 5001) would ring and the display would show 2226341111, we need to change the calling number on the display to appear as a local number with 8 digits (26341111), this is called localization....
4) Go to the Inbound Calling Party Settings on the Device Pool of the gateway receiving the call and configure the Calling party prefix for National to +91, for Subscriber as +9122 and for International as +, this would prefix the calling number with the corresponding values depending on the Number type received. so in our case the national number of 2226341111 would become +912226341111 (this is what we want should appear in our missed calls, bingo!!!) and this is called globalizing the number.
5) Now our display would show us +912226341111 but we want it to show 26341111, so we basically need to strip the +9122, to do this create a Calling Party Transformation Pattern as
Pattern Match: \+9122.XXXXXXXX, strip off the predot from the discard digits option at the bottom of the page and assign this Calling Party Tranformation Pattern to a partition (lets say PT_XFORM_CALLING) that is accessible to the CSS_CALLING_PARTY_TRANSFORMATION CSS and this CSS would then have to be assigned to the Device Pool Settings under the Device Mobility Related Settings (Calling Party Transformation CSS).
So when the call comes in to the gateway, the calling number gets prefixed with a +91 (since we added this as the prefix for calling numbers with the National Number Type underr our Device Pool Inbound Calling Party Settings) and the transformed calling number of +912226341111 then gets matched to the Calling Party Transformation Pattern of \+9122.XXXXXXXX which was added to the Calling Party Transformation CSS under the Device Mobility Related Info in the Device Pool and so the calling number further gets transformed to appear on the ip phone display as 26341111 which is what we want and the missed calls would show the number after the Incoming Calling Party Settings change and would not take the Calling Party Transformation CSS into account.
So you finally have the number appearing as local (8 digits, Localized Number) on the display of the phone and as E.164 format (i.e. +912226341111) on the missed calls (Globalized number)....
To route the Missed Calls number out (i.e. +912226341111), just create a Route Pattern with \+9122.XXXXXXXX and route it out the MUM_GW after applying "Discard Digits: Predot".
4) Go to the Inbound Calling Party Settings on the Device Pool of the gateway receiving the call and configure the Calling party prefix for National to +91, for Subscriber as +9122 and for International as +, this would prefix the calling number with the corresponding values depending on the Number type received. so in our case the national number of 2226341111 would become +912226341111 (this is what we want should appear in our missed calls, bingo!!!) and this is called globalizing the number.
5) Now our display would show us +912226341111 but we want it to show 26341111, so we basically need to strip the +9122, to do this create a Calling Party Transformation Pattern as
Pattern Match: \+9122.XXXXXXXX, strip off the predot from the discard digits option at the bottom of the page and assign this Calling Party Tranformation Pattern to a partition (lets say PT_XFORM_CALLING) that is accessible to the CSS_CALLING_PARTY_TRANSFORMATION CSS and this CSS would then have to be assigned to the Device Pool Settings under the Device Mobility Related Settings (Calling Party Transformation CSS).
So when the call comes in to the gateway, the calling number gets prefixed with a +91 (since we added this as the prefix for calling numbers with the National Number Type underr our Device Pool Inbound Calling Party Settings) and the transformed calling number of +912226341111 then gets matched to the Calling Party Transformation Pattern of \+9122.XXXXXXXX which was added to the Calling Party Transformation CSS under the Device Mobility Related Info in the Device Pool and so the calling number further gets transformed to appear on the ip phone display as 26341111 which is what we want and the missed calls would show the number after the Incoming Calling Party Settings change and would not take the Calling Party Transformation CSS into account.
So you finally have the number appearing as local (8 digits, Localized Number) on the display of the phone and as E.164 format (i.e. +912226341111) on the missed calls (Globalized number)....
To route the Missed Calls number out (i.e. +912226341111), just create a Route Pattern with \+9122.XXXXXXXX and route it out the MUM_GW after applying "Discard Digits: Predot".
No comments:
Post a Comment