If I see this right you are trying to call 5621891 which is the Iceland local number at BR2 right?
So you are doing a TEHO from US to the Iceland Gateway Not sure but has the Iceland Breakout not the requirement to send this with called party type subscriber? And calling party type international? Hth, Bernhard Von: Graham Hopkins [mailto:ghopk...@wolf-rock.co.uk] Gesendet: Freitag, 8. Oktober 2010 10:47 An: amr thabt Cc: Stutz, Bernhard; ccie_voice@onlinestudylist.com; Pithog Oil Betreff: Re: [OSL | CCIE_Voice] MVA Troubleshooting lab 6 question 5.3 Currently have a similar issue with the same lab - symptoms are: MVA call connects OK and calls placed to internal numbers are fine ( except 5002 but that is the number that the mobile is linked to so may be normal - why would you call yourself) Calls placed to local/ld numbers never reach the HQ MGCP gateway Calls placed to international numbers at BR2 reach the BR2 UCME and then hang up after one ring - Cause i = 0x80AF - Resource unavailable, unspecified Time for some CUCM debugs - any other ideas ? Bits from config and debug HQ RTR voice translation-rule 100 rule 1 /^5002$/ /2123942123/ ! voice translation-profile MVA translate calling 100 application service MVA http://10.10.210.10:8080/ccmivr/pages/IVRMainpage.vxml dial-peer voice 5010 voip translation-profile incoming MVA service mva destination-pattern 5010 session target ipv4:10.10.210.10 incoming called-number 5010 dtmf-relay h245-alphanumeric codec g711ulaw no vad CUCM 5010 in pt-internal is matched by the MGCP gateway and points to to H.323 Gateway which points to 5010 in pt-mva which is the MVA access number FROM Br2 RTR Oct 8 08:39:17.932: ISDN Se0/0/0:15 Q931: Applying typeplan for sw-type 0x12 is 0x0 0x1, Calling num 12123945002 Oct 8 08:39:17.932: ISDN Se0/0/0:15 Q931: Sending SETUP callref = 0x0082 callID = 0x8003 switch = primary-net5 interface = User Oct 8 08:39:17.936: ISDN Se0/0/0:15 Q931: TX -> SETUP pd = 8 callref = 0x0082 Bearer Capability i = 0x8090A3 Standard = CCITT Transfer Capability = Speech Transfer Mode = Circuit Transfer Rate = 64 kbit/s Channel ID i = 0xA98383 Exclusive, Channel 3 Calling Party Number i = 0x0181, '12123945002' Plan:ISDN, Type:Unknown Called Party Number i = 0x80, '5621891' Plan:Unknown, Type:Unknown BR2-RTR# Oct 8 08:39:17.972: ISDN Se0/0/0:15 Q931: RX <- CALL_PROC pd = 8 callref = 0x8082 Channel ID i = 0xA98383 Exclusive, Channel 3 Oct 8 08:39:17.992: ISDN Se0/0/0:15 Q931: RX <- ALERTING pd = 8 callref = 0x8082 Progress Ind i = 0x8188 - In-band info or appropriate now available Oct 8 08:39:18.084: ISDN Se0/0/0:15 Q931: TX -> DISCONNECT pd = 8 callref = 0x0082 Cause i = 0x80AF - Resource unavailable, unspecified Oct 8 08:39:18.096: ISDN Se0/0/0:15 Q931: RX <- RELEASE pd = 8 callref = 0x8082 Oct 8 08:39:18.100: ISDN Se0/0/0:15 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x0082 BR2-RTR# Regards Graham On 7 Oct 2010, at 20:00, amr thabt wrote: Hi Stutz, 1- add translation rule& profile to dial-p 1997 to change the calling number to be '8884343' . 2- if still have a problem , check css of RDP and may restart Mobile Voice Service I hpoe this may help HTH AMR On Thu, Oct 7, 2010 at 9:26 PM, Stutz, Bernhard <st...@pandacom.de> wrote: Hi, I run into the same issue. furthermore i have to hairpin the call through a h323 gateway as all incoming calls come per mgcp to the callmanager. You have then to add a H.323 gateway to the same mgcp gateway which is possible. I got following dial--peers configured: dial-peer voice 1999 voip service cmm incoming called-number 1999 dtmf-relay h245-alphanumeric codec g711ulaw ! dial-peer voice 101 voip preference 1 destination-pattern 1997 voice-class h323 1 session target ipv4:10.10.210.10 dtmf-relay h245-alphanumeric codec g711ulaw no vad Under callmanager i have 1997 as MVA Number defined at Media Ressources->Mobile Voice Access and also at service parameter When i call the mva the call comes in via mgcp, on ccm i have a route pattern that sends 1999 back to the h.323 configured gateway, then the service gets invoked. so far so good. I have remote destination configured with 8884343 and the call comes in as following: Oct 7 21:41:58.277: ISDN Se0/0/0:23 Q931: RX <- SETUP pd = 8 callref = 0x00B4 Bearer Capability i = 0x8090A2 Standard = CCITT Transfer Capability = Speech Transfer Mode = Circuit Transfer Rate = 64 kbit/s Channel ID i = 0xA98381 Exclusive, Channel 1 Progress Ind i = 0x8583 - Origination address is non-ISDN Calling Party Number i = 0x4180, Plan:ISDN, Type:Subscriber(local) Called Party Number i = 0xA1, '4158881999' Plan:ISDN, Type:National Oct 7 21:41:58.317: //-1/80DCADB41800/DPM/dpAssociateIncomingPeerCore: Calling Number=8884343, 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 Oct 7 21:41:58.317: //-1/80DCADB41800/DPM/dpAssociateIncomingPeerCore: Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming Dial-peer=1999 Oct 7 21:41:58.317: //-1/80DCADB41800/DPM/dpAssociateIncomingPeerCore: Calling Number=8884343, 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 Oct 7 21:41:58.317: //-1/80DCADB41800/DPM/dpAssociateIncomingPeerCore: BR1-RTR#Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming Dial-peer=1999 Oct 7 21:41:58.385: ISDN Se0/0/0:23 Q931: TX -> CALL_PROC pd = 8 callref = 0x80B4 Channel ID i = 0xA98381 Exclusive, Channel 1 Oct 7 21:41:58.393: ISDN Se0/0/0:23 Q931: TX -> CONNECT pd = 8 callref = 0x80B4 Oct 7 21:41:58.401: ISDN Se0/0/0:23 Q931: RX <- CONNECT_ACK pd = 8 callref = 0x00B4 Then i am getting asked for the pin which is been accepted. after that i choose option 1 and push 5002# Then the call gets disconnected: Oct 7 21:42:21.297: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore: Calling Number=, Called Number=1997, Peer Info Type=DIALPEER_INFO_SPEECH Oct 7 21:42:21.301: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore: Match Rule=DP_MATCH_DEST; Called Number=1997 Oct 7 21:42:21.301: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore: Result=Success(0) after DP_MATCH_DEST Oct 7 21:42:21.301: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersMoreArg: Result=SUCCESS(0) List of Matched Outgoing Dial-peer(s): 1: Dial-peer Tag=101 Oct 7 21:42:21.301: //-1/80DCADB41800/DPM/dpMatchPeersCore: Calling Number=, Called Number=1997, Peer Info Type=DIALPEER_INFO_SPEECH Oct 7 21:42:21.301: //-1/80DCADB41800/DPM/dpMatchPeersCore: Match Rule=DP_MATCH_DEST; Called Number=1997 Oct 7 21:42:21.301: //-1/80DCADB41800/DPM/dpMatchPeersCore: Result=Success(0) after DP_MATCH_DEST Oct 7 21:42:21.301: //-1/80DCADB41800/DPM/dpMatchPeersMoreArg: Result=SUCCESS(0) List of Matched Outgoing Dial-peer(s): 1: Dial-peer Tag=101 Oct 7 21:42:21.345: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore: Calling Number=, Called Number=8884343, Peer Info Type=DIALPEER_INFO_SPEECH Oct 7 21:42:21.345: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore: Match Rule=DP_MATCH_DEST; Called Number=8884343 Oct 7 21:42:21.345: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore: No Outgoing Dial-peer Is Matched; Result=NO_MATCH(-1) Oct 7 21:42:21.345: //-1/xxxxxxxxxxxx/DPM/dpMatchPeers: Result=NO_MATCH(-1) Oct 7 21:42:21.345: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore: Calling Number=, Called Number=1997, Peer Info Type=DIALPEER_INFO_SPEECH Oct 7 21:42:21.345: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore: Match Rule=DP_MATCH_DEST; Called Number=1997 Oct 7 21:42:21.345: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore: Result=Success(0) after DP_MATCH_DEST Oct 7 21:42:21.345: //-1/xxxxxxxxxxxx/DPM/dpMatchPeers: Result=SUCCESS(0) List of Matched Outgoing Dial-peer(s): 1: Dial-peer Tag=101 You see there he is trying to call 1997 which matches dial-peer 101 and sends him to the callmanager. this is expected behaviour as 1997 is the MVA number. But he is also trying to make a call again to Oct 7 21:42:21.345: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore: Calling Number=, Called Number=8884343, Peer Info Type=DIALPEER_INFO_SPEECH Oct 7 21:42:21.345: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore: Match Rule=DP_MATCH_DEST; Called Number=8884343 Oct 7 21:42:21.345: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore: No Outgoing Dial-peer Is Matched; Result=NO_MATCH(-1) Oct 7 21:42:21.345: //-1/xxxxxxxxxxxx/DPM/dpMatchPeers: Result=NO_MATCH(-1) which results in no match... You can't use a mgcp controlled gateway for outgoing calls via h.323 so you have to send it back to ccm which sends the call via mgcp out: dial-peer voice 888 voip destination-pattern 8884343 session target ipv4:10.10.210.10 dtmf-relay h245-signal h245-alphanumeric no vad but this doesn't help either. It looks buggy to me as the calling number is always empty and this can't work because the caller 8884343 has already a call to 1999 and then gets a call back again? if the caller has a busy trigger 1 then this second call will get an busy. I tried to do some various digit manipulation but this doesn't help. cheers, Bernhard ________________________________ Von: ccie_voice-boun...@onlinestudylist.com im Auftrag von amr thabt Gesendet: Do 07.10.2010 14:04 An: Pithog Oil Cc: ccie_voice@onlinestudylist.com Betreff: Re: [OSL | CCIE_Voice] MVA Troubleshooting lab 6 question 5.3 Hi , can you post your dialpeer configuration hth amr On Thu, Oct 7, 2010 at 12:24 AM, Pithog Oil <pithog...@yahoo.com> wrote: I spent some time trying to figure out a fix but, i have not gotten the solution yet, whenever i call "2123945010" in an attemp to invoke my MVA application, it rings quite fine and prompts me for my remote destination, ID and when i press 1 to call an extension, i try to place a call but the call gets dropped. I have my MVA number specified on UCM to be 5010, i will appreciate assistance on how to fix thas issue, i think a translation profile was used in the solutions to translate /5002/ /2123942123/ but its not clear how the translation pattern was invoked. Thanks in Anticipation. _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com <http://www.ipexpert.com/> _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
