Re: [OSL | CCIE_Voice] MVA partial match issue
I see, I have make sure my RDP CSS include the 4 digit ext. but still failed. On Sun, Apr 7, 2013 at 2:44 PM, William Bell b...@ucguerrilla.com wrote: Not quite. The RDP CSS is used by the MVA process in CUCM to make the final call routing decision. -- William Bell blog: http://ucguerrilla.com twitter: @ucguerrilla On Apr 7, 2013, at 3:46 PM, donny f wrote: yes i had specified it under service param, so far i only restart the MVA service in UCM/. I think this no need RDP css, as i only test MVA. When i press 4 ext , debug voip dialpeer show it hits the MVA number 5999. Here is how I understand , pls correct if this is not right. - when press 1 to call 4 digit, dial-peer voip in IOS router will match 5999 to CallManager VMA 5999 (under Media Resources). - after successfully in UCM MVA, it is up to CallManager VMA process to dial 4 digit (and no need CSS here) Tks d On Sun, Apr 7, 2013 at 12:40 PM, Barrera, Hugo hugo.barr...@nexusis.comwrote: It uses the RDP's css while snr uses the re-routing css. Did you also specify the MVA number in the service parameters? A peer had mentioned to me that the service may need to get restarted as well haven't tested it yet though. Regards, Hugo On Apr 6, 2013, at 8:38 PM, donny f f.faraday...@gmail.com wrote: hi Bill and others, I had put the MVA under Media Resources, however when i dial 4 digit ext, it said: the number you dial can't be reached. Questions: - when we use MVA to call 4 digit, are they use IOS dial-peer or RD css to call this 4 digit local ext - my partial match never work , i use 7 digit as match. any idea what missed? tks On Wed, Mar 27, 2013 at 5:46 AM, William Bell b...@ucguerrilla.com b...@ucguerrilla.com wrote: I have ran into a similar problem. In my case I would get a fast busy after entering the extension number followed by #. The issue was I neglected to provision Mobile Voice Access under Media Resources. On Tuesday, March 26, 2013, Barrera, Hugo wrote: Regarding MVA during my first attempt (real lab) I had it working except for when I dialed in and tried to call another 4-digit ext like SAPH1 or SBPH2 any ideas why that didn’t work? ** ** *Regards,*** *Hugo* ** ** *From:* ccie_voice-boun...@onlinestudylist.com [mailto: ccie_voice-boun...@onlinestudylist.com] *On Behalf Of *Justin Carney *Sent:* Monday, March 25, 2013 1:51 AM *To:* donny f *Cc:* ccie_voice@onlinestudylist.com, (ccie_voice@onlinestudylist.com); michael.se...@compucom.com; networksanitytoinsan...@gmail.com *Subject:* Re: [OSL | CCIE_Voice] MVA partial match issue ** ** You can have the rd with 7 digits only and without the 9 for pstn access - use either application dial rules (match 7 digits, prefix 9) or a translation pattern to modify the rd to match your existing local route pattern. I'm not sure if there's an MVA bug in this version of cucm, but its pretty easy to configure it so that you always have a full match since you will likely have only one rd. This is what I do for the lab. A real world (for nanp) example of MVA partial match would be using e164 address for all rd (+1 npa-nxx-) and set partial match to 10 or 7 depending on whether all sites receive inbound ani as 10d for local calls or if any sites receives only 7d. This would also work for lab, but takes extra steps if you aren't already required to use + dialing For partial match to work, the rd must be longer than the inbound ani (ani 7d and rd +11d). You cannot use partial match with an ani longer than the rd (ani 10d and rd 7d), in this case your options would be to apply inbound transformation on the gateway to make rd ani shorter (ie match the rd) or make your rd longer and manipulate outbound dnis to make it route. On Mar 25, 2013 2:00 AM, donny f f.faraday...@gmail.com wrote: hi, I config the Service parameter for MVA , using partial match 7 digit . However when I dial the RD using 7 digit ,it never works. seem like UCM only take Full match. I heard this is bug, Any suggestion for the work around if still want to use partial match ? d On Sun, Mar 17, 2013 at 9:58 AM, michael.se...@compucom.com wrote:*** * Greetings, I think you are doing everything right just need a few tweaks. Place a call from the PSTN line 2 to 3033300 and do debug isdn q931 on gateway. What digits do you see for the calling number. 7 or 10? If seeing 7 digits inbound change your Remote Destination Number to 525, without the 9. If you are seeing 10 digits inbound the NPA, NXX, TNTN change your remote destination number to XXX525, in other words match what you're seeing in the isdn debug for calling party and make that you're Remote Destination Number. Do NOT require the prefix of 9 on the Remote Destination Number. Also, under Remote Destination Information
Re: [OSL | CCIE_Voice] MVA partial match issue
Hi Donny, Partial/Complete match is NOT related to 4 digit dial. I thought you were asking about separate issue with matching remote destination. Let me ask you this, you're not trying to call the extension on the phone for which you have Remote Destination/Profile configured, are you? Sergey On Mon, Apr 8, 2013 at 1:38 AM, donny f f.faraday...@gmail.com wrote: hi sergey, yes my dial-peer for MVA that match the service parameter is there and it actually trigger it when i press 1 and 4 digit ext. Also CSS for GW and RDP seem include the 4 digit partition. When you said this : -- I know there are some bugs with partial match in early versions of CUCM 7.X, the workaround is to use complete match. Can you explain bit, how this complete/partial match related to failed 4 digit dial ? So far I always think if you can call MVA from PSTN and they prompt to enter PIN, then means partial/complete match is ok here Tks d On Sun, Apr 7, 2013 at 8:59 AM, Sergey Heyphets ser...@heyphets.comwrote: Hi Donny, When you dial 4 digit extension from the MVA, the IOS sends call to the MVA number defined under Media Resources, so you must have a dial-peer that matches that number and sends the call to the CUCM. The extension you've dialed is transfered in the Redirected number IE inside the SETUP message sent to the MVA number defined under media resources. Once the call gets to CUCM, it extracts the extension you've dialed from the Redirected Number IE and uses either Gateway CSS or RDP+Line CSS (depending on Service Parameters) to place the call to extension. So, if your call to extension doesn't work, you need to check that you have dial-peer that matches MVA number defined in Media Resources, the Service Params to see which CSS you use for MVA calls and then make sure that whatever CSS you use can reach that extension. I know there are some bugs with partial match in early versions of CUCM 7.X, the workaround is to use complete match. Sergey ___ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com http://www.platinumplacement.com/ ___ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com
Re: [OSL | CCIE_Voice] MVA partial match issue
hi Sergey, tks for reponse. I have the dial-peer to MVA number in IOS router. Because I am able to call the MVA and get the MVA prompt for pin from PSTN. Also the 4 digit extension do have partition. I also checked the CSS on the RDP/Line and GW, it should reach the 4 digit phones. Any idea what to check next? On Sun, Apr 7, 2013 at 8:59 AM, Sergey Heyphets ser...@heyphets.com wrote: Hi Donny, When you dial 4 digit extension from the MVA, the IOS sends call to the MVA number defined under Media Resources, so you must have a dial-peer that matches that number and sends the call to the CUCM. The extension you've dialed is transfered in the Redirected number IE inside the SETUP message sent to the MVA number defined under media resources. Once the call gets to CUCM, it extracts the extension you've dialed from the Redirected Number IE and uses either Gateway CSS or RDP+Line CSS (depending on Service Parameters) to place the call to extension. So, if your call to extension doesn't work, you need to check that you have dial-peer that matches MVA number defined in Media Resources, the Service Params to see which CSS you use for MVA calls and then make sure that whatever CSS you use can reach that extension. I know there are some bugs with partial match in early versions of CUCM 7.X, the workaround is to use complete match. Sergey ___ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com http://www.platinumplacement.com/ ___ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com
Re: [OSL | CCIE_Voice] MVA partial match issue
It uses the RDP's css while snr uses the re-routing css. Did you also specify the MVA number in the service parameters? A peer had mentioned to me that the service may need to get restarted as well haven't tested it yet though. Regards, Hugo On Apr 6, 2013, at 8:38 PM, donny f f.faraday...@gmail.commailto:f.faraday...@gmail.com wrote: hi Bill and others, I had put the MVA under Media Resources, however when i dial 4 digit ext, it said: the number you dial can't be reached. Questions: - when we use MVA to call 4 digit, are they use IOS dial-peer or RD css to call this 4 digit local ext - my partial match never work , i use 7 digit as match. any idea what missed? tks On Wed, Mar 27, 2013 at 5:46 AM, William Bell mailto:b...@ucguerrilla.comb...@ucguerrilla.commailto:b...@ucguerrilla.com wrote: I have ran into a similar problem. In my case I would get a fast busy after entering the extension number followed by #. The issue was I neglected to provision Mobile Voice Access under Media Resources. On Tuesday, March 26, 2013, Barrera, Hugo wrote: Regarding MVA during my first attempt (real lab) I had it working except for when I dialed in and tried to call another 4-digit ext like SAPH1 or SBPH2 any ideas why that didn’t work? Regards, Hugo From: ccie_voice-boun...@onlinestudylist.commailto:ccie_voice-boun...@onlinestudylist.com [mailto:ccie_voice-boun...@onlinestudylist.commailto:ccie_voice-boun...@onlinestudylist.com] On Behalf Of Justin Carney Sent: Monday, March 25, 2013 1:51 AM To: donny f Cc: ccie_voice@onlinestudylist.commailto:ccie_voice@onlinestudylist.com, (ccie_voice@onlinestudylist.commailto:ccie_voice@onlinestudylist.com); michael.se...@compucom.commailto:michael.se...@compucom.com; networksanitytoinsan...@gmail.commailto:networksanitytoinsan...@gmail.com Subject: Re: [OSL | CCIE_Voice] MVA partial match issue You can have the rd with 7 digits only and without the 9 for pstn access - use either application dial rules (match 7 digits, prefix 9) or a translation pattern to modify the rd to match your existing local route pattern. I'm not sure if there's an MVA bug in this version of cucm, but its pretty easy to configure it so that you always have a full match since you will likely have only one rd. This is what I do for the lab. A real world (for nanp) example of MVA partial match would be using e164 address for all rd (+1 npa-nxx-) and set partial match to 10 or 7 depending on whether all sites receive inbound ani as 10d for local calls or if any sites receives only 7d. This would also work for lab, but takes extra steps if you aren't already required to use + dialing For partial match to work, the rd must be longer than the inbound ani (ani 7d and rd +11d). You cannot use partial match with an ani longer than the rd (ani 10d and rd 7d), in this case your options would be to apply inbound transformation on the gateway to make rd ani shorter (ie match the rd) or make your rd longer and manipulate outbound dnis to make it route. On Mar 25, 2013 2:00 AM, donny f f.faraday...@gmail.commailto:f.faraday...@gmail.com wrote: hi, I config the Service parameter for MVA , using partial match 7 digit . However when I dial the RD using 7 digit ,it never works. seem like UCM only take Full match. I heard this is bug, Any suggestion for the work around if still want to use partial match ? d On Sun, Mar 17, 2013 at 9:58 AM, michael.se...@compucom.commailto:michael.se...@compucom.com wrote: Greetings, I think you are doing everything right just need a few tweaks. Place a call from the PSTN line 2 to 3033300 and do debug isdn q931 on gateway. What digits do you see for the calling number. 7 or 10? If seeing 7 digits inbound change your Remote Destination Number to 525, without the 9. If you are seeing 10 digits inbound the NPA, NXX, TNTN change your remote destination number to XXX525, in other words match what you're seeing in the isdn debug for calling party and make that you're Remote Destination Number. Do NOT require the prefix of 9 on the Remote Destination Number. Also, under Remote Destination Information make sure you are putting a tick in Mobile Phone checkbox and a tick in the Enable Mobile Connect checkbox. Otherwise your configuration looks good. Hope you find this helpful. Michael Sears CCIE 38404 Date: Sun, 17 Mar 2013 18:23:01 +0530 From: sanity insanity networksanitytoinsan...@gmail.commailto:networksanitytoinsan...@gmail.com To: ccie_voice@onlinestudylist.commailto:ccie_voice@onlinestudylist.com Subject: [OSL | CCIE_Voice] Mobile Voice Access not working since many days!! Message-ID: cag4zmyxmd5xj67pwv+_gpabedjoydyg+zbnmugtsfuj3nsx...@mail.gmail.commailto:cag4zmyxmd5xj67pwv+_gpabedjoydyg+zbnmugtsfuj3nsx...@mail.gmail.com Content-Type: text/plain; charset=iso-8859-1 Hello All, I have been trying this config for MVA for close to 2 weeks now and it does
Re: [OSL | CCIE_Voice] MVA partial match issue
Actually, one point of clarification here. The service parameter Sergey is referring to ( Inbound Calling Search Space for Remote Destination) does not play a role in digit analysis for MVA calls. That service parameter is a little misleading and confusing. There are two call flows you have to keep in mind when dealing with ingress calls from Remote Destinations. 1. Direct inward dial from the RD to your internal dial plan (e.g. directory numbers, MML, hunt pilots, etc.) Basically, anything that is not the MVA steering digit pattern. The service parameter Sergey mentioned can affect the digit analysis applied to these calls. 2. Calls handed off by the MVA VXML application to CUCM. As Sergey noted, the IOS is terminating the call. Most of the heavy lifting is done at the gateway. The prompts, etc. are all coming by way of VXML but the call is terminated on the gateway. At least up to the point where you choose the option to place a call. At this point in time, the IOS device is going to send the call to the MVA number and the CUCM digit analysis process is going to make a routing decision based on the CSS assigned to the Remote Destination Profile (RDP), regardless of what you have set for that service parameter. So, the service parameter affects ingress calls to DIDs that are not pre-processed by the MVA VXML first. Any call that comes by way of MVA, will use the RDP CSS for digit analysis. You can test this by doing the following. Using the IPExpert topology samples. 1. Create a new partition: block-hqph1_pt 2. Put a translation in this partition 2001/block-hqph1_pt and set that translation to block the number 3. Put this partition in your RDP CSS. Ensure it is at a higher priority partition than the PT that currently holds the 2001 extension programmed on HQ Phone 1. If you use the none partition then it doesn't matter where you add the block PT. 4. Ensure that the service parameter Inbound Calling Search Space for Remote Destination is set to the default value (which is to use the GW CSS). Now, use the PSTN phone line that is associated with your RD and call 2025552001 directly. It should ring (unless you have something else messed up). Using the same PSTN phone line, call into MVA. Log into the service, press 1 to place a call and dial 2001. You should get ANN telling you that the number is unassigned. Another test that may be of interest. 1. Create a new partition: block-hqph1_pt 2. Put a translation in this partition 2001/block-hqph1_pt and set that translation to block the number 3. Put this partition in the CSS you assign to your HQ gateway. Make sure it is sitting at a higher priority than your internal phone PT (if you use one). At this point in time, any calls from the PSTN to 2025552001 will fail. 4. Set the service parameter Inbound Calling Search Space for Remote Destination to use RDP Device/Line CSS 5. Ensure that the RDP CSS does NOT have the block PT 6. Call 2025552001 from the PSTN line associated with your RD. It should work. So, now you can't call 2025552001 from any PSTN line EXCEPT for the line associated with the RD. That would be an interesting IE lab question. -Bill -- William Bell blog: http://ucguerrilla.com twitter: @ucguerrilla On Apr 7, 2013, at 10:59 AM, Sergey Heyphets wrote: Hi Donny, When you dial 4 digit extension from the MVA, the IOS sends call to the MVA number defined under Media Resources, so you must have a dial-peer that matches that number and sends the call to the CUCM. The extension you've dialed is transfered in the Redirected number IE inside the SETUP message sent to the MVA number defined under media resources. Once the call gets to CUCM, it extracts the extension you've dialed from the Redirected Number IE and uses either Gateway CSS or RDP+Line CSS (depending on Service Parameters) to place the call to extension. So, if your call to extension doesn't work, you need to check that you have dial-peer that matches MVA number defined in Media Resources, the Service Params to see which CSS you use for MVA calls and then make sure that whatever CSS you use can reach that extension. I know there are some bugs with partial match in early versions of CUCM 7.X, the workaround is to use complete match. Sergey ___ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com ___ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com
Re: [OSL | CCIE_Voice] MVA partial match issue
Hugo may be right. There is a colleague of mine who has had MVA issues in the past and has had to either restart the service, restart Call Manager service, or reload the VXML service on the router. I don't recall exactly which step fixed the issue. Actually, he may have done all of them. Which, while it resolved the issue, was a bit heavy handed. If you are positive you have everything setup correctly then I would try the following: 1. Reprovision MVA on the IOS application no service MVA http://10.3.120.11:8080/ccmivr/pages/IVRMainpage.vxml service MVA http://10.3.120.11:8080/ccmivr/pages/IVRMainpage.vxml /*you should see the IOS read the VXML if you are on the console and logging to console*/ 2. Restart the MVA service on Pub 3. Restart CallManager service I'd try one at a time and test between. Hugo, out of curiosity, you mentioned service parameters. Were you referring to the parameter Mobile Voice Access Number . This is another parameter that confuses me. I never set it and MVA always works. I am wondering if it is legacy or is used for some other method to access mobility? Maybe part of CUMA? Do you know? -Bill -- William Bell blog: http://ucguerrilla.com twitter: @ucguerrilla On Apr 7, 2013, at 2:40 PM, Barrera, Hugo wrote: It uses the RDP's css while snr uses the re-routing css. Did you also specify the MVA number in the service parameters? A peer had mentioned to me that the service may need to get restarted as well haven't tested it yet though. Regards, Hugo On Apr 6, 2013, at 8:38 PM, donny f f.faraday...@gmail.com wrote: hi Bill and others, I had put the MVA under Media Resources, however when i dial 4 digit ext, it said: the number you dial can't be reached. Questions: - when we use MVA to call 4 digit, are they use IOS dial-peer or RD css to call this 4 digit local ext - my partial match never work , i use 7 digit as match. any idea what missed? tks On Wed, Mar 27, 2013 at 5:46 AM, William Bell b...@ucguerrilla.com wrote: I have ran into a similar problem. In my case I would get a fast busy after entering the extension number followed by #. The issue was I neglected to provision Mobile Voice Access under Media Resources. On Tuesday, March 26, 2013, Barrera, Hugo wrote: Regarding MVA during my first attempt (real lab) I had it working except for when I dialed in and tried to call another 4-digit ext like SAPH1 or SBPH2 any ideas why that didn’t work? Regards, Hugo From: ccie_voice-boun...@onlinestudylist.com [mailto:ccie_voice-boun...@onlinestudylist.com] On Behalf Of Justin Carney Sent: Monday, March 25, 2013 1:51 AM To: donny f Cc: ccie_voice@onlinestudylist.com, (ccie_voice@onlinestudylist.com); michael.se...@compucom.com; networksanitytoinsan...@gmail.com Subject: Re: [OSL | CCIE_Voice] MVA partial match issue You can have the rd with 7 digits only and without the 9 for pstn access - use either application dial rules (match 7 digits, prefix 9) or a translation pattern to modify the rd to match your existing local route pattern. I'm not sure if there's an MVA bug in this version of cucm, but its pretty easy to configure it so that you always have a full match since you will likely have only one rd. This is what I do for the lab. A real world (for nanp) example of MVA partial match would be using e164 address for all rd (+1 npa-nxx-) and set partial match to 10 or 7 depending on whether all sites receive inbound ani as 10d for local calls or if any sites receives only 7d. This would also work for lab, but takes extra steps if you aren't already required to use + dialing For partial match to work, the rd must be longer than the inbound ani (ani 7d and rd +11d). You cannot use partial match with an ani longer than the rd (ani 10d and rd 7d), in this case your options would be to apply inbound transformation on the gateway to make rd ani shorter (ie match the rd) or make your rd longer and manipulate outbound dnis to make it route. On Mar 25, 2013 2:00 AM, donny f f.faraday...@gmail.com wrote: hi, I config the Service parameter for MVA , using partial match 7 digit . However when I dial the RD using 7 digit ,it never works. seem like UCM only take Full match. I heard this is bug, Any suggestion for the work around if still want to use partial match ? d On Sun, Mar 17, 2013 at 9:58 AM, michael.se...@compucom.com wrote: Greetings, I think you are doing everything right just need a few tweaks. Place a call from the PSTN line 2 to 3033300 and do debug isdn q931 on gateway. What digits do you see for the calling number. 7 or 10? If seeing 7 digits inbound change your Remote Destination Number to 525, without the 9. If you are seeing 10 digits inbound the NPA, NXX, TNTN change your remote destination number to XXX525, in other words match
Re: [OSL | CCIE_Voice] MVA partial match issue
yes i had specified it under service param, so far i only restart the MVA service in UCM/. I think this no need RDP css, as i only test MVA. When i press 4 ext , debug voip dialpeer show it hits the MVA number 5999. Here is how I understand , pls correct if this is not right. - when press 1 to call 4 digit, dial-peer voip in IOS router will match 5999 to CallManager VMA 5999 (under Media Resources). - after successfully in UCM MVA, it is up to CallManager VMA process to dial 4 digit (and no need CSS here) Tks d On Sun, Apr 7, 2013 at 12:40 PM, Barrera, Hugo hugo.barr...@nexusis.comwrote: It uses the RDP's css while snr uses the re-routing css. Did you also specify the MVA number in the service parameters? A peer had mentioned to me that the service may need to get restarted as well haven't tested it yet though. Regards, Hugo On Apr 6, 2013, at 8:38 PM, donny f f.faraday...@gmail.com wrote: hi Bill and others, I had put the MVA under Media Resources, however when i dial 4 digit ext, it said: the number you dial can't be reached. Questions: - when we use MVA to call 4 digit, are they use IOS dial-peer or RD css to call this 4 digit local ext - my partial match never work , i use 7 digit as match. any idea what missed? tks On Wed, Mar 27, 2013 at 5:46 AM, William Bell b...@ucguerrilla.com b...@ucguerrilla.com wrote: I have ran into a similar problem. In my case I would get a fast busy after entering the extension number followed by #. The issue was I neglected to provision Mobile Voice Access under Media Resources. On Tuesday, March 26, 2013, Barrera, Hugo wrote: Regarding MVA during my first attempt (real lab) I had it working except for when I dialed in and tried to call another 4-digit ext like SAPH1 or SBPH2 any ideas why that didn’t work? ** ** *Regards,*** *Hugo* ** ** *From:* ccie_voice-boun...@onlinestudylist.com [mailto: ccie_voice-boun...@onlinestudylist.com] *On Behalf Of *Justin Carney *Sent:* Monday, March 25, 2013 1:51 AM *To:* donny f *Cc:* ccie_voice@onlinestudylist.com, (ccie_voice@onlinestudylist.com); michael.se...@compucom.com; networksanitytoinsan...@gmail.com *Subject:* Re: [OSL | CCIE_Voice] MVA partial match issue ** ** You can have the rd with 7 digits only and without the 9 for pstn access - use either application dial rules (match 7 digits, prefix 9) or a translation pattern to modify the rd to match your existing local route pattern. I'm not sure if there's an MVA bug in this version of cucm, but its pretty easy to configure it so that you always have a full match since you will likely have only one rd. This is what I do for the lab. A real world (for nanp) example of MVA partial match would be using e164 address for all rd (+1 npa-nxx-) and set partial match to 10 or 7 depending on whether all sites receive inbound ani as 10d for local calls or if any sites receives only 7d. This would also work for lab, but takes extra steps if you aren't already required to use + dialing For partial match to work, the rd must be longer than the inbound ani (ani 7d and rd +11d). You cannot use partial match with an ani longer than the rd (ani 10d and rd 7d), in this case your options would be to apply inbound transformation on the gateway to make rd ani shorter (ie match the rd) or make your rd longer and manipulate outbound dnis to make it route. On Mar 25, 2013 2:00 AM, donny f f.faraday...@gmail.com wrote: hi, I config the Service parameter for MVA , using partial match 7 digit . However when I dial the RD using 7 digit ,it never works. seem like UCM only take Full match. I heard this is bug, Any suggestion for the work around if still want to use partial match ? d On Sun, Mar 17, 2013 at 9:58 AM, michael.se...@compucom.com wrote: Greetings, I think you are doing everything right just need a few tweaks. Place a call from the PSTN line 2 to 3033300 and do debug isdn q931 on gateway. What digits do you see for the calling number. 7 or 10? If seeing 7 digits inbound change your Remote Destination Number to 525, without the 9. If you are seeing 10 digits inbound the NPA, NXX, TNTN change your remote destination number to XXX525, in other words match what you're seeing in the isdn debug for calling party and make that you're Remote Destination Number. Do NOT require the prefix of 9 on the Remote Destination Number. Also, under Remote Destination Information make sure you are putting a tick in Mobile Phone checkbox and a tick in the Enable Mobile Connect checkbox. Otherwise your configuration looks good. Hope you find this helpful. Michael Sears CCIE 38404 Date: Sun, 17 Mar 2013 18:23:01 +0530 From: sanity insanity networksanitytoinsan...@gmail.com To: ccie_voice@onlinestudylist.com Subject: [OSL | CCIE_Voice] Mobile Voice Access
Re: [OSL | CCIE_Voice] MVA partial match issue
Not quite. The RDP CSS is used by the MVA process in CUCM to make the final call routing decision. -- William Bell blog: http://ucguerrilla.com twitter: @ucguerrilla On Apr 7, 2013, at 3:46 PM, donny f wrote: yes i had specified it under service param, so far i only restart the MVA service in UCM/. I think this no need RDP css, as i only test MVA. When i press 4 ext , debug voip dialpeer show it hits the MVA number 5999. Here is how I understand , pls correct if this is not right. - when press 1 to call 4 digit, dial-peer voip in IOS router will match 5999 to CallManager VMA 5999 (under Media Resources). - after successfully in UCM MVA, it is up to CallManager VMA process to dial 4 digit (and no need CSS here) Tks d On Sun, Apr 7, 2013 at 12:40 PM, Barrera, Hugo hugo.barr...@nexusis.com wrote: It uses the RDP's css while snr uses the re-routing css. Did you also specify the MVA number in the service parameters? A peer had mentioned to me that the service may need to get restarted as well haven't tested it yet though. Regards, Hugo On Apr 6, 2013, at 8:38 PM, donny f f.faraday...@gmail.com wrote: hi Bill and others, I had put the MVA under Media Resources, however when i dial 4 digit ext, it said: the number you dial can't be reached. Questions: - when we use MVA to call 4 digit, are they use IOS dial-peer or RD css to call this 4 digit local ext - my partial match never work , i use 7 digit as match. any idea what missed? tks On Wed, Mar 27, 2013 at 5:46 AM, William Bell b...@ucguerrilla.com wrote: I have ran into a similar problem. In my case I would get a fast busy after entering the extension number followed by #. The issue was I neglected to provision Mobile Voice Access under Media Resources. On Tuesday, March 26, 2013, Barrera, Hugo wrote: Regarding MVA during my first attempt (real lab) I had it working except for when I dialed in and tried to call another 4-digit ext like SAPH1 or SBPH2 any ideas why that didn’t work? Regards, Hugo From: ccie_voice-boun...@onlinestudylist.com [mailto:ccie_voice-boun...@onlinestudylist.com] On Behalf Of Justin Carney Sent: Monday, March 25, 2013 1:51 AM To: donny f Cc: ccie_voice@onlinestudylist.com, (ccie_voice@onlinestudylist.com); michael.se...@compucom.com; networksanitytoinsan...@gmail.com Subject: Re: [OSL | CCIE_Voice] MVA partial match issue You can have the rd with 7 digits only and without the 9 for pstn access - use either application dial rules (match 7 digits, prefix 9) or a translation pattern to modify the rd to match your existing local route pattern. I'm not sure if there's an MVA bug in this version of cucm, but its pretty easy to configure it so that you always have a full match since you will likely have only one rd. This is what I do for the lab. A real world (for nanp) example of MVA partial match would be using e164 address for all rd (+1 npa-nxx-) and set partial match to 10 or 7 depending on whether all sites receive inbound ani as 10d for local calls or if any sites receives only 7d. This would also work for lab, but takes extra steps if you aren't already required to use + dialing For partial match to work, the rd must be longer than the inbound ani (ani 7d and rd +11d). You cannot use partial match with an ani longer than the rd (ani 10d and rd 7d), in this case your options would be to apply inbound transformation on the gateway to make rd ani shorter (ie match the rd) or make your rd longer and manipulate outbound dnis to make it route. On Mar 25, 2013 2:00 AM, donny f f.faraday...@gmail.com wrote: hi, I config the Service parameter for MVA , using partial match 7 digit . However when I dial the RD using 7 digit ,it never works. seem like UCM only take Full match. I heard this is bug, Any suggestion for the work around if still want to use partial match ? d On Sun, Mar 17, 2013 at 9:58 AM, michael.se...@compucom.com wrote: Greetings, I think you are doing everything right just need a few tweaks. Place a call from the PSTN line 2 to 3033300 and do debug isdn q931 on gateway. What digits do you see for the calling number. 7 or 10? If seeing 7 digits inbound change your Remote Destination Number to 525, without the 9. If you are seeing 10 digits inbound the NPA, NXX, TNTN change your remote destination number to XXX525, in other words match what you're seeing in the isdn debug for calling party and make that you're Remote Destination Number. Do NOT require the prefix of 9 on the Remote Destination Number. Also, under Remote Destination Information make sure you are putting a tick in Mobile Phone checkbox and a tick in the Enable Mobile Connect checkbox. Otherwise your configuration looks good. Hope you find this helpful. Michael Sears
Re: [OSL | CCIE_Voice] MVA partial match issue
Yah I was and the callmanager service like you stated. I was under the impression that this service parameter was needed for MVA to completely work, but sounds like it's not from another response. Regards, Hugo From: William Bell [mailto:b...@ucguerrilla.com] Sent: Sunday, April 07, 2013 12:03 PM To: Barrera, Hugo Cc: donny f; Justin Carney; ccie_voice@onlinestudylist.com, (ccie_voice@onlinestudylist.com); michael.se...@compucom.com; networksanitytoinsan...@gmail.com Subject: Re: [OSL | CCIE_Voice] MVA partial match issue Hugo may be right. There is a colleague of mine who has had MVA issues in the past and has had to either restart the service, restart Call Manager service, or reload the VXML service on the router. I don't recall exactly which step fixed the issue. Actually, he may have done all of them. Which, while it resolved the issue, was a bit heavy handed. If you are positive you have everything setup correctly then I would try the following: 1. Reprovision MVA on the IOS application no service MVA http://10.3.120.11:8080/ccmivr/pages/IVRMainpage.vxml service MVA http://10.3.120.11:8080/ccmivr/pages/IVRMainpage.vxml /*you should see the IOS read the VXML if you are on the console and logging to console*/ 2. Restart the MVA service on Pub 3. Restart CallManager service I'd try one at a time and test between. Hugo, out of curiosity, you mentioned service parameters. Were you referring to the parameter Mobile Voice Access Number . This is another parameter that confuses me. I never set it and MVA always works. I am wondering if it is legacy or is used for some other method to access mobility? Maybe part of CUMA? Do you know? -Bill -- William Bell blog: http://ucguerrilla.com twitter: @ucguerrilla On Apr 7, 2013, at 2:40 PM, Barrera, Hugo wrote: It uses the RDP's css while snr uses the re-routing css. Did you also specify the MVA number in the service parameters? A peer had mentioned to me that the service may need to get restarted as well haven't tested it yet though. Regards, Hugo On Apr 6, 2013, at 8:38 PM, donny f f.faraday...@gmail.commailto:f.faraday...@gmail.com wrote: hi Bill and others, I had put the MVA under Media Resources, however when i dial 4 digit ext, it said: the number you dial can't be reached. Questions: - when we use MVA to call 4 digit, are they use IOS dial-peer or RD css to call this 4 digit local ext - my partial match never work , i use 7 digit as match. any idea what missed? tks On Wed, Mar 27, 2013 at 5:46 AM, William Bell b...@ucguerrilla.commailto:b...@ucguerrilla.com wrote: I have ran into a similar problem. In my case I would get a fast busy after entering the extension number followed by #. The issue was I neglected to provision Mobile Voice Access under Media Resources. On Tuesday, March 26, 2013, Barrera, Hugo wrote: Regarding MVA during my first attempt (real lab) I had it working except for when I dialed in and tried to call another 4-digit ext like SAPH1 or SBPH2 any ideas why that didn't work? Regards, Hugo From: ccie_voice-boun...@onlinestudylist.commailto:ccie_voice-boun...@onlinestudylist.com [mailto:ccie_voice-boun...@onlinestudylist.commailto:ccie_voice-boun...@onlinestudylist.com] On Behalf Of Justin Carney Sent: Monday, March 25, 2013 1:51 AM To: donny f Cc: ccie_voice@onlinestudylist.commailto:ccie_voice@onlinestudylist.com, (ccie_voice@onlinestudylist.commailto:ccie_voice@onlinestudylist.com); michael.se...@compucom.commailto:michael.se...@compucom.com; networksanitytoinsan...@gmail.commailto:networksanitytoinsan...@gmail.com Subject: Re: [OSL | CCIE_Voice] MVA partial match issue You can have the rd with 7 digits only and without the 9 for pstn access - use either application dial rules (match 7 digits, prefix 9) or a translation pattern to modify the rd to match your existing local route pattern. I'm not sure if there's an MVA bug in this version of cucm, but its pretty easy to configure it so that you always have a full match since you will likely have only one rd. This is what I do for the lab. A real world (for nanp) example of MVA partial match would be using e164 address for all rd (+1 npa-nxx-) and set partial match to 10 or 7 depending on whether all sites receive inbound ani as 10d for local calls or if any sites receives only 7d. This would also work for lab, but takes extra steps if you aren't already required to use + dialing For partial match to work, the rd must be longer than the inbound ani (ani 7d and rd +11d). You cannot use partial match with an ani longer than the rd (ani 10d and rd 7d), in this case your options would be to apply inbound transformation on the gateway to make rd ani shorter (ie match the rd) or make your rd longer and manipulate outbound dnis to make it route. On Mar 25, 2013 2:00 AM, donny f f.faraday...@gmail.commailto:f.faraday...@gmail.com wrote: hi, I config the Service parameter for MVA , using
Re: [OSL | CCIE_Voice] MVA partial match issue
hi sergey, yes my dial-peer for MVA that match the service parameter is there and it actually trigger it when i press 1 and 4 digit ext. Also CSS for GW and RDP seem include the 4 digit partition. When you said this : -- I know there are some bugs with partial match in early versions of CUCM 7.X, the workaround is to use complete match. Can you explain bit, how this complete/partial match related to failed 4 digit dial ? So far I always think if you can call MVA from PSTN and they prompt to enter PIN, then means partial/complete match is ok here Tks d On Sun, Apr 7, 2013 at 8:59 AM, Sergey Heyphets ser...@heyphets.com wrote: Hi Donny, When you dial 4 digit extension from the MVA, the IOS sends call to the MVA number defined under Media Resources, so you must have a dial-peer that matches that number and sends the call to the CUCM. The extension you've dialed is transfered in the Redirected number IE inside the SETUP message sent to the MVA number defined under media resources. Once the call gets to CUCM, it extracts the extension you've dialed from the Redirected Number IE and uses either Gateway CSS or RDP+Line CSS (depending on Service Parameters) to place the call to extension. So, if your call to extension doesn't work, you need to check that you have dial-peer that matches MVA number defined in Media Resources, the Service Params to see which CSS you use for MVA calls and then make sure that whatever CSS you use can reach that extension. I know there are some bugs with partial match in early versions of CUCM 7.X, the workaround is to use complete match. Sergey ___ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com http://www.platinumplacement.com/ ___ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com
Re: [OSL | CCIE_Voice] MVA partial match issue
hi Bill and others, I had put the MVA under Media Resources, however when i dial 4 digit ext, it said: the number you dial can't be reached. Questions: - when we use MVA to call 4 digit, are they use IOS dial-peer or RD css to call this 4 digit local ext - my partial match never work , i use 7 digit as match. any idea what missed? tks On Wed, Mar 27, 2013 at 5:46 AM, William Bell b...@ucguerrilla.com wrote: I have ran into a similar problem. In my case I would get a fast busy after entering the extension number followed by #. The issue was I neglected to provision Mobile Voice Access under Media Resources. On Tuesday, March 26, 2013, Barrera, Hugo wrote: Regarding MVA during my first attempt (real lab) I had it working except for when I dialed in and tried to call another 4-digit ext like SAPH1 or SBPH2 any ideas why that didn’t work? ** ** *Regards,*** *Hugo* ** ** *From:* ccie_voice-boun...@onlinestudylist.com [mailto: ccie_voice-boun...@onlinestudylist.com] *On Behalf Of *Justin Carney *Sent:* Monday, March 25, 2013 1:51 AM *To:* donny f *Cc:* ccie_voice@onlinestudylist.com, (ccie_voice@onlinestudylist.com); michael.se...@compucom.com; networksanitytoinsan...@gmail.com *Subject:* Re: [OSL | CCIE_Voice] MVA partial match issue ** ** You can have the rd with 7 digits only and without the 9 for pstn access - use either application dial rules (match 7 digits, prefix 9) or a translation pattern to modify the rd to match your existing local route pattern. I'm not sure if there's an MVA bug in this version of cucm, but its pretty easy to configure it so that you always have a full match since you will likely have only one rd. This is what I do for the lab. A real world (for nanp) example of MVA partial match would be using e164 address for all rd (+1 npa-nxx-) and set partial match to 10 or 7 depending on whether all sites receive inbound ani as 10d for local calls or if any sites receives only 7d. This would also work for lab, but takes extra steps if you aren't already required to use + dialing For partial match to work, the rd must be longer than the inbound ani (ani 7d and rd +11d). You cannot use partial match with an ani longer than the rd (ani 10d and rd 7d), in this case your options would be to apply inbound transformation on the gateway to make rd ani shorter (ie match the rd) or make your rd longer and manipulate outbound dnis to make it route. On Mar 25, 2013 2:00 AM, donny f f.faraday...@gmail.com wrote: hi, I config the Service parameter for MVA , using partial match 7 digit . However when I dial the RD using 7 digit ,it never works. seem like UCM only take Full match. I heard this is bug, Any suggestion for the work around if still want to use partial match ? d On Sun, Mar 17, 2013 at 9:58 AM, michael.se...@compucom.com wrote: Greetings, I think you are doing everything right just need a few tweaks. Place a call from the PSTN line 2 to 3033300 and do debug isdn q931 on gateway. What digits do you see for the calling number. 7 or 10? If seeing 7 digits inbound change your Remote Destination Number to 525, without the 9. If you are seeing 10 digits inbound the NPA, NXX, TNTN change your remote destination number to XXX525, in other words match what you're seeing in the isdn debug for calling party and make that you're Remote Destination Number. Do NOT require the prefix of 9 on the Remote Destination Number. Also, under Remote Destination Information make sure you are putting a tick in Mobile Phone checkbox and a tick in the Enable Mobile Connect checkbox. Otherwise your configuration looks good. Hope you find this helpful. Michael Sears CCIE 38404 Date: Sun, 17 Mar 2013 18:23:01 +0530 From: sanity insanity networksanitytoinsan...@gmail.com To: ccie_voice@onlinestudylist.com Subject: [OSL | CCIE_Voice] Mobile Voice Access not working since many days!! Message-ID: cag4zmyxmd5xj67pwv+_gpabedjoydyg+zbnmugtsfuj3nsx...@mail.gmail.com Content-Type: text/plain; charset=iso-8859-1 Hello All, I have been trying this config for MVA for close to 2 weeks now and it does not work . Here are the details The Issue : == I am trying to Intiate a Call from PSTN phone to site B gateway (H323) 3033300 it should ask for authentication once authenticated press 1 to make any 4 digit calls if it is from SB phone 1 . Make sure to display 4 digits number for calling number along with calling name SB Phone 1 they can use local gateway to make the call. Also 2nd line on PSTN phone should be used to dial 3033300 and you will prompted to login. Details: = My config is following 1) The dial-peers are set in the following way dial-peer voice 102 voip preference 2 destination-pattern 3300 session target ipv4:ip
Re: [OSL | CCIE_Voice] MVA partial match issue
hi Sergey, Cab you more specific, where I need to add Media Resources for MVA? example pls d On Wed, Mar 27, 2013 at 12:14 PM, Sergey Heyphets ser...@heyphets.comwrote: The prompts you hear on the when you dial-in are the results of IOS executing the VXML script, which was defined in the application/service definition. When you, however, press 1 to make the call and enter the number, the VXML script instructs the IOS to place the call to the MVA number defined under media resources. So if you don't have the MVA number defined under Media Resources, the initial prompts would work, but placing the call would fail. Sergey On Wed, Mar 27, 2013 at 1:07 PM, Barrera, Hugo hugo.barr...@nexusis.comwrote: But would the MVA number still work on the gateway when you dial in? May it would huh because the MVA AA on the IOS is separate? * * * * *Regards,*** *Hugo * ** ** *From:* William Bell [mailto:b...@ucguerrilla.com] *Sent:* Wednesday, March 27, 2013 4:47 AM *To:* Barrera, Hugo *Cc:* Justin Carney; donny f; ccie_voice@onlinestudylist.com, ( ccie_voice@onlinestudylist.com); michael.se...@compucom.com; networksanitytoinsan...@gmail.com *Subject:* Re: [OSL | CCIE_Voice] MVA partial match issue ** ** I have ran into a similar problem. In my case I would get a fast busy after entering the extension number followed by #. ** ** The issue was I neglected to provision Mobile Voice Access under Media Resources. On Tuesday, March 26, 2013, Barrera, Hugo wrote: Regarding MVA during my first attempt (real lab) I had it working except for when I dialed in and tried to call another 4-digit ext like SAPH1 or SBPH2 any ideas why that didn’t work? *Regards,* *Hugo* *From:* ccie_voice-boun...@onlinestudylist.com [mailto: ccie_voice-boun...@onlinestudylist.com] *On Behalf Of *Justin Carney *Sent:* Monday, March 25, 2013 1:51 AM *To:* donny f *Cc:* ccie_voice@onlinestudylist.com, (ccie_voice@onlinestudylist.com); michael.se...@compucom.com; networksanitytoinsan...@gmail.com *Subject:* Re: [OSL | CCIE_Voice] MVA partial match issue You can have the rd with 7 digits only and without the 9 for pstn access - use either application dial rules (match 7 digits, prefix 9) or a translation pattern to modify the rd to match your existing local route pattern. I'm not sure if there's an MVA bug in this version of cucm, but its pretty easy to configure it so that you always have a full match since you will likely have only one rd. This is what I do for the lab. A real world (for nanp) example of MVA partial match would be using e164 address for all rd (+1 npa-nxx-) and set partial match to 10 or 7 depending on whether all sites receive inbound ani as 10d for local calls or if any sites receives only 7d. This would also work for lab, but takes extra steps if you aren't already required to use + dialing For partial match to work, the rd must be longer than the inbound ani (ani 7d and rd +11d). You cannot use partial match with an ani longer than the rd (ani 10d and rd 7d), in this case your options would be to apply inbound transformation on the gateway to make rd ani shorter (ie match the rd) or make your rd longer and manipulate outbound dnis to make it route. On Mar 25, 2013 2:00 AM, donny f f.faraday...@gmail.com wrote: hi, I config the Service parameter for MVA , using partial match 7 digit . However when I dial the RD using 7 digit ,it never works. seem like UCM only take Full match. I heard this is bug, Any suggestion for the work around if still want to use partial match ? d On Sun, Mar 17, 2013 at 9:58 AM, michael.se...@compucom.com wrote: Greetings, I think you are doing everything right just need a few tweaks. Place a call from the PSTN line 2 to 3033300 and do debug isdn q931 on gateway. What digits do you see for the calling number. 7 or 10? If seeing 7 digits inbound change your Remote Destination Number to 525, without the 9. If you are seeing 10 digits inbound the NPA, NXX, TNTN change your remote destination number to XXX525, in other words match what you're seeing in the isdn debug for calling party and make that you're Remote Destination Number. Do NOT require the prefix of 9 on the Remote Destination Number. Also, under Remote Destination Information make sure you are putting a tick in Mobile Phone checkbox and a tick in the Enable Mobile Connect checkbox. Otherwise your configuration looks good. Hope you find this helpful. Michael Sears CCIE 38404 Date: Sun, 17 Mar 2013 18:23:01 +0530 From: sanity insanity networksanitytoinsan...@gmail.com To: ccie_voice@onlinestudylist.com Subject: [OSL | CCIE_Voice] Mobile Voice Access not working since many days!! Message-ID: cag4zmyxmd5xj67pwv+_gpabedjoydyg+zbnmugtsfuj3nsx
Re: [OSL | CCIE_Voice] MVA partial match issue
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/7_0_1/ccmfeat/fsmobmgr.html On Tue, Apr 2, 2013 at 1:41 AM, donny f f.faraday...@gmail.com wrote: hi Sergey, Cab you more specific, where I need to add Media Resources for MVA? example pls d On Wed, Mar 27, 2013 at 12:14 PM, Sergey Heyphets ser...@heyphets.comwrote: The prompts you hear on the when you dial-in are the results of IOS executing the VXML script, which was defined in the application/service definition. When you, however, press 1 to make the call and enter the number, the VXML script instructs the IOS to place the call to the MVA number defined under media resources. So if you don't have the MVA number defined under Media Resources, the initial prompts would work, but placing the call would fail. Sergey On Wed, Mar 27, 2013 at 1:07 PM, Barrera, Hugo hugo.barr...@nexusis.com wrote: But would the MVA number still work on the gateway when you dial in? May it would huh because the MVA AA on the IOS is separate? * * * * *Regards,*** *Hugo * ** ** *From:* William Bell [mailto:b...@ucguerrilla.com] *Sent:* Wednesday, March 27, 2013 4:47 AM *To:* Barrera, Hugo *Cc:* Justin Carney; donny f; ccie_voice@onlinestudylist.com, ( ccie_voice@onlinestudylist.com); michael.se...@compucom.com; networksanitytoinsan...@gmail.com *Subject:* Re: [OSL | CCIE_Voice] MVA partial match issue ** ** I have ran into a similar problem. In my case I would get a fast busy after entering the extension number followed by #. ** ** The issue was I neglected to provision Mobile Voice Access under Media Resources. On Tuesday, March 26, 2013, Barrera, Hugo wrote: Regarding MVA during my first attempt (real lab) I had it working except for when I dialed in and tried to call another 4-digit ext like SAPH1 or SBPH2 any ideas why that didn’t work? *Regards,* *Hugo* *From:* ccie_voice-boun...@onlinestudylist.com [mailto: ccie_voice-boun...@onlinestudylist.com] *On Behalf Of *Justin Carney *Sent:* Monday, March 25, 2013 1:51 AM *To:* donny f *Cc:* ccie_voice@onlinestudylist.com, (ccie_voice@onlinestudylist.com); michael.se...@compucom.com; networksanitytoinsan...@gmail.com *Subject:* Re: [OSL | CCIE_Voice] MVA partial match issue You can have the rd with 7 digits only and without the 9 for pstn access - use either application dial rules (match 7 digits, prefix 9) or a translation pattern to modify the rd to match your existing local route pattern. I'm not sure if there's an MVA bug in this version of cucm, but its pretty easy to configure it so that you always have a full match since you will likely have only one rd. This is what I do for the lab. A real world (for nanp) example of MVA partial match would be using e164 address for all rd (+1 npa-nxx-) and set partial match to 10 or 7 depending on whether all sites receive inbound ani as 10d for local calls or if any sites receives only 7d. This would also work for lab, but takes extra steps if you aren't already required to use + dialing For partial match to work, the rd must be longer than the inbound ani (ani 7d and rd +11d). You cannot use partial match with an ani longer than the rd (ani 10d and rd 7d), in this case your options would be to apply inbound transformation on the gateway to make rd ani shorter (ie match the rd) or make your rd longer and manipulate outbound dnis to make it route. On Mar 25, 2013 2:00 AM, donny f f.faraday...@gmail.com wrote: hi, I config the Service parameter for MVA , using partial match 7 digit . However when I dial the RD using 7 digit ,it never works. seem like UCM only take Full match. I heard this is bug, Any suggestion for the work around if still want to use partial match ? d On Sun, Mar 17, 2013 at 9:58 AM, michael.se...@compucom.com wrote: Greetings, I think you are doing everything right just need a few tweaks. Place a call from the PSTN line 2 to 3033300 and do debug isdn q931 on gateway. What digits do you see for the calling number. 7 or 10? If seeing 7 digits inbound change your Remote Destination Number to 525, without the 9. If you are seeing 10 digits inbound the NPA, NXX, TNTN change your remote destination number to XXX525, in other words match what you're seeing in the isdn debug for calling party and make that you're Remote Destination Number. Do NOT require the prefix of 9 on the Remote Destination Number. Also, under Remote Destination Information make sure you are putting a tick in Mobile Phone checkbox and a tick in the Enable Mobile Connect checkbox. Otherwise your configuration looks good. Hope you find this helpful. Michael Sears CCIE 38404 Date: Sun, 17 Mar 2013 18:23:01 +0530 From: sanity insanity networksanitytoinsan...@gmail.com To: ccie_voice@onlinestudylist.com Subject
Re: [OSL | CCIE_Voice] MVA partial match issue
I have ran into a similar problem. In my case I would get a fast busy after
entering the extension number followed by #.
The issue was I neglected to provision Mobile Voice Access under Media
Resources.
On Tuesday, March 26, 2013, Barrera, Hugo wrote:
Regarding MVA during my first attempt (real lab) I had it working except
for when I dialed in and tried to call another 4-digit ext like SAPH1 or
SBPH2 any ideas why that didn’t work?
** **
*Regards,***
*Hugo*
** **
*From:* ccie_voice-boun...@onlinestudylist.com javascript:_e({}, 'cvml',
'ccie_voice-boun...@onlinestudylist.com'); [mailto:
ccie_voice-boun...@onlinestudylist.com javascript:_e({}, 'cvml',
'ccie_voice-boun...@onlinestudylist.com');] *On Behalf Of *Justin Carney
*Sent:* Monday, March 25, 2013 1:51 AM
*To:* donny f
*Cc:* ccie_voice@onlinestudylist.com javascript:_e({}, 'cvml',
'ccie_voice@onlinestudylist.com');,
(ccie_voice@onlinestudylist.comjavascript:_e({}, 'cvml',
'ccie_voice@onlinestudylist.com'););
michael.se...@compucom.com javascript:_e({}, 'cvml',
'michael.se...@compucom.com');;
networksanitytoinsan...@gmail.comjavascript:_e({}, 'cvml',
'networksanitytoinsan...@gmail.com');
*Subject:* Re: [OSL | CCIE_Voice] MVA partial match issue
** **
You can have the rd with 7 digits only and without the 9 for pstn access -
use either application dial rules (match 7 digits, prefix 9) or a
translation pattern to modify the rd to match your existing local route
pattern.
I'm not sure if there's an MVA bug in this version of cucm, but its pretty
easy to configure it so that you always have a full match since you will
likely have only one rd. This is what I do for the lab.
A real world (for nanp) example of MVA partial match would be using e164
address for all rd (+1 npa-nxx-) and set partial match to 10 or 7
depending on whether all sites receive inbound ani as 10d for local calls
or if any sites receives only 7d. This would also work for lab, but takes
extra steps if you aren't already required to use + dialing
For partial match to work, the rd must be longer than the inbound ani (ani
7d and rd +11d). You cannot use partial match with an ani longer than the
rd (ani 10d and rd 7d), in this case your options would be to apply inbound
transformation on the gateway to make rd ani shorter (ie match the rd) or
make your rd longer and manipulate outbound dnis to make it route.
On Mar 25, 2013 2:00 AM, donny f f.faraday...@gmail.com wrote:
hi,
I config the Service parameter for MVA , using partial match 7 digit .
However when I dial the RD using 7 digit ,it never works.
seem like UCM only take Full match. I heard this is bug,
Any suggestion for the work around if still want to use partial match ?*
***
d
On Sun, Mar 17, 2013 at 9:58 AM, michael.se...@compucom.com wrote:
Greetings,
I think you are doing everything right just need a few tweaks. Place a
call from the PSTN line 2 to 3033300 and do debug isdn q931 on gateway.
What digits do you see for the calling number. 7 or 10? If seeing 7
digits inbound change your Remote Destination Number to 525, without
the 9. If you are seeing 10 digits inbound the NPA, NXX, TNTN change your
remote destination number to XXX525, in other words match what you're
seeing in the isdn debug for calling party and make that you're Remote
Destination Number.
Do NOT require the prefix of 9 on the Remote Destination Number. Also,
under Remote Destination Information make sure you are putting a tick in
Mobile Phone checkbox and a tick in the Enable Mobile Connect checkbox.
Otherwise your configuration looks good. Hope you find this helpful.
Michael Sears
CCIE 38404
Date: Sun, 17 Mar 2013 18:23:01 +0530
From: sanity insanity networksanitytoinsan...@gmail.com
To: ccie_voice@onlinestudylist.com
Subject: [OSL | CCIE_Voice] Mobile Voice Access not working since many
days!!
Message-ID:
cag4zmyxmd5xj67pwv+_gpabedjoydyg+zbnmugtsfuj3nsx...@mail.gmail.com
Content-Type: text/plain; charset=iso-8859-1
Hello All,
I have been trying this config for MVA for close to 2 weeks now and it
does not work . Here are the details
The Issue :
==
I am trying to Intiate a Call from PSTN phone to site B gateway (H323)
3033300 it should ask for
authentication once authenticated press 1 to make any 4 digit calls if it
is from SB phone 1 . Make sure to display 4 digits number for calling
number along with calling name SB Phone 1 they can use local gateway to
make the call.
Also 2nd line on PSTN phone should be used to dial 3033300 and you will
prompted to login.
Details:
=
My config is following
1) The dial-peers are set in the following way
dial-peer voice 102 voip
preference 2
destination-pattern 3300
session target ipv4:ip address
Re: [OSL | CCIE_Voice] MVA partial match issue
But would the MVA number still work on the gateway when you dial in? May it would huh because the MVA AA on the IOS is separate? Regards, Hugo From: William Bell [mailto:b...@ucguerrilla.com] Sent: Wednesday, March 27, 2013 4:47 AM To: Barrera, Hugo Cc: Justin Carney; donny f; ccie_voice@onlinestudylist.com, (ccie_voice@onlinestudylist.com); michael.se...@compucom.com; networksanitytoinsan...@gmail.com Subject: Re: [OSL | CCIE_Voice] MVA partial match issue I have ran into a similar problem. In my case I would get a fast busy after entering the extension number followed by #. The issue was I neglected to provision Mobile Voice Access under Media Resources. On Tuesday, March 26, 2013, Barrera, Hugo wrote: Regarding MVA during my first attempt (real lab) I had it working except for when I dialed in and tried to call another 4-digit ext like SAPH1 or SBPH2 any ideas why that didn't work? Regards, Hugo From: ccie_voice-boun...@onlinestudylist.comjavascript:_e(%7b%7d,%20'cvml',%20'ccie_voice-boun...@onlinestudylist.com'); [mailto:ccie_voice-boun...@onlinestudylist.comjavascript:_e(%7b%7d,%20'cvml',%20'ccie_voice-boun...@onlinestudylist.com');] On Behalf Of Justin Carney Sent: Monday, March 25, 2013 1:51 AM To: donny f Cc: ccie_voice@onlinestudylist.comjavascript:_e(%7b%7d,%20'cvml',%20'ccie_voice@onlinestudylist.com');, (ccie_voice@onlinestudylist.comjavascript:_e(%7b%7d,%20'cvml',%20'ccie_voice@onlinestudylist.com');); michael.se...@compucom.comjavascript:_e(%7b%7d,%20'cvml',%20'michael.se...@compucom.com');; networksanitytoinsan...@gmail.comjavascript:_e(%7b%7d,%20'cvml',%20'networksanitytoinsan...@gmail.com'); Subject: Re: [OSL | CCIE_Voice] MVA partial match issue You can have the rd with 7 digits only and without the 9 for pstn access - use either application dial rules (match 7 digits, prefix 9) or a translation pattern to modify the rd to match your existing local route pattern. I'm not sure if there's an MVA bug in this version of cucm, but its pretty easy to configure it so that you always have a full match since you will likely have only one rd. This is what I do for the lab. A real world (for nanp) example of MVA partial match would be using e164 address for all rd (+1 npa-nxx-) and set partial match to 10 or 7 depending on whether all sites receive inbound ani as 10d for local calls or if any sites receives only 7d. This would also work for lab, but takes extra steps if you aren't already required to use + dialing For partial match to work, the rd must be longer than the inbound ani (ani 7d and rd +11d). You cannot use partial match with an ani longer than the rd (ani 10d and rd 7d), in this case your options would be to apply inbound transformation on the gateway to make rd ani shorter (ie match the rd) or make your rd longer and manipulate outbound dnis to make it route. On Mar 25, 2013 2:00 AM, donny f f.faraday...@gmail.commailto:f.faraday...@gmail.com wrote: hi, I config the Service parameter for MVA , using partial match 7 digit . However when I dial the RD using 7 digit ,it never works. seem like UCM only take Full match. I heard this is bug, Any suggestion for the work around if still want to use partial match ? d On Sun, Mar 17, 2013 at 9:58 AM, michael.se...@compucom.commailto:michael.se...@compucom.com wrote: Greetings, I think you are doing everything right just need a few tweaks. Place a call from the PSTN line 2 to 3033300 and do debug isdn q931 on gateway. What digits do you see for the calling number. 7 or 10? If seeing 7 digits inbound change your Remote Destination Number to 525, without the 9. If you are seeing 10 digits inbound the NPA, NXX, TNTN change your remote destination number to XXX525, in other words match what you're seeing in the isdn debug for calling party and make that you're Remote Destination Number. Do NOT require the prefix of 9 on the Remote Destination Number. Also, under Remote Destination Information make sure you are putting a tick in Mobile Phone checkbox and a tick in the Enable Mobile Connect checkbox. Otherwise your configuration looks good. Hope you find this helpful. Michael Sears CCIE 38404 Date: Sun, 17 Mar 2013 18:23:01 +0530 From: sanity insanity networksanitytoinsan...@gmail.commailto:networksanitytoinsan...@gmail.com To: ccie_voice@onlinestudylist.commailto:ccie_voice@onlinestudylist.com Subject: [OSL | CCIE_Voice] Mobile Voice Access not working since many days!! Message-ID: cag4zmyxmd5xj67pwv+_gpabedjoydyg+zbnmugtsfuj3nsx...@mail.gmail.commailto:cag4zmyxmd5xj67pwv+_gpabedjoydyg+zbnmugtsfuj3nsx...@mail.gmail.com Content-Type: text/plain; charset=iso-8859-1 Hello All, I have been trying this config for MVA for close to 2 weeks now and it does not work . Here are the details The Issue : == I am trying to Intiate a Call from PSTN phone to site B gateway (H323) 3033300 it should ask for authentication once
Re: [OSL | CCIE_Voice] MVA partial match issue
The prompts you hear on the when you dial-in are the results of IOS executing the VXML script, which was defined in the application/service definition. When you, however, press 1 to make the call and enter the number, the VXML script instructs the IOS to place the call to the MVA number defined under media resources. So if you don't have the MVA number defined under Media Resources, the initial prompts would work, but placing the call would fail. Sergey On Wed, Mar 27, 2013 at 1:07 PM, Barrera, Hugo hugo.barr...@nexusis.comwrote: But would the MVA number still work on the gateway when you dial in? May it would huh because the MVA AA on the IOS is separate? * * * * *Regards,*** *Hugo * ** ** *From:* William Bell [mailto:b...@ucguerrilla.com] *Sent:* Wednesday, March 27, 2013 4:47 AM *To:* Barrera, Hugo *Cc:* Justin Carney; donny f; ccie_voice@onlinestudylist.com, ( ccie_voice@onlinestudylist.com); michael.se...@compucom.com; networksanitytoinsan...@gmail.com *Subject:* Re: [OSL | CCIE_Voice] MVA partial match issue ** ** I have ran into a similar problem. In my case I would get a fast busy after entering the extension number followed by #. ** ** The issue was I neglected to provision Mobile Voice Access under Media Resources. On Tuesday, March 26, 2013, Barrera, Hugo wrote: Regarding MVA during my first attempt (real lab) I had it working except for when I dialed in and tried to call another 4-digit ext like SAPH1 or SBPH2 any ideas why that didn’t work? *Regards,* *Hugo* *From:* ccie_voice-boun...@onlinestudylist.com [mailto: ccie_voice-boun...@onlinestudylist.com] *On Behalf Of *Justin Carney *Sent:* Monday, March 25, 2013 1:51 AM *To:* donny f *Cc:* ccie_voice@onlinestudylist.com, (ccie_voice@onlinestudylist.com); michael.se...@compucom.com; networksanitytoinsan...@gmail.com *Subject:* Re: [OSL | CCIE_Voice] MVA partial match issue You can have the rd with 7 digits only and without the 9 for pstn access - use either application dial rules (match 7 digits, prefix 9) or a translation pattern to modify the rd to match your existing local route pattern. I'm not sure if there's an MVA bug in this version of cucm, but its pretty easy to configure it so that you always have a full match since you will likely have only one rd. This is what I do for the lab. A real world (for nanp) example of MVA partial match would be using e164 address for all rd (+1 npa-nxx-) and set partial match to 10 or 7 depending on whether all sites receive inbound ani as 10d for local calls or if any sites receives only 7d. This would also work for lab, but takes extra steps if you aren't already required to use + dialing For partial match to work, the rd must be longer than the inbound ani (ani 7d and rd +11d). You cannot use partial match with an ani longer than the rd (ani 10d and rd 7d), in this case your options would be to apply inbound transformation on the gateway to make rd ani shorter (ie match the rd) or make your rd longer and manipulate outbound dnis to make it route. On Mar 25, 2013 2:00 AM, donny f f.faraday...@gmail.com wrote: hi, I config the Service parameter for MVA , using partial match 7 digit . However when I dial the RD using 7 digit ,it never works. seem like UCM only take Full match. I heard this is bug, Any suggestion for the work around if still want to use partial match ?* *** d On Sun, Mar 17, 2013 at 9:58 AM, michael.se...@compucom.com wrote: Greetings, I think you are doing everything right just need a few tweaks. Place a call from the PSTN line 2 to 3033300 and do debug isdn q931 on gateway. What digits do you see for the calling number. 7 or 10? If seeing 7 digits inbound change your Remote Destination Number to 525, without the 9. If you are seeing 10 digits inbound the NPA, NXX, TNTN change your remote destination number to XXX525, in other words match what you're seeing in the isdn debug for calling party and make that you're Remote Destination Number. Do NOT require the prefix of 9 on the Remote Destination Number. Also, under Remote Destination Information make sure you are putting a tick in Mobile Phone checkbox and a tick in the Enable Mobile Connect checkbox. Otherwise your configuration looks good. Hope you find this helpful. Michael Sears CCIE 38404 Date: Sun, 17 Mar 2013 18:23:01 +0530 From: sanity insanity networksanitytoinsan...@gmail.com To: ccie_voice@onlinestudylist.com Subject: [OSL | CCIE_Voice] Mobile Voice Access not working since many days!! Message-ID: cag4zmyxmd5xj67pwv+_gpabedjoydyg+zbnmugtsfuj3nsx...@mail.gmail.com Content-Type: text/plain; charset=iso-8859-1 Hello All, I have been trying this config for MVA for close to 2 weeks now and it does not work . Here are the details
Re: [OSL | CCIE_Voice] MVA partial match issue
I concur with Sergey. On Mar 27, 2013, at 2:14 PM, Sergey Heyphets wrote: The prompts you hear on the when you dial-in are the results of IOS executing the VXML script, which was defined in the application/service definition. When you, however, press 1 to make the call and enter the number, the VXML script instructs the IOS to place the call to the MVA number defined under media resources. So if you don't have the MVA number defined under Media Resources, the initial prompts would work, but placing the call would fail. Sergey On Wed, Mar 27, 2013 at 1:07 PM, Barrera, Hugo hugo.barr...@nexusis.com wrote: But would the MVA number still work on the gateway when you dial in? May it would huh because the MVA AA on the IOS is separate? Regards, Hugo From: William Bell [mailto:b...@ucguerrilla.com] Sent: Wednesday, March 27, 2013 4:47 AM To: Barrera, Hugo Cc: Justin Carney; donny f; ccie_voice@onlinestudylist.com, (ccie_voice@onlinestudylist.com); michael.se...@compucom.com; networksanitytoinsan...@gmail.com Subject: Re: [OSL | CCIE_Voice] MVA partial match issue I have ran into a similar problem. In my case I would get a fast busy after entering the extension number followed by #. The issue was I neglected to provision Mobile Voice Access under Media Resources. On Tuesday, March 26, 2013, Barrera, Hugo wrote: Regarding MVA during my first attempt (real lab) I had it working except for when I dialed in and tried to call another 4-digit ext like SAPH1 or SBPH2 any ideas why that didn’t work? Regards, Hugo From: ccie_voice-boun...@onlinestudylist.com [mailto:ccie_voice-boun...@onlinestudylist.com] On Behalf Of Justin Carney Sent: Monday, March 25, 2013 1:51 AM To: donny f Cc: ccie_voice@onlinestudylist.com, (ccie_voice@onlinestudylist.com); michael.se...@compucom.com; networksanitytoinsan...@gmail.com Subject: Re: [OSL | CCIE_Voice] MVA partial match issue You can have the rd with 7 digits only and without the 9 for pstn access - use either application dial rules (match 7 digits, prefix 9) or a translation pattern to modify the rd to match your existing local route pattern. I'm not sure if there's an MVA bug in this version of cucm, but its pretty easy to configure it so that you always have a full match since you will likely have only one rd. This is what I do for the lab. A real world (for nanp) example of MVA partial match would be using e164 address for all rd (+1 npa-nxx-) and set partial match to 10 or 7 depending on whether all sites receive inbound ani as 10d for local calls or if any sites receives only 7d. This would also work for lab, but takes extra steps if you aren't already required to use + dialing For partial match to work, the rd must be longer than the inbound ani (ani 7d and rd +11d). You cannot use partial match with an ani longer than the rd (ani 10d and rd 7d), in this case your options would be to apply inbound transformation on the gateway to make rd ani shorter (ie match the rd) or make your rd longer and manipulate outbound dnis to make it route. On Mar 25, 2013 2:00 AM, donny f f.faraday...@gmail.com wrote: hi, I config the Service parameter for MVA , using partial match 7 digit . However when I dial the RD using 7 digit ,it never works. seem like UCM only take Full match. I heard this is bug, Any suggestion for the work around if still want to use partial match ? d On Sun, Mar 17, 2013 at 9:58 AM, michael.se...@compucom.com wrote: Greetings, I think you are doing everything right just need a few tweaks. Place a call from the PSTN line 2 to 3033300 and do debug isdn q931 on gateway. What digits do you see for the calling number. 7 or 10? If seeing 7 digits inbound change your Remote Destination Number to 525, without the 9. If you are seeing 10 digits inbound the NPA, NXX, TNTN change your remote destination number to XXX525, in other words match what you're seeing in the isdn debug for calling party and make that you're Remote Destination Number. Do NOT require the prefix of 9 on the Remote Destination Number. Also, under Remote Destination Information make sure you are putting a tick in Mobile Phone checkbox and a tick in the Enable Mobile Connect checkbox. Otherwise your configuration looks good. Hope you find this helpful. Michael Sears CCIE 38404 Date: Sun, 17 Mar 2013 18:23:01 +0530 From: sanity insanity networksanitytoinsan...@gmail.com To: ccie_voice@onlinestudylist.com Subject: [OSL | CCIE_Voice] Mobile Voice Access not working since many days!! Message-ID: cag4zmyxmd5xj67pwv+_gpabedjoydyg+zbnmugtsfuj3nsx...@mail.gmail.com Content-Type: text/plain; charset=iso-8859-1 Hello All, I have been trying this config for MVA for close to 2 weeks now and it does not work . Here are the details
Re: [OSL | CCIE_Voice] MVA partial match issue
Debug h245 asn1 or debug voip application vxml. If no h245 open logical channel I suspect dial peer. Sent from my Verizon Wireless 4G LTE Smartphone Original message From: William Bell b...@ucguerrilla.com Date: 03/27/2013 6:38 PM (GMT-05:00) To: Sergey Heyphets ser...@heyphets.com Cc: ccie_voice@onlinestudylist.com, (ccie_voice@onlinestudylist.com) ccie_voice@onlinestudylist.com Subject: Re: [OSL | CCIE_Voice] MVA partial match issue I concur with Sergey. On Mar 27, 2013, at 2:14 PM, Sergey Heyphets wrote: The prompts you hear on the when you dial-in are the results of IOS executing the VXML script, which was defined in the application/service definition. When you, however, press 1 to make the call and enter the number, the VXML script instructs the IOS to place the call to the MVA number defined under media resources. So if you don't have the MVA number defined under Media Resources, the initial prompts would work, but placing the call would fail. Sergey On Wed, Mar 27, 2013 at 1:07 PM, Barrera, Hugo hugo.barr...@nexusis.com wrote: But would the MVA number still work on the gateway when you dial in? May it would huh because the MVA AA on the IOS is separate? Regards, Hugo From: William Bell [mailto:b...@ucguerrilla.com] Sent: Wednesday, March 27, 2013 4:47 AM To: Barrera, Hugo Cc: Justin Carney; donny f; ccie_voice@onlinestudylist.com, (ccie_voice@onlinestudylist.com); michael.se...@compucom.com; networksanitytoinsan...@gmail.com Subject: Re: [OSL | CCIE_Voice] MVA partial match issue I have ran into a similar problem. In my case I would get a fast busy after entering the extension number followed by #. The issue was I neglected to provision Mobile Voice Access under Media Resources. On Tuesday, March 26, 2013, Barrera, Hugo wrote: Regarding MVA during my first attempt (real lab) I had it working except for when I dialed in and tried to call another 4-digit ext like SAPH1 or SBPH2 any ideas why that didn’t work? Regards, Hugo From: ccie_voice-boun...@onlinestudylist.com [mailto:ccie_voice-boun...@onlinestudylist.com] On Behalf Of Justin Carney Sent: Monday, March 25, 2013 1:51 AM To: donny f Cc: ccie_voice@onlinestudylist.com, (ccie_voice@onlinestudylist.com); michael.se...@compucom.com; networksanitytoinsan...@gmail.com Subject: Re: [OSL | CCIE_Voice] MVA partial match issue You can have the rd with 7 digits only and without the 9 for pstn access - use either application dial rules (match 7 digits, prefix 9) or a translation pattern to modify the rd to match your existing local route pattern. I'm not sure if there's an MVA bug in this version of cucm, but its pretty easy to configure it so that you always have a full match since you will likely have only one rd. This is what I do for the lab. A real world (for nanp) example of MVA partial match would be using e164 address for all rd (+1 npa-nxx-) and set partial match to 10 or 7 depending on whether all sites receive inbound ani as 10d for local calls or if any sites receives only 7d. This would also work for lab, but takes extra steps if you aren't already required to use + dialing For partial match to work, the rd must be longer than the inbound ani (ani 7d and rd +11d). You cannot use partial match with an ani longer than the rd (ani 10d and rd 7d), in this case your options would be to apply inbound transformation on the gateway to make rd ani shorter (ie match the rd) or make your rd longer and manipulate outbound dnis to make it route. On Mar 25, 2013 2:00 AM, donny f f.faraday...@gmail.com wrote: hi, I config the Service parameter for MVA , using partial match 7 digit . However when I dial the RD using 7 digit ,it never works. seem like UCM only take Full match. I heard this is bug, Any suggestion for the work around if still want to use partial match ? d On Sun, Mar 17, 2013 at 9:58 AM, michael.se...@compucom.com wrote: Greetings, I think you are doing everything right just need a few tweaks. Place a call from the PSTN line 2 to 3033300 and do debug isdn q931 on gateway. What digits do you see for the calling number. 7 or 10? If seeing 7 digits inbound change your Remote Destination Number to 525, without the 9. If you are seeing 10 digits inbound the NPA, NXX, TNTN change your remote destination number to XXX525, in other words match what you're seeing in the isdn debug for calling party and make that you're Remote Destination Number. Do NOT require the prefix of 9 on the Remote Destination Number. Also, under Remote Destination Information make sure you are putting a tick in Mobile Phone checkbox and a tick in the Enable Mobile Connect checkbox. Otherwise your configuration looks good. Hope you find this helpful. Michael Sears CCIE 38404 Date: Sun, 17 Mar 2013 18:23:01 +0530 From: sanity insanity networksanitytoinsan...@gmail.com To: ccie_voice@onlinestudylist.com Subject: [OSL
Re: [OSL | CCIE_Voice] MVA partial match issue
Yah I thought about it as I was writing the original email...makes more sense now, thanks again all who responded! Regards, Hugo From: ccie_voice-boun...@onlinestudylist.com [mailto:ccie_voice-boun...@onlinestudylist.com] On Behalf Of Sergey Heyphets Sent: Wednesday, March 27, 2013 11:14 AM To: ccie_voice@onlinestudylist.com, (ccie_voice@onlinestudylist.com) Subject: Re: [OSL | CCIE_Voice] MVA partial match issue The prompts you hear on the when you dial-in are the results of IOS executing the VXML script, which was defined in the application/service definition. When you, however, press 1 to make the call and enter the number, the VXML script instructs the IOS to place the call to the MVA number defined under media resources. So if you don't have the MVA number defined under Media Resources, the initial prompts would work, but placing the call would fail. Sergey On Wed, Mar 27, 2013 at 1:07 PM, Barrera, Hugo hugo.barr...@nexusis.commailto:hugo.barr...@nexusis.com wrote: But would the MVA number still work on the gateway when you dial in? May it would huh because the MVA AA on the IOS is separate? Regards, Hugo From: William Bell [mailto:b...@ucguerrilla.commailto:b...@ucguerrilla.com] Sent: Wednesday, March 27, 2013 4:47 AM To: Barrera, Hugo Cc: Justin Carney; donny f; ccie_voice@onlinestudylist.commailto:ccie_voice@onlinestudylist.com, (ccie_voice@onlinestudylist.commailto:ccie_voice@onlinestudylist.com); michael.se...@compucom.commailto:michael.se...@compucom.com; networksanitytoinsan...@gmail.commailto:networksanitytoinsan...@gmail.com Subject: Re: [OSL | CCIE_Voice] MVA partial match issue I have ran into a similar problem. In my case I would get a fast busy after entering the extension number followed by #. The issue was I neglected to provision Mobile Voice Access under Media Resources. On Tuesday, March 26, 2013, Barrera, Hugo wrote: Regarding MVA during my first attempt (real lab) I had it working except for when I dialed in and tried to call another 4-digit ext like SAPH1 or SBPH2 any ideas why that didn't work? Regards, Hugo From: ccie_voice-boun...@onlinestudylist.commailto:ccie_voice-boun...@onlinestudylist.com [mailto:ccie_voice-boun...@onlinestudylist.com]mailto:[mailto:ccie_voice-boun...@onlinestudylist.com] On Behalf Of Justin Carney Sent: Monday, March 25, 2013 1:51 AM To: donny f Cc: ccie_voice@onlinestudylist.commailto:ccie_voice@onlinestudylist.com, (ccie_voice@onlinestudylist.commailto:ccie_voice@onlinestudylist.com); michael.se...@compucom.commailto:michael.se...@compucom.com; networksanitytoinsan...@gmail.commailto:networksanitytoinsan...@gmail.com Subject: Re: [OSL | CCIE_Voice] MVA partial match issue You can have the rd with 7 digits only and without the 9 for pstn access - use either application dial rules (match 7 digits, prefix 9) or a translation pattern to modify the rd to match your existing local route pattern. I'm not sure if there's an MVA bug in this version of cucm, but its pretty easy to configure it so that you always have a full match since you will likely have only one rd. This is what I do for the lab. A real world (for nanp) example of MVA partial match would be using e164 address for all rd (+1 npa-nxx-) and set partial match to 10 or 7 depending on whether all sites receive inbound ani as 10d for local calls or if any sites receives only 7d. This would also work for lab, but takes extra steps if you aren't already required to use + dialing For partial match to work, the rd must be longer than the inbound ani (ani 7d and rd +11d). You cannot use partial match with an ani longer than the rd (ani 10d and rd 7d), in this case your options would be to apply inbound transformation on the gateway to make rd ani shorter (ie match the rd) or make your rd longer and manipulate outbound dnis to make it route. On Mar 25, 2013 2:00 AM, donny f f.faraday...@gmail.commailto:f.faraday...@gmail.com wrote: hi, I config the Service parameter for MVA , using partial match 7 digit . However when I dial the RD using 7 digit ,it never works. seem like UCM only take Full match. I heard this is bug, Any suggestion for the work around if still want to use partial match ? d On Sun, Mar 17, 2013 at 9:58 AM, michael.se...@compucom.commailto:michael.se...@compucom.com wrote: Greetings, I think you are doing everything right just need a few tweaks. Place a call from the PSTN line 2 to 3033300 and do debug isdn q931 on gateway. What digits do you see for the calling number. 7 or 10? If seeing 7 digits inbound change your Remote Destination Number to 525, without the 9. If you are seeing 10 digits inbound the NPA, NXX, TNTN change your remote destination number to XXX525, in other words match what you're seeing in the isdn debug for calling party and make that you're Remote Destination Number. Do NOT require the prefix of 9 on the Remote Destination Number. Also, under Remote Destination
Re: [OSL | CCIE_Voice] MVA partial match issue
Regarding MVA during my first attempt (real lab) I had it working except for when I dialed in and tried to call another 4-digit ext like SAPH1 or SBPH2 any ideas why that didn't work? Regards, Hugo From: ccie_voice-boun...@onlinestudylist.com [mailto:ccie_voice-boun...@onlinestudylist.com] On Behalf Of Justin Carney Sent: Monday, March 25, 2013 1:51 AM To: donny f Cc: ccie_voice@onlinestudylist.com, (ccie_voice@onlinestudylist.com); michael.se...@compucom.com; networksanitytoinsan...@gmail.com Subject: Re: [OSL | CCIE_Voice] MVA partial match issue You can have the rd with 7 digits only and without the 9 for pstn access - use either application dial rules (match 7 digits, prefix 9) or a translation pattern to modify the rd to match your existing local route pattern. I'm not sure if there's an MVA bug in this version of cucm, but its pretty easy to configure it so that you always have a full match since you will likely have only one rd. This is what I do for the lab. A real world (for nanp) example of MVA partial match would be using e164 address for all rd (+1 npa-nxx-) and set partial match to 10 or 7 depending on whether all sites receive inbound ani as 10d for local calls or if any sites receives only 7d. This would also work for lab, but takes extra steps if you aren't already required to use + dialing For partial match to work, the rd must be longer than the inbound ani (ani 7d and rd +11d). You cannot use partial match with an ani longer than the rd (ani 10d and rd 7d), in this case your options would be to apply inbound transformation on the gateway to make rd ani shorter (ie match the rd) or make your rd longer and manipulate outbound dnis to make it route. On Mar 25, 2013 2:00 AM, donny f f.faraday...@gmail.commailto:f.faraday...@gmail.com wrote: hi, I config the Service parameter for MVA , using partial match 7 digit . However when I dial the RD using 7 digit ,it never works. seem like UCM only take Full match. I heard this is bug, Any suggestion for the work around if still want to use partial match ? d On Sun, Mar 17, 2013 at 9:58 AM, michael.se...@compucom.commailto:michael.se...@compucom.com wrote: Greetings, I think you are doing everything right just need a few tweaks. Place a call from the PSTN line 2 to 3033300 and do debug isdn q931 on gateway. What digits do you see for the calling number. 7 or 10? If seeing 7 digits inbound change your Remote Destination Number to 525, without the 9. If you are seeing 10 digits inbound the NPA, NXX, TNTN change your remote destination number to XXX525, in other words match what you're seeing in the isdn debug for calling party and make that you're Remote Destination Number. Do NOT require the prefix of 9 on the Remote Destination Number. Also, under Remote Destination Information make sure you are putting a tick in Mobile Phone checkbox and a tick in the Enable Mobile Connect checkbox. Otherwise your configuration looks good. Hope you find this helpful. Michael Sears CCIE 38404 Date: Sun, 17 Mar 2013 18:23:01 +0530 From: sanity insanity networksanitytoinsan...@gmail.commailto:networksanitytoinsan...@gmail.com To: ccie_voice@onlinestudylist.commailto:ccie_voice@onlinestudylist.com Subject: [OSL | CCIE_Voice] Mobile Voice Access not working since many days!! Message-ID: cag4zmyxmd5xj67pwv+_gpabedjoydyg+zbnmugtsfuj3nsx...@mail.gmail.commailto:cag4zmyxmd5xj67pwv%2b_gpabedjoydyg%2bzbnmugtsfuj3nsx...@mail.gmail.com Content-Type: text/plain; charset=iso-8859-1 Hello All, I have been trying this config for MVA for close to 2 weeks now and it does not work . Here are the details The Issue : == I am trying to Intiate a Call from PSTN phone to site B gateway (H323) 3033300 it should ask for authentication once authenticated press 1 to make any 4 digit calls if it is from SB phone 1 . Make sure to display 4 digits number for calling number along with calling name SB Phone 1 they can use local gateway to make the call. Also 2nd line on PSTN phone should be used to dial 3033300 and you will prompted to login. Details: = My config is following 1) The dial-peers are set in the following way dial-peer voice 102 voip preference 2 destination-pattern 3300 session target ipv4:ip address of the CUCM Pub dtmf-relay h245-alphanumeric codec g711ulaw no vad ! dial-peer voice 5 pots service cmm incoming called-number 3300 no digit-strip 2) here is the MVA service url ! application service cmm http://iphttp://%3cip address of the CUCM Pub:8080/ccmivr/pages/IVRMainpage.vxml ! 3) I am stripping 3033300 coming from pstn to last 4 digits using a translation-rule on the voice-port level . That is 3033300 becomes 3300 when it reaches CUCM. 4) On CUCM in the service parameters... Enable Mobile Voice access is set to True Mobile voice access number is 3300 Matching caller id with Remote Destination is Partial Match Number
[OSL | CCIE_Voice] MVA partial match issue
hi, I config the Service parameter for MVA , using partial match 7 digit . However when I dial the RD using 7 digit ,it never works. seem like UCM only take Full match. I heard this is bug, Any suggestion for the work around if still want to use partial match ? d On Sun, Mar 17, 2013 at 9:58 AM, michael.se...@compucom.com wrote: Greetings, I think you are doing everything right just need a few tweaks. Place a call from the PSTN line 2 to 3033300 and do debug isdn q931 on gateway. What digits do you see for the calling number. 7 or 10? If seeing 7 digits inbound change your Remote Destination Number to 525, without the 9. If you are seeing 10 digits inbound the NPA, NXX, TNTN change your remote destination number to XXX525, in other words match what you're seeing in the isdn debug for calling party and make that you're Remote Destination Number. Do NOT require the prefix of 9 on the Remote Destination Number. Also, under Remote Destination Information make sure you are putting a tick in Mobile Phone checkbox and a tick in the Enable Mobile Connect checkbox. Otherwise your configuration looks good. Hope you find this helpful. Michael Sears CCIE 38404 Date: Sun, 17 Mar 2013 18:23:01 +0530 From: sanity insanity networksanitytoinsan...@gmail.com To: ccie_voice@onlinestudylist.com Subject: [OSL | CCIE_Voice] Mobile Voice Access not working since many days!! Message-ID: cag4zmyxmd5xj67pwv+_gpabedjoydyg+zbnmugtsfuj3nsx...@mail.gmail.com Content-Type: text/plain; charset=iso-8859-1 Hello All, I have been trying this config for MVA for close to 2 weeks now and it does not work . Here are the details The Issue : == I am trying to Intiate a Call from PSTN phone to site B gateway (H323) 3033300 it should ask for authentication once authenticated press 1 to make any 4 digit calls if it is from SB phone 1 . Make sure to display 4 digits number for calling number along with calling name SB Phone 1 they can use local gateway to make the call. Also 2nd line on PSTN phone should be used to dial 3033300 and you will prompted to login. Details: = My config is following 1) The dial-peers are set in the following way dial-peer voice 102 voip preference 2 destination-pattern 3300 session target ipv4:ip address of the CUCM Pub dtmf-relay h245-alphanumeric codec g711ulaw no vad ! dial-peer voice 5 pots service cmm incoming called-number 3300 no digit-strip 2) here is the MVA service url ! application service cmm http://ip address of the CUCM Pub:8080/ccmivr/pages/IVRMainpage.vxml ! 3) I am stripping 3033300 coming from pstn to last 4 digits using a translation-rule on the voice-port level . That is 3033300 becomes 3300 when it reaches CUCM. 4) On CUCM in the service parameters... Enable Mobile Voice access is set to True Mobile voice access number is 3300 Matching caller id with Remote Destination is Partial Match Number of digits of Caller ID Partial Match is 7 5) The Mobility softkey has been added for on hold and connected at the softkey template level and applied to the phone ( SB PH1) 6)At the User SB phone 1 I have enabled Enable Mobility and Enable Mobile Voice Access also selected the MAC address of the phone 7) Created a Remote Dest profile and selected user id of sb ph1 and the correct calling search space for the phone 8) Added a Remoted Destination number of 9525 9) Also went to device phone and selected the Owner User ID of SB Ph1 10) Cisco Unified Mobile Voice Access Service is running on both Sub and Pub on CUCM Questions : 1) I now dial from the pstn line 9525 on the pstn phone to 3033300 . The prompt I get asks me for a pin . I enter 1 and the call drops . I Even tried entering 12345 ( which the pin for user SB Phone 1) and still the call drops after the prompt. Anything wrong the above config? Anything missing in the config ? Any suggestions? 2) I am strip the number to last 4 digits ( as in step 3) . Is this correct procedure? 3) There is also no QOS setup in the config for now . Anything related to Bandwidth here? Please help! -MJ ___ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com http://www.platinumplacement.com/ ___ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com
Re: [OSL | CCIE_Voice] MVA partial match issue
You can have the rd with 7 digits only and without the 9 for pstn access - use either application dial rules (match 7 digits, prefix 9) or a translation pattern to modify the rd to match your existing local route pattern. I'm not sure if there's an MVA bug in this version of cucm, but its pretty easy to configure it so that you always have a full match since you will likely have only one rd. This is what I do for the lab. A real world (for nanp) example of MVA partial match would be using e164 address for all rd (+1 npa-nxx-) and set partial match to 10 or 7 depending on whether all sites receive inbound ani as 10d for local calls or if any sites receives only 7d. This would also work for lab, but takes extra steps if you aren't already required to use + dialing For partial match to work, the rd must be longer than the inbound ani (ani 7d and rd +11d). You cannot use partial match with an ani longer than the rd (ani 10d and rd 7d), in this case your options would be to apply inbound transformation on the gateway to make rd ani shorter (ie match the rd) or make your rd longer and manipulate outbound dnis to make it route. On Mar 25, 2013 2:00 AM, donny f f.faraday...@gmail.com wrote: hi, I config the Service parameter for MVA , using partial match 7 digit . However when I dial the RD using 7 digit ,it never works. seem like UCM only take Full match. I heard this is bug, Any suggestion for the work around if still want to use partial match ? d On Sun, Mar 17, 2013 at 9:58 AM, michael.se...@compucom.com wrote: Greetings, I think you are doing everything right just need a few tweaks. Place a call from the PSTN line 2 to 3033300 and do debug isdn q931 on gateway. What digits do you see for the calling number. 7 or 10? If seeing 7 digits inbound change your Remote Destination Number to 525, without the 9. If you are seeing 10 digits inbound the NPA, NXX, TNTN change your remote destination number to XXX525, in other words match what you're seeing in the isdn debug for calling party and make that you're Remote Destination Number. Do NOT require the prefix of 9 on the Remote Destination Number. Also, under Remote Destination Information make sure you are putting a tick in Mobile Phone checkbox and a tick in the Enable Mobile Connect checkbox. Otherwise your configuration looks good. Hope you find this helpful. Michael Sears CCIE 38404 Date: Sun, 17 Mar 2013 18:23:01 +0530 From: sanity insanity networksanitytoinsan...@gmail.com To: ccie_voice@onlinestudylist.com Subject: [OSL | CCIE_Voice] Mobile Voice Access not working since many days!! Message-ID: cag4zmyxmd5xj67pwv+_gpabedjoydyg+zbnmugtsfuj3nsx...@mail.gmail.com Content-Type: text/plain; charset=iso-8859-1 Hello All, I have been trying this config for MVA for close to 2 weeks now and it does not work . Here are the details The Issue : == I am trying to Intiate a Call from PSTN phone to site B gateway (H323) 3033300 it should ask for authentication once authenticated press 1 to make any 4 digit calls if it is from SB phone 1 . Make sure to display 4 digits number for calling number along with calling name SB Phone 1 they can use local gateway to make the call. Also 2nd line on PSTN phone should be used to dial 3033300 and you will prompted to login. Details: = My config is following 1) The dial-peers are set in the following way dial-peer voice 102 voip preference 2 destination-pattern 3300 session target ipv4:ip address of the CUCM Pub dtmf-relay h245-alphanumeric codec g711ulaw no vad ! dial-peer voice 5 pots service cmm incoming called-number 3300 no digit-strip 2) here is the MVA service url ! application service cmm http://ip address of the CUCM Pub:8080/ccmivr/pages/IVRMainpage.vxml ! 3) I am stripping 3033300 coming from pstn to last 4 digits using a translation-rule on the voice-port level . That is 3033300 becomes 3300 when it reaches CUCM. 4) On CUCM in the service parameters... Enable Mobile Voice access is set to True Mobile voice access number is 3300 Matching caller id with Remote Destination is Partial Match Number of digits of Caller ID Partial Match is 7 5) The Mobility softkey has been added for on hold and connected at the softkey template level and applied to the phone ( SB PH1) 6)At the User SB phone 1 I have enabled Enable Mobility and Enable Mobile Voice Access also selected the MAC address of the phone 7) Created a Remote Dest profile and selected user id of sb ph1 and the correct calling search space for the phone 8) Added a Remoted Destination number of 9525 9) Also went to device phone and selected the Owner User ID of SB Ph1 10) Cisco Unified Mobile Voice Access Service is running on both Sub and Pub on CUCM Questions : 1) I now dial from the pstn line 9525 on the pstn phone to
Re: [OSL | CCIE_Voice] MVA partial match issue
hi justin, the full match, always work. Just when we do partial , it never , and always ask for RD number after we dial the MVA. I did exactly you suggest below. - A real world (for nanp) example of MVA partial match would be using e164 address for all rd (+1 npa-nxx-) and set partial match to 10 or 7 depending on whether all sites receive inbound ani as 10d for local calls or if any sites receives only 7d. This would also work for lab, but takes extra steps if you aren't already required to use + dialing is it best practice to always use Full Match, and the we hv to modify using Xfrom on GW and Application Dial Rule/TP to adjust ? tks d On Mon, Mar 25, 2013 at 2:50 AM, Justin Carney justin.s.car...@gmail.comwrote: You can have the rd with 7 digits only and without the 9 for pstn access - use either application dial rules (match 7 digits, prefix 9) or a translation pattern to modify the rd to match your existing local route pattern. I'm not sure if there's an MVA bug in this version of cucm, but its pretty easy to configure it so that you always have a full match since you will likely have only one rd. This is what I do for the lab. A real world (for nanp) example of MVA partial match would be using e164 address for all rd (+1 npa-nxx-) and set partial match to 10 or 7 depending on whether all sites receive inbound ani as 10d for local calls or if any sites receives only 7d. This would also work for lab, but takes extra steps if you aren't already required to use + dialing For partial match to work, the rd must be longer than the inbound ani (ani 7d and rd +11d). You cannot use partial match with an ani longer than the rd (ani 10d and rd 7d), in this case your options would be to apply inbound transformation on the gateway to make rd ani shorter (ie match the rd) or make your rd longer and manipulate outbound dnis to make it route. On Mar 25, 2013 2:00 AM, donny f f.faraday...@gmail.com wrote: hi, I config the Service parameter for MVA , using partial match 7 digit . However when I dial the RD using 7 digit ,it never works. seem like UCM only take Full match. I heard this is bug, Any suggestion for the work around if still want to use partial match ? d On Sun, Mar 17, 2013 at 9:58 AM, michael.se...@compucom.com wrote: Greetings, I think you are doing everything right just need a few tweaks. Place a call from the PSTN line 2 to 3033300 and do debug isdn q931 on gateway. What digits do you see for the calling number. 7 or 10? If seeing 7 digits inbound change your Remote Destination Number to 525, without the 9. If you are seeing 10 digits inbound the NPA, NXX, TNTN change your remote destination number to XXX525, in other words match what you're seeing in the isdn debug for calling party and make that you're Remote Destination Number. Do NOT require the prefix of 9 on the Remote Destination Number. Also, under Remote Destination Information make sure you are putting a tick in Mobile Phone checkbox and a tick in the Enable Mobile Connect checkbox. Otherwise your configuration looks good. Hope you find this helpful. Michael Sears CCIE 38404 Date: Sun, 17 Mar 2013 18:23:01 +0530 From: sanity insanity networksanitytoinsan...@gmail.com To: ccie_voice@onlinestudylist.com Subject: [OSL | CCIE_Voice] Mobile Voice Access not working since many days!! Message-ID: cag4zmyxmd5xj67pwv+_gpabedjoydyg+zbnmugtsfuj3nsx...@mail.gmail.com Content-Type: text/plain; charset=iso-8859-1 Hello All, I have been trying this config for MVA for close to 2 weeks now and it does not work . Here are the details The Issue : == I am trying to Intiate a Call from PSTN phone to site B gateway (H323) 3033300 it should ask for authentication once authenticated press 1 to make any 4 digit calls if it is from SB phone 1 . Make sure to display 4 digits number for calling number along with calling name SB Phone 1 they can use local gateway to make the call. Also 2nd line on PSTN phone should be used to dial 3033300 and you will prompted to login. Details: = My config is following 1) The dial-peers are set in the following way dial-peer voice 102 voip preference 2 destination-pattern 3300 session target ipv4:ip address of the CUCM Pub dtmf-relay h245-alphanumeric codec g711ulaw no vad ! dial-peer voice 5 pots service cmm incoming called-number 3300 no digit-strip 2) here is the MVA service url ! application service cmm http://ip address of the CUCM Pub:8080/ccmivr/pages/IVRMainpage.vxml ! 3) I am stripping 3033300 coming from pstn to last 4 digits using a translation-rule on the voice-port level . That is 3033300 becomes 3300 when it reaches CUCM. 4) On CUCM in the service parameters... Enable Mobile Voice access is set to True Mobile voice
