800 DID issue 1

[Telecomboy]

Anyone have any thoughts:

Upgraded customer from Merlin Legend R7.0 to Merlin Magix R3.0 in December. All programming remained the same. Ever since the upgrade, sporadic DID calls go to the reception vs. the extension they should go to (this is happening more times than not). I have replaced the DID trunk module, then the processor to try and fix, but the problem still continues.

Is there a programming difference in the settings between a Legend and a Magix?

Any thoughts/help would be greatly appreciated.

 

[merlinman]

Are your D-I-D calls ROTARY or TOUCH TONE?

Do you have enough Touch Tone Receivers?

-OR- are you having problems with your TTR's?

I'd test them and see if there is a bad one.

It's been known to happen.

 

[Telecomboy]

The DID's are touch tone. They have the following config:
412 TDL (4 touch-tones)
412 TDL (4 touch-tones)
800 GS/LS (2 touch-tones)
800 DID (2 touch-tones)
016 TTR (4 touch-tones)
M. Messaging (2 touch tones)

If they have a bad TTR on one of the 412's, would that cause this type of problem? or will it only effect it if the bad TTR is on the 800 DID module?

 

[merlinman]

The deal is, Touch Tone Receivers are a "SHARED" resource, meaning that no matter where they are, they are used when needed.

Thus, my idea of testing the TTRS is a valid one.

(Or, you could cheat and have the CO change to ROTARY and you could do so as well.)

That could be a cheap way out if you do prove a bad TTR on one of your modules.

 

[Telecomboy]

Thanks for the input Merlinman. I will go back and test the TTR's.