callone

We are having problems with a new install of Merlin Magix. We have a PRI connection (NI2) to a DMS500 in the CO. We can call international, most 800 numbers and locally (10 digits). However, we are not able to dial any 1+ long distance nor some 800 numbers. The phone company tech attached his t-berd and is able to make all calls. Of course the phone company is saying that it is the phone system having problems. Our confusion comes in where we are able to dial international and the phone tech says that their trace is showing that the DMS is only receiving 10 digits. Has anyone run across this issue before? Thanks.

Cephas

I have been running into all kinds of problems lately with DMS-100's, so would imagine the DMS500 would be the same deal. I suspect Nortel has recently released a new firmware load for their DMS's, as I'm seeing the same problems show up at more and more sites lately, presumably as they roll out the upgrades.

First thing you need to know is that in the Nortel world, the only kind of PBX that exists is made by Nortel. If you have a non-nortel PBX they consider any issues you might have with their "non-standard standards" to be your problem. They also cannot do NI2, they only support NI1 - you mentioned NI2 in your post. Make sure your switchtype for the PRI is set to DMS100 and see if that helps. Also, make sure they are NOT sending you callerID name as this causes all kinds of problems also - they send it in the wrong ISDN layer 3 information element and the magix hates it.

I am currently working on a big problem where they are no longer providing an inband busy tone over PRI, but rather only sending a cause 17 (busy) disconnect code and expecting the PBX to provide the busy tone. You know you have this problem if you dial a busy number and the call disconnects, apparently for no reason, instead of hearing a busy signal. I've seen this show up on magix, IP Office, and definity in certain areas which reinforces my theory about a new load for the DMS. On IPO you can just tick "local busy tone" in the system tab to solve this problem. Will let you know once I find out a solution on Magix.

In the meantime, like I said make sure your switchtype is set to DMS100 and not NI2. If you like, printout your T1 and PRI settings and email the text files to peters@toneperformance.com and I'll look them over for you.

Peter

PBXtech.info

 

SMILEE9

I work for a CLEC with a DMS 500 and anytime we give NI-2 PRIs to Avaya equipment, we usually have to go NI-1. You will set the PBX for DMS 100. Of course the customer will not be able to receive alpha-numeric caller id... only numeric.

Brazil

Magix does not like NI2. NI1 sometimes works, but if the LEC can do "Custom", that is the preferred setting.

pepperz

Can you verify that the calls you make that are going through or failing are actually going via the PRI or perhaps backup CO trunks?