Sorry, the specific setting is PriSw5ESS (but when I talked to my PRI provider, they could only set it one of 2 ways -- 5ESSCustom, and NI2 - so I assume 3COM's 5ESS is 'custom'). My trunktype is E&M Type II Also, the only cause code that I could get to work with my PRI vendor is cause code 58. This allows me to return busy signals to the switch on all trunks full, or when channels are busied out. I played with all of the other possible settings that 3COM lists, and every single one would cause the switch to return an intercept like "all circuits busy", or "call cannot be completed as dialed". While they all have the same result, to the end user, they understand BUSY - they don't understand intercept messages. Generally speaking, NI2 is usually preferable in the PRI provider's eyes as it offers a bit more for 2-way PRI users (folks who use it for DID, DOD and call-by-call service). But since we don't use PRI's that way, we'd much rather have service messaging capabilities. Of course, your PRI vendor may play nicer with the DSP, so your mileage may vary ;-/ -- Scot
-----Original Message----- From: usr-tc-admin@mailman.xmission.com [mailto:usr-tc-admin@mailman.xmission.com] On Behalf Of Kirk Mitchell Sent: Monday, April 01, 2002 5:07 PM To: usr-tc@mailman.xmission.com Subject: RE: [USR-TC] More NI2 issues
At 04:12 PM 4/1/02 -0500, Scot Desort wrote:
Kirk-
On my 2051 cards, I could not get busy-out to work no matter what I did when I had NI2 PRI's. Swithced to 5ESSCustom, now it works like a charm.
5ESS is an option in the truck settings, but there's no 5ESSCustom there.
From what I understand, it's a 5ESS switch that I'm on, but the provider told me that NI2 would be a better setting.
-- Kirk Mitchell-General Manager mitch@keyconn.net Keystone Connect Unlock Your World Altoona, PA 814-941-5000 http://www.keyconn.net
_______________________________________________ USR-TC mailing list USR-TC@mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc