You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When routing q Q.931 call with bearer-cap=udi to ISUP, the bearer capability information is lost and the ISUP IAM is sent with "Information Transfer Capability: Speech" instead.
Oddly enough, yate does seam to notice a difference, as an actual speec call SETUP -> IAM looks like this:
Note that the UserServiceInformation is empty in the latter call, while it is "alaw" in the voice call. However, it seems that the empty UserServiceInformation is then encoded as voice, as the pcap file clearly indicates voice.
The text was updated successfully, but these errors were encountered:
laf0rge
added a commit
to osmocom/yate
that referenced
this issue
Dec 3, 2023
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 yatevoip#12
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 yatevoip#12
When routing q Q.931 call with bearer-cap=udi to ISUP, the bearer capability information is lost and the ISUP IAM is sent with "Information Transfer Capability: Speech" instead.
Oddly enough, yate does seam to notice a difference, as an actual speec call SETUP -> IAM looks like this:
While the SETUP + IAM for te data call (actually an ISDN video phone) looks like this:
Note that the UserServiceInformation is empty in the latter call, while it is "alaw" in the voice call. However, it seems that the empty UserServiceInformation is then encoded as voice, as the pcap file clearly indicates voice.
The text was updated successfully, but these errors were encountered: