Outbound issue with BRI

Answered Question
Jun 24th, 2008
User Badges:

Hi,


We're having an issue with a new setup. The router is a 2811 and has 4 BRI interfaces. The telco is Swisscom from Switzerland. The four lines are configured as a group on the telco side.


Inbound calls are working, but when trying to call out, the call is dropped.

Doing a debug isdn q931 shows :


000574: Jun 24 11:58:32.521 PCTime: ISDN BR0/2/0 Q931: Applying typeplan for sw-type 0x1 is 0x0 0x0, Calling num 022365xxxx


000575: Jun 24 11:58:32.525 PCTime: ISDN BR0/2/0 Q931: Applying typeplan for sw-type 0x1 is 0x0 0x0, Called num 003247595xxxx


000576: Jun 24 11:58:32.525 PCTime: ISDN BR0/2/0 Q931: TX -> SETUP pd = 8 callref = 0x0D


Bearer Capability i = 0x8090A2


Standard = CCITT


Transfer Capability = Speech


Transfer Mode = Circuit


Transfer Rate = 64 kbit/s


Channel ID i = 0x89


Exclusive, B1


Calling Party Number i = 0x0081, '022365xxxx'


Plan:Unknown, Type:Unknown


Called Party Number i = 0x80, '003247595xxxx'


Plan:Unknown, Type:Unknown


000577: Jun 24 11:58:32.609 PCTime: ISDN BR0/2/0 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x8D


Cause i = 0x82E404 - Invalid information element contents


When I compare this with an inbound call

000582: Jun 24 11:59:28.925 PCTime: ISDN BR0/3/0 Q931: RX <- SETUP pd = 8 callref = 0x01


Sending Complete


Bearer Capability i = 0x8090A3


Standard = CCITT


Transfer Capability = Speech


Transfer Mode = Circuit


Transfer Rate = 64 kbit/s


Channel ID i = 0x89


Exclusive, B1


Calling Party Number i = 0x0183, '003247595xxxx'


Plan:ISDN, Type:Unknown


Called Party Number i = 0x81, '71'


Plan:ISDN, Type:Unknown


High Layer Compat i = 0x9181


000583: Jun 24 11:59:28.945 PCTime: ISDN BR0/3/0 Q931: TX -> CALL_PROC pd = 8 callref = 0x81


Channel ID i = 0x89


Exclusive, B1


000584: Jun 24 11:59:29.169 PCTime: ISDN BR0/3/0 Q931: TX -> ALERTING pd = 8 callref = 0x81


000585: Jun 24 11:59:32.093 PCTime: ISDN BR0/3/0 Q931: TX -> CONNECT pd = 8 callref = 0x81


Channel ID i = 0x89


Exclusive, B1


000586: Jun 24 11:59:32.213 PCTime: ISDN BR0/3/0 Q931: RX <- CONNECT_ACK pd = 8 callref = 0x01


000587: Jun 24 11:59:32.217 PCTime: %ISDN-6-CONNECT: Interface BRI0/3/0:1 is now connected to 003247595xxxx N/A


000588: Jun 24 11:59:38.217 PCTime: %ISDN-6-CONNECT: Interface BRI0/3/0:1 is now connected to 003247595xxxx N/A


000589: Jun 24 11:59:48.929 PCTime: ISDN BR0/3/0 Q931: RX <- DISCONNECT pd = 8 callref = 0x01


Cause i = 0x8090 - Normal call clearing


Progress Ind i = 0x8288 - In-band info or appropriate now available


000590: Jun 24 11:59:48.929 PCTime: %ISDN-6-DISCONNECT: Interface BRI0/3/0:1 disconnected from 003247595xxxx , call lasted 16 seconds


000591: Jun 24 11:59:48.949 PCTime: ISDN BR0/3/0 Q931: TX -> RELEASE pd = 8 callref = 0x81


000592: Jun 24 11:59:49.013 PCTime: ISDN BR0/3/0 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x01


The only difference I can see is the bearer cap, for inbound it is 0x8090A3 which means Voice/Speech call (A-law) and for outbound it is 0x8090A2 which means Voice/Speech call (u-law))


How and where can I specify I want to use G711 Alaw for outbound calls?


Thanks,


Jeroen





Correct Answer by paolo bevilacqua about 8 years 10 months ago

Under voice-port, compand-type a-law.


Hope this helps, please rate post if it does!

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4.8 (3 ratings)
Loading.
Correct Answer
paolo bevilacqua Tue, 06/24/2008 - 03:44
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Under voice-port, compand-type a-law.


Hope this helps, please rate post if it does!

paolo bevilacqua Tue, 06/24/2008 - 04:04
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Thanks for the appreciation and good luck!

singh-ashok Tue, 06/24/2008 - 06:40
User Badges:

Paolo,

Could you please tell me the exact function of this command & how it helped resolve this issue?


Regards,

Ashok.

paolo bevilacqua Tue, 06/24/2008 - 10:43
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

North America uses a PCM companding algorithm called U law tat is the default. Rest of the world uses A law and must be configured accordingly.



Actions

This Discussion