Error Code 803 Legend T1

[adc110]

I have a customer with a Merlin Legend CKE4 with a 100D module that is connected to their provider's Adtran. They are giving me a partial T (12 channels). Apparently the service provider decided to displace their switch at their CO with a new switch and moved the circuit over to their new switch about 3 weeks ago. We were unaware of this as it was done on a Sunday early morning. In any case, right after this we started getting a loud "BEEP BEEP BEEP........" after making a few successful calls. This happens to all users. I tested this and out of the 12 channels, I seem to always have the ability of making 5-6 successful calls, then (like clock work!!) get this long quiet pause when making the next call followed by the loud "BEEP BEEP BEEP BEEP" sound which continues until I hang up. This will happen for the next 2-3 attempts at dialing out then I will get the next 5-6 calls which will be successful. All the while this happens, the error log is plagued with Error CODE 803 which apparently (according to Lucent description) is "No External Release:Communication problems between module and CO. Far end has not disconnected within 4 minutes. If error occurs twice consecutively, trunk is busied out automatically whether or not automatic trunk maintenance busy is enabled. Check the nework interface. Check for faulty cable."

This was continually happening and can be re-created everytime. I have checked everything and then after contacting the provider it was mentioned that they had swapped T1 circuit to a new switch at about the same time!! The last email that I got from their switch technician was this:
"I have had a live signal state trace on that T1 intermittently, and I am seeing a lot of call setups from you with seize, wink, then nothing, and seize, wink, partial dials, with another attempt immediately following on the next sequential channel as if the system was partial dialing and then seizing another line to try again. Another strange issue I saw was you had a channel go into a constant seize, wink sequence (constant seizure) until I killed the channel and brought it back into service (this only happened once) and it was right after I made the line hunt change per our last conversation."

Our T1 is ESF/B8ZS/RB Signaling/E&M WINK and each of our trunks are configured as follows:

A TRUNK 810Slot/Port :8/ 2 Toll
A Direction: 2 Way E&M Signal: Type1SDialtone: Remote
A InType : WinkInMode: TouchTone AnsSupvr: 300ms
A OutType: WinkOutMode : TouchTone Disconnect: 300ms

Does anyone have any ideas as to what is going on? Any help would be much appreciated!

 

[SYQUEST]

adc110,

I have some questions. What ADTRAN is being used for the 12 channels and when the tests are performed is it in the loop or removed?

Also what kind of NIU did the Telco install for the DS1?

I looked thru some of the Legend documents, the only timing related items I found was Disconnect and Answer timers. The description is not very good as far as how they function. You might want to look over those and may be make some adjustments and see if that helps. The adjustment range is pretty large and the value is in milliseconds. I suspect that the DISCONNECT timer may be the one to try, but let us know what your results are. In one of your earlier posts you showed the tie-trunk parameters and it said 300ms for timing.

....JIM....

 

[adc110]

I'm not sure of the Adtran model but will find out. The provider connects the T1 directly to their Adtran from the SmartJack on the wall. There is no other intermdiary equipment. Goes directly from Adtran to DS1 card in Legend. I will try the disconnect timers - perhaps increase them?

 

[phonesrus]

Maybe you might ask the service provider to provide some Metaswitch documentation regarding their E & M emulation.
Are they doing a full ABCD Bits, or like Cisco products and only doing the AB bit sequence. These bit sequences determine the validity on the setup. Are they doing Type 1 standard (T1S), or type 1 compatible (T1C), or something else? If the switch gets confused after several calls outbound, but has no apparent issues inbound then you have a compatibility issue in the Adtran (?? is the Adtran new or pre-existing??) or the Metaswitch, or both.
If it worked before, on the old switch, but not on the new, then the new switch is where the problem is.

My email tagline is from Sherlock Holmes " When all options have been examined and found wanting, that which remains, however illogical, is the solution!"

 

[adc110]

I cannot even begin to thank each of you "SyQuest, phonesrus, Merlinman" for taking the time to review this issue I had. It seems as though it has been "mysteriously" resolved. I did monkey with the disconnect timers (300 to 400ms) but somewhere in doing this the issue went away. Unfortunately I was not on-site and performed the change remotely and relied on an inside employee to perform tests for me. I'm not confident that this was the issue as the vendor was still reviewing the issue but all I can say is that the system is successfully calling out on all channels without error (for now!!! let's cross our fingers). I know what to suspect but sometimes things just work out. Thank you again for all of your assistance with this.

 

[merlinman]

Another Central Office "MIRACLE" I suspect.

Glad it's working.

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