ISDN PRI call get disconnected


Doc ID    SOLN341704
Version:    2.0
Status:    Published
Published date:    10 Nov 2019
Created Date:    21 Jul 2019
Author:   
Amol R Kajgikar
 

Details

Communication Manager with DS1 PRI trunk.

Problem Clarification

ISDN PRIL call get disconnected.

Cause

 

Call details
04366-xxxx 055xxxxxxx 15-Jul-19 4:18 PM 2062

48984  16:15:32.595  60 4001000f ==> SETUP      crv 0_16ba
48984  16:15:32.595  60 4001000f ==> SETUP      crv 0_16ba 
            D-channel port number:                                   4001000f
            Protocol Discriminator: 08                           call control
            Call Reference Value: 02 16 ba                   Origination 16ba
            Q.931 Message Type: 05                                      Setup
       =>   BEARER CAPABILITY 80 90 a3                 speech, 64 kbps, A-law
            | coding standard:                                          CCITT
            | transfer mode:                                     circuit-mode
            | layer 1 indent:                                         layer 1
       =>   CHANNEL IDENT a1 83 8e                          B-ch num 14, pref
       =>   CALLING PARTY NUMBER ................................. 055xxxxxxx
            | type of number:                                        national
            | numbering plan:  ISDN/telphny plan E.164/3 |cv ISDN/telphny pln
            | presentation ind:                          presentation allowed
            | screening:                                     network provided
       =>   CALLED PARTY NUMBER ..................................... 366xxxx
            | type of number:                                      subscriber
            | numbering plan:  ISDN/telphny plan E.164/3 |cv ISDN/telphny pln
       =>   SENDING COMPLETE (a1)                                           

48986  16:15:32.595  62 4001000f <-- CALL_PROC  crv 1_16ba
49071  16:15:32.600  62 4001000f <-- ALERT      crv 1_16ba
49332  16:15:34.795  62 4001000f <-- CONN       crv 1_16ba
49354  16:15:34.840  60 4001000f ==> CONN_ACK   crv 0_16ba
52892  16:17:48.743  62 4001000f <-- STA_ENQ/CL crv 1_16ba  CM sent status enquiry to know the status of the trunk
52892  16:17:48.743  62 4001000f <-- STA_ENQ/CL crv 1_16ba 
            D-channel port number:                                   4001000f
            Protocol Discriminator: 08                           call control
            Call Reference Value: 02 96 ba                   Destination 16ba
            Q.931 Message Type: 75                 Status Enquiry/Close(1TR6)

52913  16:17:48.813  60 4001000f ==> STATUS     crv 0_16ba  (status resp) Service provider reply and call up
52913  16:17:48.813  60 4001000f ==> STATUS     crv 0_16ba  (status resp) 
            D-channel port number:                                   4001000f
            Protocol Discriminator: 08                           call control
            Call Reference Value: 02 16 ba                   Origination 16ba
            Q.931 Message Type: 7d                                     Status
       =>   CAUSE user:                        30. Response to status enquiry
       =>   CALL STATE 0a                        active |cv active-crv in use
60031  16:19:41.347  62 4001000f <-- STA_ENQ/CL crv 1_16ba  CM AGAIN sent status enquiry to know the status of the trunk
60031  16:19:41.347  62 4001000f <-- STA_ENQ/CL crv 1_16ba 
            D-channel port number:                                   4001000f
            Protocol Discriminator: 08                           call control
            Call Reference Value: 02 96 ba                   Destination 16ba
            Q.931 Message Type: 75                 Status Enquiry/Close(1TR6)
60035  16:19:41.405  60 4001000f ==> REL_COM    crv 0_16ba  invalid cref !  Service provider reply with release.
Cause :- Need to check from Service Provider cause of this issue.
 

Good call from the same number 055xxxxxxx and land on same 04366-xxxx but different D-channel.
Good Call
55864  16:19:06.183  60 4004180f ==> SETUP      crv 0_1eac
55864  16:19:06.183  60 4004180f ==> SETUP      crv 0_1eac 
            D-channel port number:                                   4004180f
            Protocol Discriminator: 08                           call control
            Call Reference Value: 02 1e ac                   Origination 1eac
            Q.931 Message Type: 05                                      Setup
       =>   BEARER CAPABILITY 80 90 a3                 speech, 64 kbps, A-law
            | coding standard:                                          CCITT
            | transfer mode:                                     circuit-mode
            | layer 1 indent:                                         layer 1
       =>   CHANNEL IDENT a1 83 85                           B-ch num 5, pref
       =>   CALLING PARTY NUMBER ................................. 055xxxxxxx
            | type of number:                                        national
            | numbering plan:  ISDN/telphny plan E.164/3 |cv ISDN/telphny pln
            | presentation ind:                          presentation allowed
            | screening:                                     network provided
       =>   CALLED PARTY NUMBER ..................................... 366xxxx
            | type of number:                                      subscriber
            | numbering plan:  ISDN/telphny plan E.164/3 |cv ISDN/telphny pln
       =>   SENDING COMPLETE (a1)                                           
55866  16:19:06.183  62 4004180f <-- CALL_PROC  crv 1_1eac
55951  16:19:06.188  62 4004180f <-- ALERT      crv 1_1eac
57035  16:19:10.086  62 4004180f <-- CONN       crv 1_1eac
57057  16:19:10.128  60 4004180f ==> CONN_ACK   crv 0_1eac
67291  16:21:33.006  60 4004180f ==> DISC       crv 0_1eac
67311  16:21:33.007  62 4004180f <-- REL        crv 1_1eac
67327  16:21:33.051  60 4004180f ==> REL_COM    crv 0_1eac
 Bad Call
We can see same behavior and same d-channel used for the call.
51492  16:17:06.175  60 4001000f ==> SETUP      crv 0_0f10
51492  16:17:06.175  60 4001000f ==> SETUP      crv 0_0f10 
            D-channel port number:                                   4001000f
            Protocol Discriminator: 08                           call control
            Call Reference Value: 02 0f 10                   Origination 0f10
            Q.931 Message Type: 05                                      Setup
       =>   BEARER CAPABILITY 90 90 a3          3.1 kHz audio, 64 kbps, A-law
            | coding standard:                                          CCITT
            | transfer mode:                                     circuit-mode
            | layer 1 indent:                                         layer 1
       =>   CHANNEL IDENT a1 83 85                           B-ch num 5, pref
       =>   PROGRESS IND 82 81      local pub netwk, call NOT end-to-end ISDN
       =>   CALLING PARTY NUMBER ................................. 050xxxxxxx
            | type of number:                                        national
            | numbering plan:  ISDN/telphny plan E.164/3 |cv ISDN/telphny pln
            | presentation ind:                          presentation allowed
            | screening:                                     network provided
       =>   CALLED PARTY NUMBER ..................................... 366xxxx
            | type of number:                                      subscriber
            | numbering plan:  ISDN/telphny plan E.164/3 |cv ISDN/telphny pln
       =>   SENDING COMPLETE (a1)
51494  16:17:06.175  62 4001000f <-- CALL_PROC  crv 1_0f10
51575  16:17:06.180  62 4001000f <-- ALERT      crv 1_0f10
51601  16:17:06.181  62 4001000f <-- CONN       crv 1_0f10
51605  16:17:06.225  60 4001000f ==> CONN_ACK   crv 0_0f10
52886  16:17:48.728  62 4001000f <-- STA_ENQ/CL crv 1_0f10 CM sent status enquiry to know the status of the trunk
52886  16:17:48.728  62 4001000f <-- STA_ENQ/CL crv 1_0f10 
            D-channel port number:                                   4001000f
            Protocol Discriminator: 08                           call control
            Call Reference Value: 02 8f 10                   Destination 0f10
            Q.931 Message Type: 75                 Status Enquiry/Close(1TR6)
52902  16:17:48.774  60 4001000f ==> STATUS     crv 0_0f10  (status resp)
52902  16:17:48.774  60 4001000f ==> STATUS     crv 0_0f10  (status resp)  Service provider reply and call up
            D-channel port number:                                   4001000f
            Protocol Discriminator: 08                           call control
            Call Reference Value: 02 0f 10                   Origination 0f10
            Q.931 Message Type: 7d                                     Status
       =>   CAUSE user:                        30. Response to status enquiry
       =>   CALL STATE 0a                        active |cv active-crv in use
59832  16:19:41.118  62 4001000f <-- STA_ENQ/CL crv 1_0f10
59832  16:19:41.118  62 4001000f <-- STA_ENQ/CL crv 1_0f10  CM AGAIN sent status enquiry to know the status of the trunk
            D-channel port number:                                   4001000f
            Protocol Discriminator: 08                           call control
            Call Reference Value: 02 8f 10                   Destination 0f10
            Q.931 Message Type: 75                 Status Enquiry/Close(1TR6)
59938  16:19:41.211  60 4001000f ==> REL_COM    crv 0_0f10  invalid cref ! Service provider reply with release.
 

Solution

This issue is from service provider as they have back end SIP trunk where they mapped incorrect d channel.


Avaya -- Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy