The user may suggest a given channel in the SETUP, but it's not legal
for the network to return a non-mandatory ChannelID.
See Q.931 Section 5.1.2 (B-channel selection - Originating):
The selected B-channel is indicated in the Channel identification information
element coded as "channel is indicated, no acceptable alternative" in the first
message returned by the network in response to the SETUP message (i.e. a SETUP
ACKNOWLEDGE or CALL PROCEEDING message)
In an earlier commit I had only fixed SETUP ACK, but missed that this is
a more general problem that needs addressing in whatever is the first
message containing a channelID yate sends in response to the SETUP.
The user may suggest a given channel in the SETUP, but it's not legal
for the network to return a non-mandatory ChannelID.
See Q.931 Section 5.1.2 (B-channel selection - Originating):
The selected B-channel is indicated in the Channel identification information
element coded as "channel is indicated, no acceptable alternative" in the first
message returned by the network in response to the SETUP message (i.e. a SETUP
ACKNOWLEDGE or CALL PROCEEDING message)
If yate is operating in the 'network' role of a PRI interface,
it must send a valid ChannelID InformationElement in the SETUP ACK.
However, current yate code is encoding the channel selection field
of said information element wrong, as it unconditionally looks up
the s_dict_channelIDSelect_BRI (instead of _PRI).
This fixes a regression introduced in 2009 in the following commit:
commit 05b717e0b9
Author: paulc <paulc@acf43c95-373e-0410-b603-e72c3f656dc1>
Date: Mon Mar 2 18:51:30 2009 +0000
ISDN BRI support, most Andrei's (andrei@null.ro) work.
Fixes and new features throughout the signalling engine.
it-svn-id: http://yate.null.ro/svn/yate/trunk@2505 acf43c95-373e-0410-b603-e72c3f656dc1
Updated copyright notices for 2014.
Fixed end of lines in many files.
git-svn-id: http://yate.null.ro/svn/yate/trunk@5755 acf43c95-373e-0410-b603-e72c3f656dc1
Added the possibility of setting the Channel Exclusive flag from configuration or routing.
git-svn-id: http://yate.null.ro/svn/yate/trunk@5294 acf43c95-373e-0410-b603-e72c3f656dc1
This should reduce contention during high load and the chances to deadlock.
git-svn-id: http://yate.null.ro/svn/yate/trunk@4950 acf43c95-373e-0410-b603-e72c3f656dc1
Send extra Called Party Number digits in a SAM message.
The overlapped dialing script accepts an initial number.
Merged branch paulc/pstn -c 3485
git-svn-id: http://yate.null.ro/svn/yate/trunk@3493 acf43c95-373e-0410-b603-e72c3f656dc1
Default reset interval for both ISUP and ISDN is 300s with 60s minimum.
git-svn-id: http://yate.null.ro/svn/yate/trunk@3404 acf43c95-373e-0410-b603-e72c3f656dc1
The creation of subcomponents is offloaded to each component to allow for proper building of the component stack.
git-svn-id: http://yate.null.ro/svn/yate/trunk@2650 acf43c95-373e-0410-b603-e72c3f656dc1
Detect early a congestion or network failure and attempt next link.
git-svn-id: http://yate.null.ro/svn/yate/trunk@2368 acf43c95-373e-0410-b603-e72c3f656dc1
File type can be modified by extension (.hex/.txt/.raw)
Documented dump files in ysigchan.conf
git-svn-id: http://yate.null.ro/svn/yate/trunk@2211 acf43c95-373e-0410-b603-e72c3f656dc1
Protocol data dumping capability for several L2 and L3 components.
Data dumpers can be set at runtime from rmanager command with completion.
git-svn-id: http://yate.null.ro/svn/yate/trunk@2210 acf43c95-373e-0410-b603-e72c3f656dc1
Harald Welte
paulc