cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1112
Views
0
Helpful
1
Replies

debug result

miskoolak
Level 1
Level 1

hello everyone

here is my debug messege

can anyone fine the reason and the solution?

ct 16 11:00:49.147: ISDN Se0/0/0:15 Q931: Applying typeplan for sw-type 0x16 is 0x0 0x0, Calling num 8

*Oct 16 11:00:49.147: ISDN Se0/0/0:15 Q931: Applying typeplan for sw-type 0x16 is 0x0 0x0, Called num 2830

*Oct 16 11:00:49.151: ISDN Se0/0/0:15 Q931: TX -> SETUP pd = 8 callref = 0x008E

Sending Complete

Bearer Capability i = 0x9090A3

Standard = CCITT

Transfer Capability = 3.1kHz Audio

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA9838A

Exclusive, Channel 10

Progress Ind i = 0x8183 - Origination address is non-ISDN

Calling Party Number i = 0x0080, '8'

Plan:Unknown, Type:Unknown

Called Party Number i = 0x80, '2830'

Plan:Unknown, Type:Unknown

*Oct 16 11:00:49.243: ISDN Se0/0/0:15 Q931: RX <- SETUP_ACK pd = 8 callref = 0x808E

*Oct 16 11:00:49.247: ISDN Se0/0/0:15 Q931: TX -> STATUS pd = 8 callref = 0x008E

Cause i = 0x80E018 - Mandatory information element missing

Call State i = 0x01

*Oct 16 11:00:49.271: ISDN Se0/0/0:15 Q931: RX <- CALL_PROC pd = 8 callref = 0x808E

*Oct 16 11:00:49.275: ISDN Se0/0/0:15 Q931: TX -> STATUS pd = 8 callref = 0x008E

Cause i = 0x80E018 - Mandatory information element missing

Call State i = 0x01

*Oct 16 11:00:49.283: ISDN Se0/0/0:15 Q931: RX <- ALERTING pd = 8 callref = 0x808E

*Oct 16 11:00:49.287: ISDN Se0/0/0:15 Q931: TX -> STATUS pd = 8 callref = 0x008E

Cause i = 0x80E018 - Mandatory information element missing

Call State i = 0x01

*Oct 16 11:01:05.367: ISDN Se0/0/0:15 Q931: TX -> DISCONNECT pd = 8 callref = 0x008E

Cause i = 0x8090 - Normal call clearing

*Oct 16 11:01:05.439: ISDN Se0/0/0:15 Q931: RX <- RELEASE pd = 8 callref = 0x808E

1 Reply 1

irisrios
Level 6
Level 6

“Mandatory information element missing” indicates that the equipment sending this cause has received a message which is missing an IE that must be present in the message before the message can be processed.

Channel is always mandatory in the first response we receive from the peer. But, for the user-side, some implementations allow user not to respond with a channel-id in which case network-side need to assume the channel that was sent in SETUP.