? about PRI Switch Type and Network Service 3

[thephonelady]

Under what circumstances would you use Merlin-Pbx as the Switch type and ElectandNtwk as the Network Service? I ask because a client with CBeyond is having trouble and the Pri is down. The D channel showes inoperative and I know it's a CBeyond issue...isn't it always!!! This is what the printout shows as settings. As soon as I changed the switch type to 5ess the d channel came up but still no service and the client was on hold for over 45 minutes trying to get someone to help them from CBeyond.The client seems to think CBeyond changes the swithc settings on their end but the current settings confused me a bit. Thanks for any help!

 

[merlinman]

The two switch types you mentioned are for connecting 2 (or more) Merlin-PBX Systems together.

9 times out of 10 with such a failure (on a previously working circuit) is the Vendor's problem and it's due to their equipment changing from NI-1 to NI-2.

When C-Beyond first hit the street we had to really work with them to get the Legend/Magix to work with their stuff. Somewhere in their Engineer Notes is the information they came up with to make it work. After the first bit of Heart Burn dealing with them, when they referred to those notes, all was good.

I have had so many INTERFACE DEVICES (from various vendors) get hit with a POWER OUTAGE and come back up with the WRONG DEFAULT that I have pretty much determined that's the main reason these PRI circuits fail. Of course, the Vendors all point to our "outdated" equipment.

Once you can get them to set their DEFAULTS to be the correct settings, problems go away, and stay away.

Good luck!

http://home.comcast.net/~merlinman

-merlinmansblog.blogspot.com

 

[CarGoSki]

The best way to communicate with a cbeyond IAD is for your side to be set to 5ess and for them to be set to 5E custom. They are probably set to NI2 or something other than 5E custom.

If you know the password for monitor you could "trace prigon 1" and see the dchannel messages. Recently a provider had an issue where they had to downgrade their IOS to a previous build. Their connection to Merlin was flooded with extraneous service messages that Merlin did not understand. Not a good thing for stability. This can be seen in monitor.

 

[thephonelady]

Thank you all for your input. As I thought it was a CBeyond issue with switch type. They were set for NI1 not 5ESS as it was previously set for. After changing it back it worked perfectly! There is still something not kosher about this though. When I first got out there the PRI settings were Merlin-Pbx and ElectandNtwk as the Network Service. I originally turned up this PRI in 11/12 and had the printout of how I configured it on my laptop just because...so I know something happened and the contact is not on site so he did not make any changes.I know those settings don't change by themselves. I could not make changes on the pri settings for some reason- maybe corruption?? I ended up having to remove the 2 100D boards and do a board renumber and put them back in and reprogram the PRI. That brought the PRI back up but there was also a T1 linking the Merlin to a few other systems. I had printouts of that too and reprogrammed it but the T1 doesnt work now and I get a fast busy when I try site to site dialing. The T1 is set for ESF B8ZS Rob-Bit.
Pool is 895 and all 24 channels are assigned. The UDP tables are correct. And ideas on what else to check that would have been wiped out when I did the board removal and renumber adn reinstall the boards? I know I am missing something. There is a yellow light on the NIU board next to HCRC. All channels are set to Wink Wink.
Any help is greatly appreciated.

 

[merlinman]

Your post is somewhat confusing. You speak of PRI, and then you talk of Wink-Wink.

Is Pool 895 NOT part of the PRI Issue?

If that's the case, please print it out and let us look at it here. Also, where does your T1 Time off of?

http://home.comcast.net/~merlinman

-merlinmansblog.blogspot.com

 

[thephonelady]

Sorry Merlinman- I was tired when I wrote that last response. The PRI issue is fixed but I inadvertantly caused another. In addition to the PRI they have a T1 ckt that ties the Legend to 3 other locations, 2 of which are IPOffices. The 895 pool is the tie lines/T1 and I can't get it to work. I was having trouble making changes on the PRI so I removed both 100D boards and did a board renumber to wipe out all the PRI setup. This wiped out the T1 settings also. The 2nd ckt/T1 is set for ESF/B8ZS Common Channel and that was the original setting before I wiped it all out. All 24 channels are in the 895 pool which is the primary route for the non local udp. The extension ranges are correct in the udp table as that stayed intact. I am not all that familiar with tie line settings but do know the channels are set for wink/wink. What else should I look for?? I hope this clears things up.
Thanks!

 

[CarGoSki]

You should elaborate more on what you are connecting to: What is the other side: Merlin; Telco; etc
Since you mention UDP I suppose another Merlin? If so then I would provision the Merlins and Merlin-PBX and Merlin-Network and not as TIE trunks. You can have centralized voicemail with a Merlin network. Make the side with the voicemail card Merlin-Network since Merlin-Network setting is for Central Office emulation and Merlin-PBX is for PBX emulation.

 

[thephonelady]

Let me try to do a better job of explaining the issue. They have a T1 that is used to connect the Legend at my site to a few other systems 2 of which are IP Offices. Before my screw up,the circuit in the Legend was set for T1/ESF/B8ZS/Common Channel. All channels are in the 895 pool and that is the route for dialing site to site. The chk goes from the NIU to an Adtran TSU/ACE unit and into the 100D. Nothing has changed from the NIU to the TSU/ACE. But there is an amber light on the NUI next to HCRC.I think my issue is with some settings on the Legend (possibly Tie options??)since I removed both 100D'd and did a board renumber to fix an issue with the PRI they have. The PRI is up now. When I did the renumber it slipped my mind that they had the T1 also but I did have some info on the original T1 settings and pool info. I hope this makes my screwup/issue a bit clearer.
Thanks for bearing with me.

 

[wireboy]

common channel signaling and wink start are conflicting settings. either is valid, but not both.

42

 

[CarGoSki]

https://downloads.avaya.com/css/P8/documents/003750139

> for connecting IPO to Merlin via TIE trunks

I have connected Merlin and IPO via PRI before by programming IPO as normal PRI 5ess and set to CO
Merlin is normal programming for PRI.

 

[thephonelady]

Thank you for the link. I will be heading out there tomorrow and hopefully get this working.

 

[thephonelady]

PROBLEM SOLVED!!!! Thank you all for your input and thank you CarGoSki for the AVAYA link. That helped me get the point to point working. I went through the Legend programming step by step and when I got to the step where you assign all the channels as tie trunks I said "Uh Oh!". As soon as I put all 24 channels in as tie trunks it magically started working!Have a great weekend all!

 

[CarGoSki]

thanks for the star