cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Anonymous
Not applicable

Isdn TmState Messages

Jump to solution

Does anyone know of document describing the ISDN TM messages recieved in Syslog?  I am seeing a large number of Isdn TmStateOutbound Deliver - rcvd unexpected CallRelease messages along with some other messages and am looking for something that will describe what the various messages mean so I know if I have an issue to troubleshoot or if it is standard type messaging.

John Wable

Labels (1)
0 Kudos
1 Solution

Accepted Solutions
Anonymous
Not applicable

Re: Isdn TmState Messages

Jump to solution

I understand John. 

Since not all isdn TM messages you may see indicate a dropped call or a problem, you would need an isdn l2-formatted debug (and possible more debug) to really get a handle on what is happening.  There are so many different isdn call states and the timing of the messages plays a big part in how the call is handled.  There is not a master list that relates a call state to a problem or single occurrence. 

Regards,

Geoff

View solution in original post

0 Kudos
4 Replies
Anonymous
Not applicable

Re: Isdn TmState Messages

Jump to solution

Hello John,

In order to know the exact nature of the message you would have to do a sip, isdn l-2 formatted, and voice verbose debug.  Is the ADTRAN connected to an auto-dialer?  I have seen some instances where call control messages are not received by the CPE and messages like that come up when a call or duplicate call gets torn down.

If you want to pursue this in more detail you can also open a ticket with Technical Support.  Let me know if you have any questions.

Regards,

Geoff

Anonymous
Not applicable

Re: Isdn TmState Messages

Jump to solution

I was just looking for information on what the different messages mean so as we get different messages reported in SYSLOG we would be able to proactively react to errors from our devices in the field. 

Anonymous
Not applicable

Re: Isdn TmState Messages

Jump to solution

I understand John. 

Since not all isdn TM messages you may see indicate a dropped call or a problem, you would need an isdn l2-formatted debug (and possible more debug) to really get a handle on what is happening.  There are so many different isdn call states and the timing of the messages plays a big part in how the call is handled.  There is not a master list that relates a call state to a problem or single occurrence. 

Regards,

Geoff

0 Kudos
Anonymous
Not applicable

Re: Isdn TmState Messages

Jump to solution

Thanks what you stated makes sense.