ISUP: support transfer capability interworking with Q.931 #13
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A Q.931 call has the 'transfer-cap' attribute set to 'udi' for data calls. The ISUP module must pick this up and encode it in the UseServiceInformation IE to preserve this vital information. Inversely, a call arriving via ISUP must put its transfer-capability into the 'transfer-cap' attribute, so that when it's routed to Q.931 it is preserved.
Without this transfer-capability transparency, no UDI/RDI data calls or ISDN video calls can transition on the Q931/ISUP boundary
See also #12