From: Alejandro (a.cadarso@xxxxxxxxxxxxxx)
Date: Wed Jun 07 2000 - 16:03:38 GMT-3
Hi,
I had a simmilar problem with a NM-HDV-2E1 module in a 3640 I'm not sure
is the same bu it looks very much as yours:
12:42:12.654: ISDN Se1/1:15: TX -> SETUP pd = 8 callref = 0x016B
12:42:12.654: Sending Complete
12:42:12.654: Bearer Capability i = 0x8090A3
12:42:12.654: Channel ID i = 0xA98381
12:42:12.654: Called Party Number i = 0x80, '9228',
Plan:Unknown, Type:Unknown
12:42:12.714: ISDN Se1/1:15: RX <- CALL_PROC pd = 8 callref = 0x816B
12:42:12.714: Channel ID i = 0xA98381
12:42:12.758: ISDN Se1/1:15: RX <- ALERTING pd = 8 callref = 0x816B
12:42:12.758: Progress Ind i = 0x8081 - Call not end-to-end ISDN, may
have in-band inf
12:42:22.810: ISDN Se1/1:15: RX <- CONNECT pd = 8 callref = 0x816B
12:42:22.810: Connected Number i = 0x008030373739323238
12:42:22.818: ISDN Se1/1:15: TX -> CONNECT_ACK pd = 8 callref = 0x016B
12:42:22.918: ISDN Se1/1:15: TX -> FACILITY pd = 8 callref = 0x016B
12:42:22.942: ISDN Se1/1:15: RX <- STATUS pd = 8 callref = 0x816B
12:42:22.942: Cause i = 0x80E01C - Mandatory information element
missing
12:42:22.942: Call State i = 0x0A
12:42:22.946: ISDN Se1/1:15: TX -> DISCONNECT pd = 8 callref = 0x016B
12:42:22.970: ISDN Se1/1:15: RX <- RELEASE pd = 8 callref = 0x816B
12:42:22.974: Cause i = 0x80E0 - Mandatory information element
missing
12:42:22.982: ISDN Se1/1:15: TX -> RELEASE_COMP pd = 8 callref =
0x016B
I managed that the PABX connected to my router didn't send to me the
Connected Number i = 0x008030373739323238 and all began to work, I'm
using 12.1.2(T), perhaps there is any bug in the Q.931 protocol
implementation.
I also have another PABX connected to another Router and I have a
message:
Jun 1 13:46:41.852: ISDN Se1/0:15: TX -> SETUP pd = 8 callref =
0x00AB
Jun 1 13:46:41.852: Sending Complete
Jun 1 13:46:41.852: Bearer Capability i = 0x8090A3
Jun 1 13:46:41.856: Channel ID i = 0xA98381
Jun 1 13:46:41.856: Called Party Number i = 0x80, '9031',
Plan:Unknown, Type:Unknown
Jun 1 13:46:41.920: ISDN Se1/0:15: RX <- CALL_PROC pd = 8 callref =
0x80AB
Jun 1 13:46:41.920: Channel ID i = 0xA98381
Jun 1 13:46:41.984: ISDN Se1/0:15: RX <- ALERTING pd = 8 callref =
0x80AB
Jun 1 13:46:43.564: ISDN Se1/0:15: RX <- CONNECT pd = 8 callref =
0x80AB
Jun 1 13:46:43.564: Connected Number i = 0x8039303331
Jun 1 13:46:43.572: ISDN Se1/0:15: TX -> CONNECT_ACK pd = 8 callref =
0x00AB
Jun 1 13:46:43.684: ISDN Se1/0:15: TX -> FACILITY pd = 8 callref =
0x00AB
Jun 1 13:46:43.704: ISDN Se1/0:15: RX <- STATUS pd = 8 callref =
0x80AB
Jun 1 13:46:43.708: Cause i = 0x80E262 - Message not compatible
with call state or not implemented
Jun 1 13:46:43.708: Call State i = 0x0A
Jun 1 13:46:56.395: ISDN Se1/0:15: TX -> DISCONNECT pd = 8 callref =
0x00AB
Jun 1 13:46:56.395: Cause i = 0x8090 - Normal call clearing
Jun 1 13:46:56.443: ISDN Se1/0:15: RX <- RELEASE pd = 8 callref =
0x80AB
Jun 1 13:46:56.447: ISDN Se1/0:15: TX -> RELEASE_COMP pd = 8 callref
= 0x00AB
but in this case the call succeeds.
Alejandro Cadarso
Jim Bond wrote:
>
> Hello,
>
> I encountered this problem: 3640 BRI dials into
> AS5200. Link comes up for 3 or 4 seconds, then drops.
> Debug ppp authentication shows it passed
> authentication, debug isdn q931 shows the following,
> what does "invalid message for call state 10" mean?
> Thanks in advance.
>
> Jim
>
> 5d00h: ISDN BR0/0: Outgoing call id = 0x96D2
> 5d00h: ISDN BR0/0: Event: Call to 0015106511084 at 64
> Kb/s
> 5d00h: ISDN BR0/0: TX -> SETUP pd = 8 callref = 0x4B
> 5d00h: Bearer Capability i = 0x8890
> 5d00h: Channel ID i = 0x83
> 5d00h: Called Party Number i = 0x80,
> '0015106511084'
> 5d00h: ISDN BR0/0: Ux_BadMsg(): Invalid Message for
> call state 10, call id 0x96D
> 0, call ref 0x49, event 0x1310
> 5d00h: ISDN BR0/0: RX <- SETUP_ACK pd = 8 callref =
> 0xCB
> 5d00h: Channel ID i = 0x8A
> 5d00h: ISDN BR0/0: received HOST_INFORMATION call_id
> 0x96D2..
> 5d00h: ISDN BR0/0: Ux_BadMsg(): Invalid Message for
> call state 10, call id 0x96D
> 0, call ref 0x49, event 0x1320..
> 5d00h: ISDN Event: dsl 0 call_id 0x96D2 B channel
> assigned by switch 1
> ISDN BR0/0: RX <- ALERTING pd = 8 callref = 0xCB
> 5d00h: ISDN BR0/0: received HOST_ALERTING call_id
> 0x96D2
> 5d00h: ISDN BR0/0: RX <- CONNECT pd = 8 callref =
> 0xCB
> 5d00h: Connected Number i = 0x00C3
> 5d00h: ISDN BR0/0: received HOST_CONNECT call_id
> 0x96D2
> 5d00h: %LINK-3-UPDOWN: Interface BRI0/0:2, changed
> state to up
> 5d00h: %ISDN-6-CONNECT: Interface BRI0/0:2 is now
> connected to 0015106511084
> 5d00h: ISDN BR0/0: Event: Connected to 0015106511084
> on B2 at 64 Kb/s
> 5d00h: ISDN BR0/0: TX -> CONNECT_ACK pd = 8 callref
> = 0x4B
> 5d00h: ISDN BR0/0: Ux_BadMsg(): Invalid Message for
> call state 10, call id 0x96D
> 0, call ref 0x49, event 0x1310.
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:41 GMT-3