It could exist, what happened is it wouldn't try "Voice-mail" param anymore
Jeremy 2009/5/19 <[email protected]> > gdm cant co-exist with final destination. remove the final destination in > hunt list config > > *Sandy Lee <[email protected]>* wrote: > > Hi, > > I configured a GDM(3333) in CUE and it works fine when I call it directly > when I put in a final destination in the ephone-hunt. MWI envelopes are > flashing and my users can access the message and turn off mwi. But when I > try via the BACD (I took off the final destination in ephone-hunt), it > doesn’t go to voicemail. Here’s my config and my debug: > > ! > application > service queue flash:app-b-acd-2.1.0.0.tcl > param aa-hunt3 3333 > param queue-len 15 > param number-of-hunt-grps 2 > param aa-hunt2 3210 > param queue-manager-debugs 1 > ! > service aa flash:app-b-acd-aa-2.1.0.0.tcl > paramspace english index 1 > param number-of-hunt-grps 2 > param handoff-string aa > param dial-by-extension-option 1 > paramspace english language en > param max-time-vm-retry 2 > param aa-pilot 3500 > paramspace english location flash: > param second-greeting-time 60 > param welcome-prompt _bacd_welcome.au > param call-retry-timer 5 > param max-time-call-retry 90 > param voice-mail 3333 > param service-name queue > ! > ! > dial-peer voice 3600 voip > translation-profile outgoing VM > destination-pattern 3[126]00 > session protocol sipv2 > session target ipv4:10.4.202.2 > incoming called-number 399[89].... > dtmf-relay sip-notify > codec g711ulaw > no vad > ! > dial-peer voice 3500 voip > service aa > destination-pattern 3500 > session target ipv4:172.4.102.1 > incoming called-number 3500 > dtmf-relay h245-alphanumeric > codec g711ulaw > no vad > ! > dial-peer voice 3501 pots > service aa > incoming called-number 3500 > ! > ephone-hunt 1 sequential > pilot 3210 > list 3001, 3003 > timeout 12 > no-reg both > ! > ephone-dn 6 > number 3333 no-reg primary > call-forward all 3600 > ! > > **** From debug voip dial-peer **** > > Pod14-BR2-RTR# 1: Dial-peer Tag=20001 > May 18 16:49:36.183: //-1/B45007EF80EA/DPM/dpMatchPeersCore: > Calling Number=, Called Number=3600, Peer Info Type=DIALPEER_INFO_SPEECH > May 18 16:49:36.183: //-1/B45007EF80EA/DPM/dpMatchPeersCore: > Match Rule=DP_MATCH_DEST; Called Number=3600 > May 18 16:49:36.183: //-1/B45007EF80EA/DPM/dpMatchPeersCore: > Result=Success(0) after DP_MATCH_DEST > May 18 16:49:36.183: //-1/B45007EF80EA/DPM/dpMatchPeersMoreArg: > Result=SUCCESS(0) > List of Matched Outgoing Dial-peer(s): > 1: Dial-peer Tag=3600 > Pod14-BR2-RTR# > May 18 16:49:41.195: //-1/B74CC78A80EC/DPM/dpMatchPeersCore: > Calling Number=, Called Number=3333, Peer Info Type=DIALPEER_INFO_SPEECH > May 18 16:49:41.199: //-1/B74CC78A80EC/DPM/dpMatchPeersCore: > Match Rule=DP_MATCH_DEST; Called Number=3333 > May 18 16:49:41.199: //-1/B74CC78A80EC/DPM/dpMatchPeersCore: > Result=Success(0) after DP_MATCH_DEST > May 18 16:49:41.199: //-1/B74CC78A80EC/DPM/dpMatchPeersMoreArg: > Result=SUCCESS(0) > List of Matched Outgoing Dial-peer(s): > 1: Dial-peer Tag=20005 > May 18 16:49:41.199: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore: > Calling Number=, Called Number=3001, Peer Info Type=DIALPEER_INFO_SPEECH > May 18 16:49:41.199: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore: > Match Rule=DP_MATCH_DEST; Called Number=3001 > May 18 16:49:41.199: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore: > Result=Success(0) after DP_MATCH_DEST > May 18 16:49:41.199: //-1/xxxxxxxxxxxx/DPM/dpMatchPeers: > Result=SUCCESS(0) > List of Matched Outgoing Dial-peer(s): > > It’s like the called-number turns out to be the calling number. Can someone > help me figure this out ? > > Thanks, > Sandy. > > > ------------------------------ > Power up the Internet with Yahoo! > Toolbar.<http://pr.mail.yahoo.co.jp/toolbar/> >
