Can't forward to auto-attd 1

[LegoGirl]

Hello all! I am working on a remote option 11, release 20. One of my outgoing trunks displays xxx-8346 on the called party's caller ID. When folks on the outside tried to call this number back, it was RNA. This of course was not good for business. The user wants this number to go to an auto-attd box. After doing a few coordinated traces, we were able to determine that xxx-8346 is the BTN, it comes in on trunk 8 16, and points to extension 2000. As 2000 was not in use, I turned it into an ACD, with NCFW to voicemail. Now when you call xxx-8346, it rings to voicemail, but you get an error message from MerMail saying this is not an available service. However, if you call 2000 directly, you get to the auto-attd box created for 2000. The traces still show that trunk 8 16 points to 2000.

How can I make xxx-8346 go to the auto-attd box set up for 2000?

Thank you in advance for any help!

Marie Curie

 

[johnpoole]

go to your voice service dn table and add it their, you'll need to use the sme voice service as the menu... fromt he main menu options 3 4 and 1

john poole
bellsouth business
columbia,sc

 

[N2NT]

Set up an IDC table and send the DNIS digits 8346 directly to 2000.

 

[LegoGirl]

John,
I have already added 2000 as the voice service and menu. You can reach it just fine by dialing xxx-2000. Just not by dialing the BTN xxx-8346 (which points to 2000). I thought maybe the ACD part was screwing up the routing, so I turned it into a private line on a 2008, but it would not hunt or forward to voicemail, even as the only appearance on the mock set.
N2NT,
I set up an IDC table with digits 8346 being sent to 2000. I still get the same error message from MerMail. I wrote down the message this time: "That voice service application is not defined or cannot be accessed through this service." You only get that message when dialing the xxx-8346, but not when dialing xxx-2000.

Any other ideas? Thank you both for your suggestions, by the way.

Marie Curie

 

[Nortellian]

in mail point 8346 to same voice service number you pointed 2000 too.

 

[LegoGirl]

Nortellian,
Do you mean to set up a voice service DN pointing to the menu service 2000?

 

[johnpoole]

yes that was what i tried to put in my post, wording could have been better

john poole
bellsouth business
columbia,sc

 

[N2NT]

I am guessing you got it by now, by adding the voice service ID...It looks like the DNIS is 2000 and it might work if you IDC 2000 to the auto att DN. It's basically what you are doing with the ACD ncfw though, just a matter of how you are getting it there.

 

[johnpoole]

fyi for n2nt, the big diff between an acd maxp 1 is that the number although being forwarded retains the original dialed digits..ie.. dial the acd 3000.. go to load 23..ncfw to mail acd-dn 4000... you'll get the mb or voice service dn for 3000... if you put 3000 in an idc table you'll get the voice service of for the output of 3000... you could put the dn in idc and point it to the menu service...after a call is reaches a station or acd group, the dialed dn is part of that call process forever...

john poole
bellsouth business
columbia,sc

 

[LegoGirl]

I have 2000 as a voice service DN. This still does not work, unless you dial 2000 directly. Dialing the xxx-8346 still gets that error message. These are the things I've tried:

*2000 has been set up as a voice service DN, with menu service. It has been this way before I tried the rest of these steps.
*8346 in IDC table, pointing to 2000
*2000 set up in PBX as ACD, with NCFW to 2099 (voicemail)
*Removed ACD 2000, and set up 2000 as private line on 2008 set, with HUNT and FDN to 2099
*Removed PRL 2000, and set up 2000 as normal SCR on 2008 set, with HUNT and FDN to 2099

None of these steps have worked, exept to allow me to dial xxx-2000. For some reason that BTN xxx-8346 still gets the error message.

 

[techman3030]

set up 8346 as a voice service dn and set it to use the menu service ID that 2000 uses. If it comes in on the trunk as 8346 set up ext. 8346 as an ACD and ncfw to mail. I think this is what Nortellian and John Poole said earlier.

 

[LegoGirl]

Techman,
I have set up 8346 as a voice service DN, to point to menu service 2000 (which is what the voice service DN 2000 was using). This did not work. It appears to me that 8346 comes in on the trunk as 2000, but I tried both ACD 2000 and ACD 8346, each pointing to 2099 (voicemail). I tried this also with both 8346 and 2000 set up as voice service DNs, at different times. This did not work. I am posting the trace, so y'all can see how xxx-8346 comes in:


ACTIVE TN 008 16
ORIG 008 16 COT RMBR 0 16
TERM NONE
TDTN 1 SLOT 19 PTY SLOT 19
DIAL DN 2000
MAIN_PM WAIT AUX_PM
TALKSLOT NONE
EES_DATA:
NONE
QUEU ATTN
CALL ID 0

Thank you for your continuing help!

Marie Curie

 

[johnpoole]

set 2000 up as a maxp 1 acd ncfw to mail, then put 2000 in MM as a voice sevvice dn with the service id your menu service dn...i have several that work that way

john poole
bellsouth business
columbia,sc

 

[LegoGirl]

John,

That is how I set it up originally. I can dial 2000 directly and hit the voice service DN just fine. It's when I dial the xxx-8346 that I get that error message.

 

[johnpoole]

if you dial 8346 what do you get?... set it back up that way and also put the idc of 8346 to 2000 in load 49 and apply that table number to your did trunks.. is 2000 a voice service dn?.. if so how is it built in your switch. maxp 1 acd?.. if you can dial it internal, and you are rec 4 digits on your did's the the idc should translate it clean. if you have 2000 as a steering code, then make sure asup is set to yes...answer supervision is necessary to auto term a did..

john poole
bellsouth business
columbia,sc

 

[LegoGirl]

John,
Currently, I do not have 8346 set up as an extension in the PBX. If I dial xxx-8346, I get the MerMail error message from before. Right now, 2000 is set up as a voice service DN, and as maxp 1 acd in the switch. Dialing 2000 works fine; I get no error message and I go to the auto attd. The xxx-8346 number is a CO line. When I dial that number, I get the error message, even though the trace in LD 80 says the trunk (8 16) has a dial DN of 2000. I have tried setting things up every which way to get it to work, but right now, 2000 is set up as an acd in the switch, and as a voice service DN in the MerMail. I have also set it back up to have 8346 in the IDC table pointing to 2000. I was ignorant on applying the IDC tables to the trunks. You said to apply it to the DID trunks, but 8 16 is a CO trunk. Should I still apply the IDC to DID, or rather to CO trunks? And if to CO, how is that done? I tried to change the RDB, but never saw the IDC prompt.

Thank you for all your help!

Marie Curie

 

[johnpoole]

if your on a pri, the dialed dn may show the area code plus the 7 digit number, i had a problem with that, adding the 10 digit number as a ext on that users md worked.. don't know if a 10 digit will work as an access dn.. is this a number that comes in as a did? or does it come in as on a single route.. if your that lucky, set auto to yes in the rdb and 2000 and the att dn for the trunk, your set up is right, to test my theroy, put the full 10 digit number on your md as an ext and try calling it.. at least then you'll know why the mail don't see the 4 digit number when you test 9+

john poole
bellsouth business
columbia,sc

 

[LegoGirl]

John,
The line does come in on a single route. I set auto to yes in the RDB, and the ATDN to 2000. Works perfect.

THANK YOU!!!

Marie Curie

 

[johnpoole]

that one took a while, glad to see we found it..

john poole
bellsouth business
columbia,sc