Magix PRI and DID 1

[JSTagert]

I have 2 questions. We recently installed a PRI for our Merlin Magix.

1. Since the installation I have 2 extension that seem to be connected is some way. Example - When a DID call comes for extension 657 it rings on both 657 and 698. I have checked for coverage and found nothing, and I forwarded the extensions back to themselves, but the problem persist. The other day when a call came in on 657 the voicemail covered the message to 698. What am I missing?

2. When calls are placed to a client, and the clients phones are busy the call just drops. We don't get busy signals since we went to the PRI. Is this the nature of the PRI or can this be corrected in the Magix?

Thanks!

 

[jgideon]

PRI is 'smart' like SS7. The carrier is probably sending a result code back to the Magix that says 'destination busy' with the expectation that the Magix will play the busy signal. I've never used the Magix, so I don't know if that is something you can configure. You'll probably get similar results if the user dials a not-in-service number, too. I've usually tried to get the carrier to play the caller an annoucnement rather than getting the PBX to do it.

 

[JSTagert]

We get the announcements from the carrier such as out-of-service, but we can't get a busy signal. This is the first PRI I have been involved with, and I don't know much about phone systems. Do systems from other venders receive busy signals on PRI's?

 

[merlinman]

I really think you may have problems with the way the Magix is set up.

I had a problem the other day on a PRI and it proved to me that yes the SWITCH (in your case the Magix) does provide busy tones and ringing tones.

Our problem was a bad T1 card, but I think you may have some configuration issues.

Print the PRI tables out, you may have something translating 657 to go to 698 as well.

 

[Ghostin]

sounds like you have a cover button for 657 on 698.

Who originally installed the PRI? If you have issues, get your original vendor out to correct them. Sounds like the PRI was not installed properly.

 

[JSTagert]

I may not have explained the first part very well. The problem only occurs when a calls come in on the DID's. Internal calls are not effected. I can't find any coverage on either phone, and it doesn't matter which of the two DID's you call, both phones ring.

I will get in touch with our vendor, and have them look at the configuration. I was having a difficult time believing that the Magix couldn't provide busy signals on a PRI.

Thanks for all your help.

 

[Pepperz]

Renumber one of them to a number that hasn't given a problem. If the inbound calling is still an issue, then the problem is most likely a coverage situation.

Pepperz@charter.net

 

[JSTagert]

Could the Night Service be an issue? I found the following information, and it involves both of the extensions in question.

NIGHT SERVICE INFORMATION

OPERATOR 651 DGCG #: 7929
STNS : 651
LINES :

OPERATOR 657 DGCG #:
STNS : 698 657 7162
LINES :

The second operator list both extensions 698 and 657. Could this be causing the problem? I have not found any covers involving these 2 extensions.

 

[franke]

Only if the problem occurs when the night button is active or the Merlins business schedule indicates it's in nights. In which case any calls to 657 would ring all three extensions. Since the problem only occurs on calls over the PRI, I would agree that the first place to start is how the the PRI is set up.

franke

 

[JSTagert]

franke, thanks for the information. I checked the night service schedule and it looked fine. The start time was set to business closing time, and the stop time was set to business opening time. To satisfy my curiosity though, I removed extension 698 from the 657 operator group, and the problems between extension 657 and 698 went away.

Thanks again.

 

[franke]

That's bee-zar, that it should only have reared it's ugly head with the addition of the PRI or during the 'open' hours.

Sometimes there's no explaining what the electrons are up to

franke