[PATCH 3/3] mncc: Send "Dest OOO" cause in case of a link radio failure.
Previously we were sending a generic "Resource unavailable" cause code making it impossible to distinguish real error cases from a regular radio link failure. This was the reason for many "unknown" call errors we've seen at Rhizomatica installations. Now they are properly classified as non-erroneous call failures. The code is also a part of the achemeris/mncc_cause_fixes_master branch. -- Regards, Alexander Chemeris. CEO, Fairwaves, Inc. https://fairwaves.co
Btw, I'm not sure 27 DESTINATION_OUT_OF_ORDER is the best cause in this case. Two other options I see suitable are 102 RECOVERY_ON_TIMER_EXPIRE and 604 MEDIA_TIMEOUT. Does anyone know is there an official mapping between Q.850 codes and various GSM cause codes? Another useful change here would be to propagate information about which timer expired. That would help to gather information about issues with the network. On Sat, Sep 12, 2015 at 8:48 PM, Alexander Chemeris <alexander.chemeris@gmail.com> wrote:
Previously we were sending a generic "Resource unavailable" cause code making it impossible to distinguish real error cases from a regular radio link failure. This was the reason for many "unknown" call errors we've seen at Rhizomatica installations. Now they are properly classified as non-erroneous call failures.
The code is also a part of the achemeris/mncc_cause_fixes_master branch.
-- Regards, Alexander Chemeris. CEO, Fairwaves, Inc. https://fairwaves.co
-- Regards, Alexander Chemeris. CEO, Fairwaves, Inc. https://fairwaves.co
bump On Sun, Sep 13, 2015 at 6:24 PM, Alexander Chemeris < alexander.chemeris@gmail.com> wrote:
Btw, I'm not sure 27 DESTINATION_OUT_OF_ORDER is the best cause in this case. Two other options I see suitable are 102 RECOVERY_ON_TIMER_EXPIRE and 604 MEDIA_TIMEOUT. Does anyone know is there an official mapping between Q.850 codes and various GSM cause codes?
Another useful change here would be to propagate information about which timer expired. That would help to gather information about issues with the network.
On Sat, Sep 12, 2015 at 8:48 PM, Alexander Chemeris <alexander.chemeris@gmail.com> wrote:
Previously we were sending a generic "Resource unavailable" cause code making it impossible to distinguish real error cases from a regular radio link failure. This was the reason for many "unknown" call errors we've seen at Rhizomatica installations. Now they are properly classified as non-erroneous call failures.
The code is also a part of the achemeris/mncc_cause_fixes_master branch.
-- Regards, Alexander Chemeris. CEO, Fairwaves, Inc. https://fairwaves.co
-- Regards, Alexander Chemeris. CEO, Fairwaves, Inc. https://fairwaves.co
-- Regards, Alexander Chemeris. CEO, Fairwaves, Inc. https://fairwaves.co
participants (1)
-
Alexander Chemeris