Yeah what was pointed out earlier there is a UCM Service Parameter under mobility called "Inbound Calling Search Space for Remote Destination" by default it is set to use the gateways incoming calling search space, this can be changed to device+line allowing better control over whom they can call. This is one of those things I tend to change anytime I see MVA to be implemented.
HTH, Chris On Wed, Sep 21, 2011 at 1:53 PM, Geoghegan, Stuart < stuart.geoghe...@ngbailey.co.uk> wrote: > Hi all, > > My CSS for my H323 Gateway could see the MVA partition but i did not have > the internal partiton - doh! > > KP, hopefully that solves your problem too > > Kind Regards > > Stuart > ------------------------------ > *From:* DeShon Crayton [dcrayto...@comcast.net] > *Sent:* Wednesday, September 21, 2011 7:03 PM > *To:* Geoghegan, Stuart; ccie_voice@onlinestudylist.com > *Subject:* RE: [OSL | CCIE_Voice] MVA Hairpinning > > Check the ucm service parameter for mva and see what css is being used > to route calls.. > > > > *From:* ccie_voice-boun...@onlinestudylist.com [mailto: > ccie_voice-boun...@onlinestudylist.com] *On Behalf Of *Geoghegan, Stuart > *Sent:* Wednesday, September 21, 2011 8:39 AM > *To:* ccie_voice@onlinestudylist.com > *Subject:* [OSL | CCIE_Voice] MVA Hairpinning > > > > Hi All, > > > > I have an issue with MVA and hairpinning. > > > > I have followed IPX proctor guide for LAB 6 question 5.3 > > > > I have reached the stage where I can dial in to the MVA access number from > the PSTN line (2123942123 - simulated mobile phone number of HQPH2 – 5002) > and CUCM recognises the associated Remote destination identity of the Remote > destination profile. > > > > So I am happy that initially the vxml script is passing the correct digits > back to CUCM from the H323 GW. > > > > Once I have authenticated with my PIN I press 1 to make a call outbound and > the I receive silence and shortly after the GW disconnects the call. > > > > It’s my understanding that the CSS of the Remote destination profile > dictates the partitions and thus route patterns that can be used for MVA. > > > > This CSS has visibility of the route pattern that I am trying to dial and > as I’m using SLRG I’d expect that that the Route pattern matched points to > SLRG and would use the SLRG assigned to the Device Pool of the Remote > destination Profile. I have also tried this using a specific CSS for the > RDP and specific route pattern pointing to a specific Route List/RG but to > no avail. > > > > I have checked Call Manager traces which reveal the Remote Destination > Information number match and then a H.323 call sent to the HQ Gateway, but > no digits appear for what I have attempted to dial back outbound > > > > Ccapi inout and h225 asn1 traces on the gateway again just reveal the > dialled destination of 5010 which is my MVA access number but then no digits > for my dialled number. > > > > > > I have checked the SRND guide for the call flow ( I have changed the > numbers to match my config) > > > > > > *the Mobile Voice Access user on PSTN phone 408 555-7890 dials the Mobile > Voice Access enterprise DID DN 2123945010 (step 1). * > > ** > > *The call comes into the enterprise PSTN gateway (step 2) * > > ** > > *and is forwarded to Unified CM for call handling (step 3).* > > ** > > * Unified CM next routes the inbound call to the H.323 VoiceXML gateway > (step 4). * > > ** > > *The user is then prompted by IVR to enter their numeric user ID, PIN, and > then a 1 to make a Mobile Voice Access call, followed by the phone number > they wish to reach. Again the user enters 9 1 6745738932 as the number they > wish to reach (followed by the # sign).** **In the meantime, the H.323 > VoiceXML gateway collects and forwards the user input to Unified CM and then > plays the forwarded IVR prompts to the PSTN gateway and the Mobile Voice > Access user. Unified CM in turn receives user input, authenticates the user, > and forwards appropriate IVR prompts to the H.323 VoiceXML gateway based on > user input (step 5). * > > ** > > *After receiving the number to be dialed, Unified CM generates a call > using the user's Remote Destination Profile (step 6). * > > ** > > *The outbound call to 9 1 6745738932 is routed through the PSTN gateway > (step 7). * > > ** > > *Finally, the call rings at the PSTN destination phone with number > 6745738932 (step 8).* > > > > > > So I am failing at step 6, but I believe that my RDP CSS is correct and the > Route pattern I am matching is correct (I have verified this by dialling the > pattern from a device with the same CSS) > > > > I do not see the digits that I am dialing in my traces on CUCM which point > sback to the GW/MVA script, however the IVR prompts are sent initially and > CUCM authenticate using the PIN, so digits are sent back & forth between the > CUCM and H323 GW. > > > > My GW clears down the call, but this must be due to time-out as it reports > normal call clearing > > ** > > *HQ-RTR#* > > *.Sep 21 12:36:25.106: ISDN Se0/1/0:15 Q931: TX -> DISCONNECT pd = 8 > callref = 0x824C * > > * Cause i = 0x8090 - Normal call clearing* > > *.Sep 21 12:36:25.118: ISDN Se0/1/0:15 Q931: RX <- RELEASE pd = 8 callref > = 0x024C* > > *.Sep 21 12:36:25.154: ISDN Se0/1/0:15 Q931: TX -> RELEASE_COMP pd = 8 > callref = 0x824C* > > > > Also to note I am following the same as IPexperts where I am using the same > GW for MGCP and H323. > > > > Any help would be appreciated, thanks, > > > > kind regards > > > > Stuart Geoghegan > > > > The information contained in this e-mail (and attachments) is confidential. > It must not be read, copied, disclosed, printed, forwarded, relied upon or > used by any person other than the intended recipient. Unauthorised use, > disclosure or copying is strictly prohibited. If you have received this > e-mail in error immediately contact the sender and > postmas...@ngbailey.co.uk then permanently delete it and any attachments. > NG Bailey may monitor email where it is considered proportionate to any > perceived risk. This email has been sent on behalf of an NG Bailey company, > if in doubt ask the sender to clarify which company. The NG Bailey > companies include NG Bailey Limited (342778), NG Bailey IT Services Limited > (2338401), NG Bailey Facilities Services Limited (5472032), Kedington > (Northern Ireland) Limited (NI 31145) and NG Bailey Group Limited > (1490238). All of the companies, except Kedington (Northern Ireland) > Limited, are registered in England with registered office at Denton Hall > Ilkley West Yorkshire LS29 0HH. Kedington (Northern Ireland) Limited is > registered in Northern Ireland and its registered office is c/o Carson > McDowell, Murray House, Murray Street, Belfast, BT1 6DN. > > _______________________________________________ > 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
