Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

81C signaling Server

Status
Not open for further replies.

rlgriffin

MIS
Oct 26, 2004
34
US
I have a large campus utilizing sip trunking. I was wondering if anyone could help decipher the folowing:

PRI241 DCH: 81 DATA: 000000D1

PRI241 DCH: 81 DATA: 000000D0

ELAN025 tcp error: tcp write fail too many times!! ERRNO is 70.

I had the PRI241 DCH: 81 message scroll numerous times across the screen then the tcp error then my primary signaling server went down. My failover SS took control then my primary SS reestablished.

DCH 81 is my SIP route.
Any ideas?
 
PRI0241 Protocol Error: No response from far end to this PRI call. Output data: DCH: x
DATA: y . Where: x = D-channel number and y = B-channel number.
Action: Report problem if condition persists.
 
that could be as simple as a bandwidth problem or a missing patch... either way, the B channel didn't link.. barrier to barrier blocking can be almost anyting from protocol to timer.. timers might be a good place to start since it does not fail every time

john poole
bellsouth business
columbia,sc
 
SIP or H323 virtual trunk establish the DCH between PBX and SS. If you have a protocol error, one of these 2 equipment is involved. CHeck patches on 81C and on SS.

I guess that a configuration fault is not the cause of these errors
 
... but curious that a SIP trunk create PRI messages!!
Are you sure about this SIP trunk?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top