Re: [OSL | CCIE_Voice] Digit Manipulation on H323
Hi, You can get digit manipulation to shown on the display of a IP Phone for calls to a H.323 gw just as with an MGCP gw. Add this to you H.323 config, voice service voip no supplementary-service h225-notify cid-update Sincerely Roger Källberg CCIE #26199 (Voice) Consultant Cygate AB Från: Goran Selthofer [seltho...@gmail.com] Skickat: den 17 oktober 2010 20:54 Till: Cristobal Priego Kopia: ccie_voice@onlinestudylist.com Ämne: Re: [OSL | CCIE_Voice] Digit Manipulation on H323 Hi C.P, Digit manipulation will be done on CUCM and will be sent to H323 as well, and the preference would be on the manipulations done within RL rather than on RP. So, i.e. RP is 91608.[2-9]XX and - if you put pre-dot and prefix 608 under RP, - and then you also do pre-dot and prefix 9 for specific RG (for your h323 gw) under RL, then your h323 gw will receive 9[2-9]XX hence, dial-peer pots on your h323 gw needed to terminate this call should have the same/similar destination-pattern configured, i.e: dial-peer voice 9 pots destination-pattern 9[2-9]..$ port 0/1/0:23 Now, the real trick comes if you want to actually influence your calling phone LCD digit presentations of DNIS (so, not ANI on the receiving end, but the actual dialed number on the calling end being presented on your phone from which you are dialing those digits - this is where the difference between mgcp and h323 gw can be seen). mgcp will present whatever manipulations you've done using RP (will not present back to calling phone LCD what you have done withing RG/RL manipulations though it will use those manipulations to send to the GW). however, in case of h323 gw, manipulations on DNIS done withing RG/RL will be also presented back to calling phone LCD. Now, since that is H323, you can still have one more chance to do your digits manipulations and influence back presenting of dialed digits to calling phone - voice transformation rules/profiles attached to pots dial-peer (or forward-digits under dial-peer but that one will not influence LCD DNIS presentation on the calling phone) i.e. if for above example we want to actually show 9 in front of local number, we can just put 'forward-digits 7' under above pots and that's it. dial-peer voice 9 pots destination-pattern 9[2-9]..$ port 0/1/0:23 forward-digits 7 But, if we would like to show ONLY local number, without leading 9 back to the caller on his ip phone LCD, then we would have to strip that 9 inside voice translation-rule, i.e: voice translation-rule 9 rule 1 /^9\([2-9]..$\)/ /\1/ p any sub t any sub voice translation-profile 9 translate called 9 and then add that to above dp: dial-peer voice 9 pots translation-profile out 9 destination-pattern 9[2-9]..$ port 0/1/0:23 so this will result in showing only 7 digits back to LCD of the calling phone. (if dialed number was 91234567, it will show back only 1234567). here, you can also include forward-digits as well, but translation-profile will still have precedence dial-peer voice 9 pots translation-profile out 9 destination-pattern 9[2-9]..$ port 0/1/0:23 forward 7 in both cases you are sending 7 digits to PSTN, just the difference is what you will present back to the caller who actually dialed this number. and that is the difference with mgcp, as you don't have that extra step to manipulate DNIS - all needs to be done on the CUCM withing RP, RG of RL or CalledPartTransformationPattern attached to outgoing mgcp gw. hope this will give you some clues how it works... cheers, G. On Sun, Oct 17, 2010 at 8:17 PM, Cristobal Priego cristobalpri...@gmail.commailto:cristobalpri...@gmail.com wrote: hello all, I'm working on the workbook 1 lab 5 and i noticed what when i do digit manipulation either on the RP, RL or by using transformation patterns, the changes aren't sent to the GW, if my protocol is H.323 usually I need to create some dial rules on the Voice Gateway when I'm using MGCP i have no problem i was wondering if there is a setting on the ccm that will allow ccm to send the digit manipulation to the GW or does it has to be manually done at the GW level ? could you please explain a bit for me thank you ___ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.comhttp://www.ipexpert.com ___ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
[OSL | CCIE_Voice] Digit Manipulation on H323
hello all, I'm working on the workbook 1 lab 5 and i noticed what when i do digit manipulation either on the RP, RL or by using transformation patterns, the changes aren't sent to the GW, if my protocol is H.323 usually I need to create some dial rules on the Voice Gateway when I'm using MGCP i have no problem i was wondering if there is a setting on the ccm that will allow ccm to send the digit manipulation to the GW or does it has to be manually done at the GW level ? could you please explain a bit for me thank you ___ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
Re: [OSL | CCIE_Voice] Digit Manipulation on H323
Hi C.P, Digit manipulation will be done on CUCM and will be sent to H323 as well, and the preference would be on the manipulations done within RL rather than on RP. So, i.e. RP is 91608.[2-9]XX and - if you put pre-dot and prefix 608 under RP, - and then you also do pre-dot and prefix 9 for specific RG (for your h323 gw) under RL, then your h323 gw will receive 9[2-9]XX hence, dial-peer pots on your h323 gw needed to terminate this call should have the same/similar destination-pattern configured, i.e: dial-peer voice 9 pots destination-pattern 9[2-9]..$ port 0/1/0:23 Now, the real trick comes if you want to actually influence your calling phone LCD digit presentations of DNIS (so, not ANI on the receiving end, but the actual dialed number on the calling end being presented on your phone from which you are dialing those digits - this is where the difference between mgcp and h323 gw can be seen). mgcp will present whatever manipulations you've done using RP (will not present back to calling phone LCD what you have done withing RG/RL manipulations though it will use those manipulations to send to the GW). however, in case of h323 gw, manipulations on DNIS done withing RG/RL will be also presented back to calling phone LCD. Now, since that is H323, you can still have one more chance to do your digits manipulations and influence back presenting of dialed digits to calling phone - voice transformation rules/profiles attached to pots dial-peer (or forward-digits under dial-peer but that one will not influence LCD DNIS presentation on the calling phone) i.e. if for above example we want to actually show 9 in front of local number, we can just put 'forward-digits 7' under above pots and that's it. dial-peer voice 9 pots destination-pattern 9[2-9]..$ port 0/1/0:23 forward-digits 7 But, if we would like to show ONLY local number, without leading 9 back to the caller on his ip phone LCD, then we would have to strip that 9 inside voice translation-rule, i.e: voice translation-rule 9 rule 1 /^9\([2-9]..$\)/ /\1/ p any sub t any sub voice translation-profile 9 translate called 9 and then add that to above dp: dial-peer voice 9 pots translation-profile out 9 destination-pattern 9[2-9]..$ port 0/1/0:23 so this will result in showing only 7 digits back to LCD of the calling phone. (if dialed number was 91234567, it will show back only 1234567). here, you can also include forward-digits as well, but translation-profile will still have precedence dial-peer voice 9 pots translation-profile out 9 destination-pattern 9[2-9]..$ port 0/1/0:23 forward 7 in both cases you are sending 7 digits to PSTN, just the difference is what you will present back to the caller who actually dialed this number. and that is the difference with mgcp, as you don't have that extra step to manipulate DNIS - all needs to be done on the CUCM withing RP, RG of RL or CalledPartTransformationPattern attached to outgoing mgcp gw. hope this will give you some clues how it works... cheers, G. On Sun, Oct 17, 2010 at 8:17 PM, Cristobal Priego cristobalpri...@gmail.com wrote: hello all, I'm working on the workbook 1 lab 5 and i noticed what when i do digit manipulation either on the RP, RL or by using transformation patterns, the changes aren't sent to the GW, if my protocol is H.323 usually I need to create some dial rules on the Voice Gateway when I'm using MGCP i have no problem i was wondering if there is a setting on the ccm that will allow ccm to send the digit manipulation to the GW or does it has to be manually done at the GW level ? could you please explain a bit for me thank you ___ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com ___ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
Re: [OSL | CCIE_Voice] Digit Manipulation on H323
thank you very much it really make sense and what would happen to the call type ? if i use a called party transformation pattern to set the called type to: national, subscriber, intl, on the MGCP gateway it's no problem the call is sent out on the PRI with the proper digit manipulation and the proper call type on the other hand on H323. stripping digits from ccm are passed to the h323 gw, but that's it, no call type at all this is when the translation rules comes in place, right ? 2010/10/17 Goran Selthofer seltho...@gmail.com Hi C.P, Digit manipulation will be done on CUCM and will be sent to H323 as well, and the preference would be on the manipulations done within RL rather than on RP. So, i.e. RP is 91608.[2-9]XX and - if you put pre-dot and prefix 608 under RP, - and then you also do pre-dot and prefix 9 for specific RG (for your h323 gw) under RL, then your h323 gw will receive 9[2-9]XX hence, dial-peer pots on your h323 gw needed to terminate this call should have the same/similar destination-pattern configured, i.e: dial-peer voice 9 pots destination-pattern 9[2-9]..$ port 0/1/0:23 Now, the real trick comes if you want to actually influence your calling phone LCD digit presentations of DNIS (so, not ANI on the receiving end, but the actual dialed number on the calling end being presented on your phone from which you are dialing those digits - this is where the difference between mgcp and h323 gw can be seen). mgcp will present whatever manipulations you've done using RP (will not present back to calling phone LCD what you have done withing RG/RL manipulations though it will use those manipulations to send to the GW). however, in case of h323 gw, manipulations on DNIS done withing RG/RL will be also presented back to calling phone LCD. Now, since that is H323, you can still have one more chance to do your digits manipulations and influence back presenting of dialed digits to calling phone - voice transformation rules/profiles attached to pots dial-peer (or forward-digits under dial-peer but that one will not influence LCD DNIS presentation on the calling phone) i.e. if for above example we want to actually show 9 in front of local number, we can just put 'forward-digits 7' under above pots and that's it. dial-peer voice 9 pots destination-pattern 9[2-9]..$ port 0/1/0:23 forward-digits 7 But, if we would like to show ONLY local number, without leading 9 back to the caller on his ip phone LCD, then we would have to strip that 9 inside voice translation-rule, i.e: voice translation-rule 9 rule 1 /^9\([2-9]..$\)/ /\1/ p any sub t any sub voice translation-profile 9 translate called 9 and then add that to above dp: dial-peer voice 9 pots translation-profile out 9 destination-pattern 9[2-9]..$ port 0/1/0:23 so this will result in showing only 7 digits back to LCD of the calling phone. (if dialed number was 91234567, it will show back only 1234567). here, you can also include forward-digits as well, but translation-profile will still have precedence dial-peer voice 9 pots translation-profile out 9 destination-pattern 9[2-9]..$ port 0/1/0:23 forward 7 in both cases you are sending 7 digits to PSTN, just the difference is what you will present back to the caller who actually dialed this number. and that is the difference with mgcp, as you don't have that extra step to manipulate DNIS - all needs to be done on the CUCM withing RP, RG of RL or CalledPartTransformationPattern attached to outgoing mgcp gw. hope this will give you some clues how it works... cheers, G. On Sun, Oct 17, 2010 at 8:17 PM, Cristobal Priego cristobalpri...@gmail.com wrote: hello all, I'm working on the workbook 1 lab 5 and i noticed what when i do digit manipulation either on the RP, RL or by using transformation patterns, the changes aren't sent to the GW, if my protocol is H.323 usually I need to create some dial rules on the Voice Gateway when I'm using MGCP i have no problem i was wondering if there is a setting on the ccm that will allow ccm to send the digit manipulation to the GW or does it has to be manually done at the GW level ? could you please explain a bit for me thank you ___ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com ___ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
Re: [OSL | CCIE_Voice] Digit Manipulation on H323
To set Called and Calling type on H323 GW it is preferred to use voice-translation rules on the gateway so that if you go into srst you dont have to do it again. However if no srst you can set it in CUCM. HTH, Prashant On Sun, Oct 17, 2010 at 3:02 PM, Cristobal Priego cristobalpri...@gmail.com wrote: thank you very much it really make sense and what would happen to the call type ? if i use a called party transformation pattern to set the called type to: national, subscriber, intl, on the MGCP gateway it's no problem the call is sent out on the PRI with the proper digit manipulation and the proper call type on the other hand on H323. stripping digits from ccm are passed to the h323 gw, but that's it, no call type at all this is when the translation rules comes in place, right ? 2010/10/17 Goran Selthofer seltho...@gmail.com Hi C.P, Digit manipulation will be done on CUCM and will be sent to H323 as well, and the preference would be on the manipulations done within RL rather than on RP. So, i.e. RP is 91608.[2-9]XX and - if you put pre-dot and prefix 608 under RP, - and then you also do pre-dot and prefix 9 for specific RG (for your h323 gw) under RL, then your h323 gw will receive 9[2-9]XX hence, dial-peer pots on your h323 gw needed to terminate this call should have the same/similar destination-pattern configured, i.e: dial-peer voice 9 pots destination-pattern 9[2-9]..$ port 0/1/0:23 Now, the real trick comes if you want to actually influence your calling phone LCD digit presentations of DNIS (so, not ANI on the receiving end, but the actual dialed number on the calling end being presented on your phone from which you are dialing those digits - this is where the difference between mgcp and h323 gw can be seen). mgcp will present whatever manipulations you've done using RP (will not present back to calling phone LCD what you have done withing RG/RL manipulations though it will use those manipulations to send to the GW). however, in case of h323 gw, manipulations on DNIS done withing RG/RL will be also presented back to calling phone LCD. Now, since that is H323, you can still have one more chance to do your digits manipulations and influence back presenting of dialed digits to calling phone - voice transformation rules/profiles attached to pots dial-peer (or forward-digits under dial-peer but that one will not influence LCD DNIS presentation on the calling phone) i.e. if for above example we want to actually show 9 in front of local number, we can just put 'forward-digits 7' under above pots and that's it. dial-peer voice 9 pots destination-pattern 9[2-9]..$ port 0/1/0:23 forward-digits 7 But, if we would like to show ONLY local number, without leading 9 back to the caller on his ip phone LCD, then we would have to strip that 9 inside voice translation-rule, i.e: voice translation-rule 9 rule 1 /^9\([2-9]..$\)/ /\1/ p any sub t any sub voice translation-profile 9 translate called 9 and then add that to above dp: dial-peer voice 9 pots translation-profile out 9 destination-pattern 9[2-9]..$ port 0/1/0:23 so this will result in showing only 7 digits back to LCD of the calling phone. (if dialed number was 91234567, it will show back only 1234567). here, you can also include forward-digits as well, but translation-profile will still have precedence dial-peer voice 9 pots translation-profile out 9 destination-pattern 9[2-9]..$ port 0/1/0:23 forward 7 in both cases you are sending 7 digits to PSTN, just the difference is what you will present back to the caller who actually dialed this number. and that is the difference with mgcp, as you don't have that extra step to manipulate DNIS - all needs to be done on the CUCM withing RP, RG of RL or CalledPartTransformationPattern attached to outgoing mgcp gw. hope this will give you some clues how it works... cheers, G. On Sun, Oct 17, 2010 at 8:17 PM, Cristobal Priego cristobalpri...@gmail.com wrote: hello all, I'm working on the workbook 1 lab 5 and i noticed what when i do digit manipulation either on the RP, RL or by using transformation patterns, the changes aren't sent to the GW, if my protocol is H.323 usually I need to create some dial rules on the Voice Gateway when I'm using MGCP i have no problem i was wondering if there is a setting on the ccm that will allow ccm to send the digit manipulation to the GW or does it has to be manually done at the GW level ? could you please explain a bit for me thank you ___ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com ___ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com ___ For more information regarding
Re: [OSL | CCIE_Voice] Digit Manipulation on H323
thank you all for your comments I've been debugging the gateway i have digit manipulation on the rp, rl. I also have a called pattern transformation css applied to the h323 gateway i've reset the GW multiple times however when i make the call this is what i see Exclusive, Channel 1 Display i = 'HQ Phone 2' Calling Party Number HQ-RTR(config-gk)# i = 0x0081, '12123945002' Plan:Unknown, Type:Unknown Called Party Number i = 0x80, '16178632683' Plan:Unknown, Type:Unknown My calling party transformation CSS is being hit by the GW 10/17/2010 16:01:47.979 CCM|SPROC DATransformMatch - matchNumber [5002]transformCSSPkid [c85a253f-f88d-7fbb-50b0-ff8aaacde5c3] transformationCss [gw-hq-pt] patternUsage [15] paternNodeID [b071ad82-eaf4-c3c5-09df-6acba1ad0832] OutpulsedNum.nd [+12123945002] tn [2] pi [1] npi [0]|CLID::StandAloneClusterNID::10.10.210.11LVL::ArbitraryMASK::0800 however i didn't see the called party transformation pattern being hit and i can't get the call type to work properly nor the + dialing without Dialing Rules with dialing rules works great however i was wondering if it could be done from CUCM 2010/10/17 Prashant Patel prashantpatel...@gmail.com To set Called and Calling type on H323 GW it is preferred to use voice-translation rules on the gateway so that if you go into srst you dont have to do it again. However if no srst you can set it in CUCM. HTH, Prashant On Sun, Oct 17, 2010 at 3:02 PM, Cristobal Priego cristobalpri...@gmail.com wrote: thank you very much it really make sense and what would happen to the call type ? if i use a called party transformation pattern to set the called type to: national, subscriber, intl, on the MGCP gateway it's no problem the call is sent out on the PRI with the proper digit manipulation and the proper call type on the other hand on H323. stripping digits from ccm are passed to the h323 gw, but that's it, no call type at all this is when the translation rules comes in place, right ? 2010/10/17 Goran Selthofer seltho...@gmail.com Hi C.P, Digit manipulation will be done on CUCM and will be sent to H323 as well, and the preference would be on the manipulations done within RL rather than on RP. So, i.e. RP is 91608.[2-9]XX and - if you put pre-dot and prefix 608 under RP, - and then you also do pre-dot and prefix 9 for specific RG (for your h323 gw) under RL, then your h323 gw will receive 9[2-9]XX hence, dial-peer pots on your h323 gw needed to terminate this call should have the same/similar destination-pattern configured, i.e: dial-peer voice 9 pots destination-pattern 9[2-9]..$ port 0/1/0:23 Now, the real trick comes if you want to actually influence your calling phone LCD digit presentations of DNIS (so, not ANI on the receiving end, but the actual dialed number on the calling end being presented on your phone from which you are dialing those digits - this is where the difference between mgcp and h323 gw can be seen). mgcp will present whatever manipulations you've done using RP (will not present back to calling phone LCD what you have done withing RG/RL manipulations though it will use those manipulations to send to the GW). however, in case of h323 gw, manipulations on DNIS done withing RG/RL will be also presented back to calling phone LCD. Now, since that is H323, you can still have one more chance to do your digits manipulations and influence back presenting of dialed digits to calling phone - voice transformation rules/profiles attached to pots dial-peer (or forward-digits under dial-peer but that one will not influence LCD DNIS presentation on the calling phone) i.e. if for above example we want to actually show 9 in front of local number, we can just put 'forward-digits 7' under above pots and that's it. dial-peer voice 9 pots destination-pattern 9[2-9]..$ port 0/1/0:23 forward-digits 7 But, if we would like to show ONLY local number, without leading 9 back to the caller on his ip phone LCD, then we would have to strip that 9 inside voice translation-rule, i.e: voice translation-rule 9 rule 1 /^9\([2-9]..$\)/ /\1/ p any sub t any sub voice translation-profile 9 translate called 9 and then add that to above dp: dial-peer voice 9 pots translation-profile out 9 destination-pattern 9[2-9]..$ port 0/1/0:23 so this will result in showing only 7 digits back to LCD of the calling phone. (if dialed number was 91234567, it will show back only 1234567). here, you can also include forward-digits as well, but translation-profile will still have precedence dial-peer voice 9 pots translation-profile out 9 destination-pattern 9[2-9]..$ port 0/1/0:23 forward 7 in both cases you are sending 7 digits to PSTN, just the difference is what you will present back to the caller who actually dialed this number. and that is the difference with
