[asterisk-bugs] [LibPRI 0013118]: Outgoing ISDN call blocked with cause (100) in Libpri 1.4.5 and 1.4.4, not in 1.4.3, because change in q931.c

[noreply at bugs.digium.com]

The following issue has been SUBMITTED. 
====================================================================== 
http://bugs.digium.com/view.php?id=13118 
====================================================================== 
Reported By:                radpeter
Assigned To:                mattf
====================================================================== 
Project:                    LibPRI
Issue ID:                   13118
Category:                   General
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.21 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             07-20-2008 16:35 CDT
Last Modified:              07-20-2008 16:35 CDT
====================================================================== 
Summary:                    Outgoing ISDN call blocked with cause (100) in
Libpri 1.4.5 and 1.4.4, not in 1.4.3, because change in q931.c
Description: 
Recently I updated from asterisk 1.4.18.3, libpri 1.4.3 to asterisk
1.4.21.1, libpri 1.4.5, zaptel 1.4.11

In my system I have a TE405P card, with the 1st port connected by a E1 to
a telco, and the 2nd port by a E1 to an Alcatel 4400 E pbx, using EuroISDN

The incoming calls are received by asterisk and, when appropriate, passed
through to the Pbx, which usually results in native bridge.

After a while I detected that incoming ISDN modem calls, which are passed
through to the Alcatel Pbx, wheren't answered properly. Inspection revealed
that at the moment Asterisk dialed the Alcatel PBX, the SETUP (5) resulted
in a response RELEASE COMPLETE (90) from the Alcatel, because of a Invalid
Information Contents (100).   

Voice calls had no problems. A significant difference is that while voice
calls use PRI_TRANS_CAP_SPEACH, modems use PRI_TRANS_CAP_DIGITAL 

Inspection of the logfile for the modme calls revealed that while Asterisk
originally received a 4-byte SETUP message from the Telco, it used a 5-byte
SETUP message to the PBX, which refused this.

After some digging I traced this to a change in the
FUNC_SEND(transmit_bearer_capability)

Originally (1.4.3)

	if ((tc & PRI_TRANS_CAP_DIGITAL) && (pri->switchtype ==
PRI_SWITCH_EUROISDN_E1)) {
		/* Apparently EuroISDN switches don't seem to like user layer 2/3 */
		return 4;
	}

In 1.4.4, perhaps related to 11593, r525

	if ((tc & PRI_TRANS_CAP_DIGITAL) && (pri->switchtype ==
PRI_SWITCH_EUROISDN_E1) &&
		(call->transmoderate == TRANS_MODE_PACKET)) {
		/* Apparently EuroISDN switches don't seem to like user layer 2/3 */
		return 4;
	}

In my case call->transmoderate == TRANS_MODE_64_CIRCUIT so I placed an
additional

	if ((tc & PRI_TRANS_CAP_DIGITAL) && (pri->switchtype ==
PRI_SWITCH_EUROISDN_E1) &&
		(call->transmoderate == TRANS_MODE_64_CIRCUIT)) {
		/* Apparently EuroISDN switches don't seem to like user layer 2/3 */
		return 4;
	}

And this solved the problem, as far as I have been able to test this for
now.




  
====================================================================== 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-20-08 16:35  radpeter       Asterisk Version          => 1.4.21          
07-20-08 16:35  radpeter       SVN Branch (only for SVN checkou => N/A          
  
======================================================================