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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

call diconnecton mx one

Status
Not open for further replies.

teenu3

Technical User
Jul 20, 2012
98
IN
Hi all,

The mx one is connected to an external SIP pabx with two E1.
The mx one is connected to pstn with two E1.
SIP system calling the PSTN Thru mx one.
now some calls from the SIP SYSTEM are disconnecting and they get the
report as follows.

1) 0fc183a27b5ada83076279cc0d6c53e1@192.168.30.28 This call is OK
2) 434c23977596a09c4985c782543c73fd@192.168.30.28 This call was cancelled by the SIP side (Asterisk). It can not be considered as a failed call.
3) 0e923ca877f47bcb556e512e272f51c3@192.168.30.28 This call is OK
4) 79251a6a40d781ee347705585881ca5d@192.168.30.28 This call was cancelled by the SIP side (Asterisk). It can not be considered as a failed call.
5) 4c8752e76055dbc027bc3db20fa54cc1@192.168.30.28 This call is OK
6) 3dc0060d24ef29ff7eecae482dced10d@192.168.30.28 This call is OK
7) 35c47bed046f85b92f4d735f44f39420@192.168.30.28 This call is OK
8) 16eb7cd03582be5328cc413c68844488@192.168.30.28 This call is OK
9) 1ddf0c43023263017b99d2ad7ea3e788@192.168.30.28 This call was cancelled by the SIP side (Asterisk). It can not be considered as a failed call.
10) 303c8a6723e4b3071ce78ff64751e839@192.168.30.28 This call was disconnected by the PSTN side with ISDN release cause 31.
11) 15cfca9c3911701a471835fe3f58b25c@192.168.30.28 This call was disconnected by the PSTN side with ISDN release cause 31.
12) 34a52c910987811c4b81476d17df2cd1@192.168.30.28 This call was disconnected by the PSTN side with ISDN release cause 31.
13) 6bb8d7d05fb3bdee449f47c824b78c2c@192.168.30.28 This call is OK
14) 75d06f7d30bf0b4349af933f295ffebf@192.168.30.28
15) 5284d5fc300133a260e464b9602966ac@192.168.30.28 This call is OK
16) 4f00cbc9204512846b0121cd6438a478@192.168.30.28 This call was disconnected by the PSTN side with ISDN release cause 31.
17) 56a49ee57a51acaa63af3c376cf9f18e@192.168.30.28 This call was disconnected by the PSTN side with ISDN release cause 31.
18) 7301244b3a2efd637e8b574719eb1c33@192.168.30.28 This call is OK
19) 68f8be87170350a8630dff477e27a3bd@192.168.30.28 This call is OK

i don't have a clue what is the release cause 31.

any suggesson please.
mx one some time giving ALARM CODE 38.

Regards
 
Remember, Google is your friend-
Cause No. 31 - normal. unspecified.
This cause is used to report a normal event only when no other cause in the normal class applies.

Can we assume that this is the same TSW SP8 system you have asked about before? As a rule, to save time it is best to state up front the release and sp level of the system.

At the risk of repeating myself =
"As a start I would do HIREI; then wait for a report of a call release and then do HIEDP; HIMDP; to see if there are any lost signals to indicate a TSW software fault.

If the connections are ISDN (SLP60) to both PSTN and PABX A then do-
STISR;
STUNI:LIM=?,UNIT=SLP60;
wait for a call release error then do-
STTSE:TRI=1;
STRAP:TRI=1;
Log the output to a file and run it through STI (part of SAM toolbox) which will give you an idea of what is releasing the call."

Good luck
 
Thanks himdp,
it is the same tsw sp8,
i will do your suggessions and let you know the result.

Thanks once again
Regards
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top