DN extenson to Enternal number

[firefoxfire]

I thought it best to start a new thread.

Customer has a MICA 4.1 and NAM 4.1 set for immediate answer. They want to be able to have callers dial a 3 digit extension that will then ROUTE out of the system automatically to an external number.

I have tried this by setting a ROUTE 333 then DEST CODE 333 to xxx-xxxx but when I dial into the name it says then extension is invalid.

 

[allworxguy]

You're barking up the wrong tree, You can't dial a dest code from the AA, only a DN or CCR tree.

Marv

http://www.telemarv.ca

 

[firefoxfire]

beg to differ. I just tested it with the system b of a large MICS installation and it worked just fine. I setup code 701 to ring an external number and it works just fine.

that's why if I was able to get that to work I am wondering why I can't get it to work on system a or another installation.

 

[firefoxfire]

I was also able to get system-A to do the same thing and it works just fine from the NAM 4.1 with immediate answer.

This large installation is using 7.1 XC

Now I did try it on another instillation that only has a single MICS 4.1 with a NAM 4.1 and I am unable to get it to route the call out.

DO you know why the NAM would deny routing the call?

 

[firefoxfire]

P.S> but it is using a NAM 4.1

 

[curlycord]

Because that NAM was not patched and had network transfer allowed is why dest code allowed transfer to public.

Tell your client it cant be done and be done with it once and for all.




=----(((((((((()----=
curlycord

http://www.curlycord.com

 

[hawks]

The system that it worked on was is using MCDN with a CDP set up. The one it don't work on is not, if you use MCDN then you can call out to an invalid extension from the NAM becaue it sees it as a networked call.

 

[firefoxfire]

yes that is correct. As a workaround could I not connect an a s m module I'm in permanently program those extensions for call forwarding?

 

[curlycord]

That is what I was referring to in a way.
For the MCDN to work network transfer must be enabled on the NAM.

If one NAM is patched with the Toll Fraud patch then it wont let you per my last post.


As for ASM it should work since its a device.
Try Link * 4 plus dest code.







=----(((((((((()----=
curlycord

http://www.curlycord.com

 

[firefoxfire]

When you mean LINK * 4, where s this entered?

By the way if a DEST CODE could be able to F71 wth a few F78's at the end then the call could flash, dial and should drop the line. This way the centrex feature could be used to save resources.

 

[hawks]

You can do the use the F71 & F78 with the call forward but I don't think your going to be able use them on Desti codes.

 

[firefoxfire]

F78 works but nothing else.

 

[firefoxfire]

I am passing this valuable information on to everyone from the Nortel expert Eddie from MySupportGuy.Net. this information has cleared up this issue. I upgraded a client today who has MICS 4.1 and NAM 4.1 to MICS 6.1 with the same NAM 4.1 and it worked beautifully! Extensions ( DNs ) using virtual numbers i.e. 301 internally and externally via the NAM AA were routed properly every time:


FROM EDDIE:
To answer your question about why some work and some don't, keep this in mind.

In order to use Norstar Voicemail to dial destination codes, three requirements must be met.
1) The NVM must be 4.1
2) The Norstar must be 6.0 or higher
3) The NVM must not have the NVM Toll Fraud Patch for CAA applied.

It's the combination of the Norstar software version and the NVM software version.