hi all,

thanks for your suggestion. i will try your suggestions when i do next lab
and will get back to you guys.

thanks
-adil


On Thu, Jun 16, 2011 at 4:29 AM, Sam Park <upperlevelpark...@gmail.com>wrote:

> George;
> No disagreement here.
> I will definitely try it.
>
> Regards;
> Sam
>
>
> On Wed, Jun 15, 2011 at 1:45 PM, George Goglidze <gogli...@gmail.com>wrote:
>
>> Hi Sam,
>>
>> I do agree both will work, there's no reason why one would work and not
>> the other.
>> But in my opinion having two different numbers, makes the task easier, as
>> you don't have to worry about Partitions and Calling Search Spaces as you
>> would with only one number, as MVA Number and RP with the same number can't
>> be on the same Partition.
>>
>> Just try it next time, believe me works very well,
>>
>> And another thing, I don't really see difference between "best practice"
>> and "known good". This should be sinonims, as normally SRND "Best Practice"
>> is the one that you would want to configure.  Especially in CCIE Lab.
>> Now it's different in Production network, where every customer's
>> particular network, and sircumstances can dictate if you should go for "Best
>> Practice" or just "Known Good - this has worked in my previous customer"
>> solution.
>>
>> Regards,
>>
>>
>>
>> On Wed, Jun 15, 2011 at 5:45 PM, Sam Park <upperlevelpark...@gmail.com>wrote:
>>
>>> George;
>>>
>>> Thanks for post.  I've actually not read the SRND on MVA (haven't got to
>>> it yet)
>>>
>>> I think you are talking about SRND "best practice" not a "known good".
>>> I've been practicing IPX method for the Lab.  Same number in and out and
>>> back in, works everytime.  Sure, it's not "best practice" but if someone is
>>> familiar with IPX material, it is a "known good".  and anyway, I recommended
>>> that for his testing - not final config.
>>>
>>> Cheers
>>>
>>> Sam.
>>>
>>>
>>>
>>> On Wed, Jun 15, 2011 at 10:41 AM, George Goglidze <gogli...@gmail.com>wrote:
>>>
>>>> Hi Sam,
>>>>
>>>> The "known good" config is what Cisco suggests in their SRND, and they
>>>> suggest to have two different numbers:
>>>> Here's a snippet from SRND:
>>>>
>>>> *Note *When deploying Mobile Voice Access in hairpinning mode, Cisco
>>>> recommends configuring the Mobile Voice Access DID at the PSTN gateway and
>>>> the Mobile Voice Access Directory Number within Cisco Unified CM (under
>>>> *Media Resources* > *Mobile Voice Access*) as different numbers. A
>>>> translation pattern within Unified CM can then be used to translate the
>>>> called number of the Mobile Voice Access DID to the configured Mobile Voice
>>>> Access directory number. Because the Mobile Voice Access directory number
>>>> configured within Unified CM is visible to the administrator only,
>>>> translation between the DID and directory number will be invisible to the
>>>> end user and there will be no change in end-user dialing behavior. This is
>>>> recommended in order to prevent mobility call routing issues in
>>>> multi-cluster environments. This recommendation does not apply to Mobile
>>>> Voice Access in non-hairpinning mode.
>>>>
>>>>
>>>>
>>>> On Wed, Jun 15, 2011 at 3:02 PM, Sam Park 
>>>> <upperlevelpark...@gmail.com>wrote:
>>>>
>>>>> Adil;
>>>>>
>>>>> For testing, create a G711-region only device pool and put your H323 gw
>>>>> in that DP.  So all devices even PSTN should be able to make the call.
>>>>> If not than, there might be some other config error.
>>>>> Start from there to see where it's failing.  I got through testing
>>>>> yesterday but reset my rack.
>>>>>
>>>>> As suggested earlier make sure you don't user voice class codec in your
>>>>> Dialpeer.
>>>>>
>>>>> Also, your config is interesting, have to try it next time.
>>>>> But since a "known good" config (in this forum for Lab takers) is to
>>>>> make the Route Parttern number the same as the MVA number, you could try
>>>>> that, again just to see that it all works, and there isn't some other 
>>>>> issue.
>>>>>
>>>>> Sam.
>>>>>
>>>>>
>>>>> On Wed, Jun 15, 2011 at 9:02 AM, Adil Shaikh <adil.sha...@gmail.com>wrote:
>>>>>
>>>>>> Hi SinGei,
>>>>>>
>>>>>> I do not have translation pattern in CM. You call flow is aboslutely
>>>>>> correct. Just for clarity. I am adding few things in your call flow as
>>>>>> below:
>>>>>>
>>>>>> PSTN IN [4158881999]--> mgcp gw [4digit]--> route pattern[1999] -->
>>>>>> h323 gw --> match incoming [1999] (service mva configure) dp {here 
>>>>>> service
>>>>>> mva URL  talks to publisher and downloads the MVA number configured in 
>>>>>> CM -
>>>>>> in my case it is 1998}-->match outgoing mva# dp [1998] --> UCM
>>>>>> I hope this clarifies the setup.
>>>>>>
>>>>>> -adil
>>>>>>
>>>>>> On Wed, Jun 15, 2011 at 9:49 PM, ShinGei Yong <shingei.y...@gmail.com
>>>>>> > wrote:
>>>>>>
>>>>>>> hi Adil,
>>>>>>>
>>>>>>> Apologize for the questions, because never try your setup before.
>>>>>>>
>>>>>>> How do you translate the mgcp incoming 1999 to 1998? Do you have any
>>>>>>> translation?
>>>>>>> If not, how are you going to match the DNIS#
>>>>>>>
>>>>>>> My understanding was:
>>>>>>>
>>>>>>> PSTN IN --> mgcp gw --> route pattern --> h323 gw --> match incoming
>>>>>>> mva# (service mva configure) dp-->match outgoing mva# dp --> UCM
>>>>>>>
>>>>>>> TIA
>>>>>>> Shingei
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Jun 15, 2011 at 7:32 PM, Adil Shaikh 
>>>>>>> <adil.sha...@gmail.com>wrote:
>>>>>>>
>>>>>>>> hi ShinGei,
>>>>>>>>
>>>>>>>> The MVA number is 1998.
>>>>>>>> Rather than using same number for the inbound to application service
>>>>>>>> mva and outbound to MVA number, two seperate numbers are used.
>>>>>>>>
>>>>>>>> So, inbound dialpeer to application service mva is 1999 and after
>>>>>>>> hairpinning on Gateway the outbound number is 1998 which is the Mobile 
>>>>>>>> Voice
>>>>>>>> Access number configured on the Call Manager.
>>>>>>>>
>>>>>>>> i hope this clarifies what i am trying to do.
>>>>>>>>
>>>>>>>> thanks
>>>>>>>> -adil
>>>>>>>>
>>>>>>>> On Wed, Jun 15, 2011 at 9:27 PM, ShinGei Yong <
>>>>>>>> shingei.y...@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> May i know where is your outbound dp for mva#1999?
>>>>>>>>> What is the purpose of 1998 ?
>>>>>>>>>
>>>>>>>>> TIA
>>>>>>>>> Shingei
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wed, Jun 15, 2011 at 2:26 PM, Adil Shaikh <
>>>>>>>>> adil.sha...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> Forgot to add that HQ and BR1 phones are sccp.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Wed, Jun 15, 2011 at 4:21 PM, Adil Shaikh <
>>>>>>>>>> adil.sha...@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi all,
>>>>>>>>>>>
>>>>>>>>>>> I have configured MVA hairpin on BR1 router which is an MGCP
>>>>>>>>>>> gateway.
>>>>>>>>>>> If the call is made to MVA route-pattern number [1999] from BR1
>>>>>>>>>>> phone then i hear "Welcome to Cisco Unfiied Communications"
>>>>>>>>>>> If i call to MVA route-pattern number [1999] from HQ phone or
>>>>>>>>>>> PSTN phone then i do not hear "Welcome to Cisco Unfied 
>>>>>>>>>>> Communications".
>>>>>>>>>>> debug shows the correct MVA dial-peer hits on BR1-GW.
>>>>>>>>>>>
>>>>>>>>>>> There is no transcoder configured on HQ or BR1 device pool.  To
>>>>>>>>>>> resolve my issue, if transcoder needs to be configured on HQ or BR1 
>>>>>>>>>>> device
>>>>>>>>>>> pool then i would like to know why.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Here is the configuration:
>>>>>>>>>>> MVA directory number: 1998
>>>>>>>>>>> Route-pattern: 1999 <none> ----> BR1-H323-GW in BR1 device pool
>>>>>>>>>>> BR1-MGCP-GW in BR1 devicepool
>>>>>>>>>>> BR1 and HQ region talks g729
>>>>>>>>>>>
>>>>>>>>>>> Configuration from BR1-RTR:
>>>>>>>>>>>
>>>>>>>>>>> interface Loopback0
>>>>>>>>>>>  ip address 10.10.110.2 255.255.255.255
>>>>>>>>>>>  ip ospf network point-to-point
>>>>>>>>>>>  h323-gateway voip bind srcaddr 10.10.110.2
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> voice service voip
>>>>>>>>>>>  allow-connections h323 to h323
>>>>>>>>>>> !
>>>>>>>>>>> !
>>>>>>>>>>> !
>>>>>>>>>>> voice class codec 1
>>>>>>>>>>>  codec preference 1 g711ulaw bytes 160
>>>>>>>>>>>  codec preference 2 g729r8 bytes 20
>>>>>>>>>>> !
>>>>>>>>>>> !
>>>>>>>>>>> !
>>>>>>>>>>> voice class h323 1
>>>>>>>>>>>  h225 timeout tcp establish 3
>>>>>>>>>>> !
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> voice translation-rule 1002
>>>>>>>>>>>  rule 1 /^1002$/ /4158884343/
>>>>>>>>>>> !
>>>>>>>>>>> !
>>>>>>>>>>> voice translation-profile 1002
>>>>>>>>>>>  translate calling 1002
>>>>>>>>>>> !
>>>>>>>>>>> !
>>>>>>>>>>> !
>>>>>>>>>>> application
>>>>>>>>>>>   service mva
>>>>>>>>>>> http://10.10.210.10:8080/ccmivr/pages/IVRMainpage.vxml
>>>>>>>>>>>   !
>>>>>>>>>>>
>>>>>>>>>>> dial-peer voice 1997 voip
>>>>>>>>>>>  destination-pattern 1998
>>>>>>>>>>>  voice-class codec 1
>>>>>>>>>>>  voice-class h323 1
>>>>>>>>>>>  session target ipv4:10.10.210.11
>>>>>>>>>>>  dtmf-relay h245-alphanumeric
>>>>>>>>>>>  no vad
>>>>>>>>>>> !
>>>>>>>>>>> dial-peer voice 1998 voip
>>>>>>>>>>>  preference 1
>>>>>>>>>>>  destination-pattern 1998
>>>>>>>>>>>  voice-class codec 1
>>>>>>>>>>>  voice-class h323 1
>>>>>>>>>>>  session target ipv4:10.10.210.10
>>>>>>>>>>>  dtmf-relay h245-alphanumeric
>>>>>>>>>>>  no vad
>>>>>>>>>>> !
>>>>>>>>>>> dial-peer voice 1999 voip
>>>>>>>>>>>  translation-profile incoming 1002
>>>>>>>>>>>  service mva
>>>>>>>>>>>  voice-class codec 1
>>>>>>>>>>>  incoming called-number 1999
>>>>>>>>>>>  dtmf-relay h245-alphanumeric
>>>>>>>>>>> !
>>>>>>>>>>> ---------------------
>>>>>>>>>>> output of debug voip dial-p
>>>>>>>>>>>
>>>>>>>>>>> Following output when called 1999 from BR1 extenstion 1002. I
>>>>>>>>>>> hear the MVA message:
>>>>>>>>>>> R1-RTR#
>>>>>>>>>>> *Jun 15 11:23:22.838:
>>>>>>>>>>> //-1/800CEF8C0B00/DPM/dpAssociateIncomingPeerCore:
>>>>>>>>>>>    Calling Number=1002, Called Number=1999, Voice-Interface=0x0,
>>>>>>>>>>>    Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search
>>>>>>>>>>> Type=PEER_TYPE_VOICE,
>>>>>>>>>>>    Peer Info Type=DIALPEER_INFO_SPEECH
>>>>>>>>>>> *Jun 15 11:23:22.838:
>>>>>>>>>>> //-1/800CEF8C0B00/DPM/dpAssociateIncomingPeerCore:
>>>>>>>>>>>    Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming
>>>>>>>>>>> Dial-peer=1999
>>>>>>>>>>> *Jun 15 11:23:22.838:
>>>>>>>>>>> //-1/800CEF8C0B00/DPM/dpAssociateIncomingPeerCore:
>>>>>>>>>>>    Calling Number=1002, Called Number=1999, Voice-Interface=0x0,
>>>>>>>>>>>    Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search
>>>>>>>>>>> Type=PEER_TYPE_VOICE,
>>>>>>>>>>>    Peer Info Type=DIALPEER_INFO_SPEECH
>>>>>>>>>>> BR1-RTR#
>>>>>>>>>>> *Jun 15 11:23:22.838:
>>>>>>>>>>> //-1/800CEF8C0B00/DPM/dpAssociateIncomingPeerCore:
>>>>>>>>>>>    Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming
>>>>>>>>>>> Dial-peer=1999
>>>>>>>>>>> BR1-RTR#
>>>>>>>>>>> BR1-RTR#
>>>>>>>>>>> BR1-RTR#
>>>>>>>>>>> BR1-RTR#
>>>>>>>>>>> BR1-RTR#
>>>>>>>>>>> Following output when called 1999 from HQ extenstion 5002. I do
>>>>>>>>>>> not hear the MVA message:
>>>>>>>>>>> BR1-RTR#
>>>>>>>>>>> BR1-RTR#
>>>>>>>>>>> *Jun 15 11:23:34.346:
>>>>>>>>>>> //-1/801A16940C00/DPM/dpAssociateIncomingPeerCore:
>>>>>>>>>>>    Calling Number=5002, Called Number=1999, Voice-Interface=0x0,
>>>>>>>>>>>    Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search
>>>>>>>>>>> Type=PEER_TYPE_VOICE,
>>>>>>>>>>>    Peer Info Type=DIALPEER_INFO_SPEECH
>>>>>>>>>>> *Jun 15 11:23:34.346:
>>>>>>>>>>> //-1/801A16940C00/DPM/dpAssociateIncomingPeerCore:
>>>>>>>>>>>    Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming
>>>>>>>>>>> Dial-peer=1999
>>>>>>>>>>> *Jun 15 11:23:34.346:
>>>>>>>>>>> //-1/801A16940C00/DPM/dpAssociateIncomingPeerCore:
>>>>>>>>>>>    Calling Number=5002, Called Number=1999, Voice-Interface=0x0,
>>>>>>>>>>>    Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search
>>>>>>>>>>> Type=PEER_TYPE_VOICE,
>>>>>>>>>>>    Peer Info Type=DIALPEER_INFO_SPEECH
>>>>>>>>>>> BR1-RTR#
>>>>>>>>>>> *Jun 15 11:23:34.346:
>>>>>>>>>>> //-1/801A16940C00/DPM/dpAssociateIncomingPeerCore:
>>>>>>>>>>>    Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming
>>>>>>>>>>> Dial-peer=1999
>>>>>>>>>>> BR1-RTR#
>>>>>>>>>>> BR1-RTR#
>>>>>>>>>>> BR1-RTR#
>>>>>>>>>>>
>>>>>>>>>>> Following output when called 4158881999 from PSTN phone
>>>>>>>>>>> 4158884343. I do not hear the MVA message:
>>>>>>>>>>> BR1-RTR#
>>>>>>>>>>> *Jun 15 11:25:44.078:
>>>>>>>>>>> //-1/808792E10D00/DPM/dpAssociateIncomingPeerCore:
>>>>>>>>>>>    Calling Number=1002, Called Number=1999, Voice-Interface=0x0,
>>>>>>>>>>>    Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search
>>>>>>>>>>> Type=PEER_TYPE_VOICE,
>>>>>>>>>>>    Peer Info Type=DIALPEER_INFO_SPEECH
>>>>>>>>>>> *Jun 15 11:25:44.078:
>>>>>>>>>>> //-1/808792E10D00/DPM/dpAssociateIncomingPeerCore:
>>>>>>>>>>>    Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming
>>>>>>>>>>> Dial-peer=1999
>>>>>>>>>>> *Jun 15 11:25:44.078:
>>>>>>>>>>> //-1/808792E10D00/DPM/dpAssociateIncomingPeerCore:
>>>>>>>>>>>    Calling Number=1002, Called Number=1999, Voice-Interface=0x0,
>>>>>>>>>>>    Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search
>>>>>>>>>>> Type=PEER_TYPE_VOICE,
>>>>>>>>>>>    Peer Info Type=DIALPEER_INFO_SPEECH
>>>>>>>>>>> *Jun 15 11:25:44.078:
>>>>>>>>>>> //-1/808792E10D00/DPM/dpAssociateIncomingPeerCore:
>>>>>>>>>>>    Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming
>>>>>>>>>>> Dial-peer=1999
>>>>>>>>>>> BR1-RTR#
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> thanks
>>>>>>>>>>> -adil
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>>   .            . . .
>>>>>>>>>>> _7___|___|_|_|    adil.sha...@gmail.com
>>>>>>>>>>>
>>>>>>>>>>>         . .
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>>   .            . . .
>>>>>>>>>> _7___|___|_|_|    adil.sha...@gmail.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
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>>   .            . . .
>>>>>>>> _7___|___|_|_|    adil.sha...@gmail.com
>>>>>>>>
>>>>>>>>         . .
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>   .            . . .
>>>>>> _7___|___|_|_|    adil.sha...@gmail.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
>>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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
>



-- 
  .            . . .
_7___|___|_|_|    adil.sha...@gmail.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

Reply via email to