Actions
Bug #3241
closedFailed MS <-> MS call assignment
Start date:
05/06/2018
Due date:
% Done:
0%
Resolution:
Spec Reference:
Description
There are only two subscribers:
#1 IMSI: 001010000011996, MSISDN: 11996 #2 IMSI: 262423403001393, MSISDN: 01393
Please have a look at 'call.pcapng.gz' attached to this issue:
#118: Subscriber 01393 initiates a call to 11996, by sending CM Service Request on established channel; #227: The network accepts this request, by sending CM Service Accept; #230: Subscriber 01393 sends SETUP to 11996 #427: The network responds with Call Proceeding message; #447: The network initiates paging of subscriber 11996, by sending Paging Request Type 1; #475: Subscriber 11996 responds by sending Paging Response; #600: The network informs subscriber 11996 about an incoming call, by sending SETUP message; #611: Subscriber 11996 confirms this call, by sending Call Confirmed message; ... #667: OsmoMGW fails to send a dummy RTP packet... #710: OsmoMGW fails to send a dummy RTP packet... ... #758: The MSC indicates assignment failure ... Both SDCCH channels remain open for some long time ... #1488: Subscriber 01393 sends Disconnect message, due to "(102) Recovery on timer expiry"; #1584: Subscriber 11996 sends Disconnect message, due to "(102) Recovery on timer expiry"; ... Both SDCCH channels remain open for some long time ...
I am running a single OsmoMGW instance, both BSC and MSC
are configured to use it, configuration files attached.
Files
Actions