-
1
- #1
I had an new IPO benched and tested on a PRI on working off of a DMS100; all calls progressed inbound and outbound without a problem. I took the system to a cusotmer site in another community serviced by a DMS10 and all we could get was a busy for outbound calls even after we added the NI2_CALLED_PARTY_TYPE=UNKNOWN to the No User. The DMS10 only will accept NI2 but the only way the calls would go out was to change the PRI setting as if we had a 5E in the CO. The calls would go out but then if we had to re-boot the system, the PRI channels would not return to IDLE but went into Out Of Service status. The CO network engineer had to put them into service manually one at a time while we were endeavoring to figure this out which was extremely frustrating.
After assistance from another Avaya partner this is what I learned:
A) If you encounter this problem the temporary solution to retore the PRI channels is to tell them they are NI2 and reboot. The channels come up but the calls won't go out. Next you change the PRI to 5E but only MERGE - do not reboot. The calls will go out and the channels will all be inservice.
B) The way to get rid of this problem is to upgrade to 8.1.(73) which just released. We spent a lot of time with our stocking distrubutor's tech support and then engaging another partner for support due to this issue.
I am making this post in hopes that someone else will benefit from this information and be saved a lot of frustration and wasted time while on a customer site.
After assistance from another Avaya partner this is what I learned:
A) If you encounter this problem the temporary solution to retore the PRI channels is to tell them they are NI2 and reboot. The channels come up but the calls won't go out. Next you change the PRI to 5E but only MERGE - do not reboot. The calls will go out and the channels will all be inservice.
B) The way to get rid of this problem is to upgrade to 8.1.(73) which just released. We spent a lot of time with our stocking distrubutor's tech support and then engaging another partner for support due to this issue.
I am making this post in hopes that someone else will benefit from this information and be saved a lot of frustration and wasted time while on a customer site.
