Actions
Bug #6070
closedvoice call fails, error log: "DMNCC NOTICE (call 80000003) We only support voice calls (mncc_builtin.c:90)"
Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
06/21/2023
Due date:
% Done:
0%
Resolution:
Spec Reference:
Description
Using current master of osmo-msc and trying to establish a 3G voice call, I get a failing voice call and this error in the MSC log:
DMNCC NOTICE (call 80000003) We only support voice calls (mncc_builtin.c:90)
It seems the MNCC_SETUP's 'transport' parameter reflects something other than 0 = speech. The error message fails to output what it sees instead.
So far I'm still busy ruling out whether this problem is somehow caused by my particular testing setup or an osmo-msc regression.
Details will follow.
Updated by neels 10 months ago
- Status changed from New to Rejected
This is not an osmo-msc regression,
it is caused from an unusual "information transport capability" that the 3G modems send in the CC Setup message.
We expect '000 speech' and the modem sent '010 3.1 kHz audio, ex PLMN".
osmo-msc does not support that and never did.
Actions