07-03-2011 02:55 AM - edited 03-21-2019 04:18 AM
Hello all,
I'm having some serious difficulty getting a divert to a voicemail box working from the auto attendant. I've tried pretty much everything I can think of but always seem to end up with the same result of the call being dropped on trying to divert to the correct voicemail box. The configuration we're trying to setup is an after-hours prompt where the user can "Press One" to leave a message, which immediately diverts to a designated voicemail box.
The VoIP hardware is comprised of:
The three phone models are just for information as ideally the divert wouldn't even go through them in this configuration.
The SPA9000 (192.168.0.5) has the incoming VoIP service on Line 1 and the SPA400 (192.168.0.6) on Line 2. The after-hours prompt uses AA script 2 with Dial Plan 2. Ideally, we want to be in the situation where we can press 1 to divert to a designated mailbox (in this case, 102 on the SPA400) to directly divert the call immediately to the mailbox. Presumably, we could modify this with ease in future, as it seems there's some underlying flaw in the configuration that breaks all diverts to mailboxes from outside numbers (including our initial desired configuration).
I've also taken a look at this document:
https://supportforums.cisco.com/docs/DOC-9872
However, even with this configuration we get the same result (and I don't entirely understand the nature of internap ports nor can I find any documentation on them). Attached is the configuration of the SPA9000 as well as two syslog traces from attempting to dial-in and divert to mailbox. One with the AA Dial Plan 2 diverting direct to vm2102 and the other with the internap port routing. Neither configurations will work correctly.
Please let me know if there's any further information I can provide to be of assistance as unfortunately I've really hit a dead-end with this setup.
07-07-2011 09:52 AM
I looked up some old info on this and below is an example that you can try.
--
Forward calls to the spa400 voicemail from both fxo spa400 calls and sip calls.
Steps
1. Define a hunt group on the 9000
150:cwfd=vm3700100
This registers an extension (huntgroup) 150 and will forward to voice mail box 700100 the 3 states the spa400 is attached to the 3rd line on the spa9000
2. if you want the aa script to transfer to a voicemail box then script target need to look like this:
~~~ target="150@127.0.0.1:5083" ~~~~
3. If you want the aa user to dial an extension or response and get directly to a voicemail box the aa dial plan needs to look list this
|<150:150@127.0.0.1:5083>|
We are using the spa9000 existing sip listener on port 5083 to hairpin turn the calls. The 5083 appears to process the huntgroup, connecting the calls, where the default 6060 port, that is used if you just attempt to use a 150 or vm38700100 target in the aa script and dial plan, does not correctly process the resulting 150@
07-07-2011 02:38 PM
Hi Nseto,
Thanks very much for the help. Unfortunately, I'm still getting the same result! In AA DP2:
(<1:2102@127.0.0.1:5083>)
In Hunt Groups:
2102:cfwd=vm2102
Syslog output from sample call:
<159>AVT Rx Start Tone: 1
192.168.0.5 08/07 07:37:39.300
<159>AVT Rx End Tone
192.168.0.5 08/07 07:37:39.571
<159>[AA]: xfer to target=2102@127.0.0.1:5083
192.168.0.5 08/07 07:37:41.530
<151>CC:BlndXferTgt:2102@127.0.0.1:5083
192.168.0.5 08/07 07:37:41.533
<151>Calling:2102@127.0.0.1:5083
192.168.0.5 08/07 07:37:41.542
<151>[7:0]AAA Rel Call
192.168.0.5 08/07 07:37:41.543
<151>[7:0]AAA:Destory SAA OBJ
192.168.0.5 08/07 07:37:41.545
<134>pri--REFER-->BCC:target=2102@127.0.0.1:5083
192.168.0.5 08/07 07:37:41.547
<134>pri--REFER-->BCC:target=2102@127.0.0.1:5083
192.168.0.5 08/07 07:37:41.548
<151>SESS:?Mtd 4
192.168.0.5 08/07 07:37:41.557
<134>[2]->203.55.229.194:5060(485)
192.168.0.5 08/07 07:37:41.575
<134>[2]->203.55.229.194:5060(485)
192.168.0.5 08/07 07:37:41.576
<134>
192.168.0.5 08/07 07:37:41.577
<134>
192.168.0.5 08/07 07:37:41.578
<134>[2]<<203.55.229.194:5060(382)
192.168.0.5 08/07 07:37:41.614
<134>[2]<<203.55.229.194:5060(382)
192.168.0.5 08/07 07:37:41.616
<134>
192.168.0.5 08/07 07:37:41.619
<134>
192.168.0.5 08/07 07:37:41.621
<151>DLG Terminated 3a2888
192.168.0.5 08/07 07:37:41.623
<151>Sess Terminated 3dd0c4
192.168.0.5 08/07 07:37:41.626
Any further help greatly appreciated as I'd love to get this working but am running out of ideas...
07-07-2011 04:44 PM
What do you get when you just use step 1? Eliminating steps 2 and 3, try without the reference to 127.0.0.1.
07-07-2011 05:50 PM
Ni Nseto,
I'm a bit unclear re: the above. Do you mean something like:
Hunt Groups:
2102:cfwd=vm2102
AA DP2:
(<1:2102>)
Thanks.
07-08-2011 08:40 AM
yes
07-08-2011 09:30 PM
Same result unfortunately:
<159>AVT Rx Start Tone: 1
192.168.0.5 09/07 14:28:31.747
<159>AVT Rx End Tone
192.168.0.5 09/07 14:28:31.827
<159>[AA]: xfer to target=2102
192.168.0.5 09/07 14:28:33.786
<151>CC:BlndXferTgt:2102
192.168.0.5 09/07 14:28:33.788
<151>Calling:2102@192.168.0.5:6060
192.168.0.5 09/07 14:28:33.799
<151>[7:0]AAA Rel Call
192.168.0.5 09/07 14:28:33.800
<151>[7:0]AAA:Destory SAA OBJ
192.168.0.5 09/07 14:28:33.800
<134>pri--REFER-->BCC:target=2102@192.168.0.5:6060
192.168.0.5 09/07 14:28:33.804
<134>pri--REFER-->BCC:target=2102@192.168.0.5:6060
192.168.0.5 09/07 14:28:33.805
<134>[BCC]CallRoute:
192.168.0.5 09/07 14:28:33.806
<134>[BCC]CallRoute:
192.168.0.5 09/07 14:28:33.806
<134>[2]No Resource to Bridge Blind Xfer 2102
192.168.0.5 09/07 14:28:33.806
<134>[2]No Resource to Bridge Blind Xfer 2102
192.168.0.5 09/07 14:28:33.807
<134>[2]->203.55.229.194:5060(483)
192.168.0.5 09/07 14:28:33.818
<134>[2]->203.55.229.194:5060(483)
192.168.0.5 09/07 14:28:33.818
<134>
192.168.0.5 09/07 14:28:33.819
<134>
192.168.0.5 09/07 14:28:33.819
<134>[2]<<203.55.229.194:5060(380)
192.168.0.5 09/07 14:28:33.860
<134>[2]<<203.55.229.194:5060(380)
192.168.0.5 09/07 14:28:33.860
<134>
192.168.0.5 09/07 14:28:33.862
<134>
192.168.0.5 09/07 14:28:33.862
<151>DLG Terminated 3a1c58
192.168.0.5 09/07 14:28:33.862
<151>Sess Terminated 3ac5a4
192.168.0.5 09/07 14:28:33.862
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide