[Freeswitch-users] Registration problem after attempting to install mod_opal and updating to latest git pull

[Phil Quesinberry]

After a recent unsuccessful attempt to install mod_opal and updating to a
recent git, I now get some odd reports of gateway registration failures,
although everything appears to be working ok call-wise for the moment.
Doing a 'make uninstall' from /root/opal and updating to the latest git
tonight yielded no improvement.

Here are some excerpts of failures reported in fs_cli:

2012-02-09 00:12:59.992099 [WARNING] sofia.c:4717 Unregister QS8002
2012-02-09 00:12:59.992099 [WARNING] sofia.c:4730 Ping failed QS8002 with
code 900 - count -1/-1/1, state UP
2012-02-09 00:12:59.992099 [WARNING] sofia.c:4717 Unregister HL7612
2012-02-09 00:12:59.992099 [WARNING] sofia.c:4730 Ping failed HL7612 with
code 900 - count -1/-1/1, state UP
2012-02-09 00:13:00.011988 [WARNING] sofia.c:4717 Unregister HL7611
2012-02-09 00:13:00.011988 [WARNING] sofia.c:4730 Ping failed HL7611 with
code 900 - count -1/-1/1, state UP
2012-02-09 00:13:00.011988 [WARNING] sofia.c:4717 Unregister HL7519
2012-02-09 00:13:00.011988 [WARNING] sofia.c:4730 Ping failed HL7519 with
code 900 - count -1/-1/1, state UP
2012-02-09 00:13:00.011988 [WARNING] sofia.c:4717 Unregister
CallCentric_T.38
2012-02-09 00:13:00.011988 [WARNING] sofia.c:4730 Ping failed
CallCentric_T.38 with code 900 - count -1/-1/1, state UP
2012-02-09 00:13:01.992050 [WARNING] sofia_reg.c:474 QS8002 Failed
Registration [0], setting retry to 60 seconds.
2012-02-09 00:13:01.992050 [WARNING] sofia_reg.c:474 HL7612 Failed
Registration [0], setting retry to 90 seconds.
2012-02-09 00:13:01.992050 [WARNING] sofia_reg.c:474 HL7611 Failed
Registration [0], setting retry to 90 seconds.
2012-02-09 00:13:01.992050 [WARNING] sofia_reg.c:474 HL7519 Failed
Registration [0], setting retry to 60 seconds.
2012-02-09 00:13:01.992050 [WARNING] sofia_reg.c:474 CallCentric_T.38 Failed
Registration [0], setting retry to 60 seconds.

To give a sense of the timing, the three groups of warnings below are
contiguous, from a single fs_cli session:

2012-02-09 00:21:18.984384 [WARNING] sofia.c:4717 Unregister HL7611
2012-02-09 00:21:18.984384 [WARNING] sofia.c:4730 Ping failed HL7611 with
code 900 - count -1/-1/1, state UP
2012-02-09 00:21:20.988379 [WARNING] sofia_reg.c:474 HL7611 Failed
Registration [0], setting retry to 90 seconds.
2012-02-09 00:21:22.988382 [WARNING] sofia.c:4717 Unregister HL7519
2012-02-09 00:21:22.988382 [WARNING] sofia.c:4730 Ping failed HL7519 with
code 900 - count -1/-1/1, state UP
2012-02-09 00:21:24.988318 [WARNING] sofia_reg.c:474 HL7519 Failed
Registration [0], setting retry to 60 seconds.

2012-02-09 00:22:00.447778 [WARNING] sofia_reg.c:1422 SIP auth challenge
(REGISTER) on sofia profile 'internal' for [226 at qsystemseng.no-ip.org] from
ip 74.93.222.182
2012-02-09 00:22:04.147688 [WARNING] sofia.c:4717 Unregister HL7612
2012-02-09 00:22:04.147688 [WARNING] sofia.c:4730 Ping failed HL7612 with
code 900 - count -1/-1/1, state UP
2012-02-09 00:22:04.167699 [WARNING] sofia.c:4717 Unregister HL7611
2012-02-09 00:22:04.167699 [WARNING] sofia.c:4730 Ping failed HL7611 with
code 900 - count -1/-1/1, state UP
2012-02-09 00:22:04.167699 [WARNING] sofia.c:4717 Unregister
CallCentric_T.38
2012-02-09 00:22:04.167699 [WARNING] sofia.c:4730 Ping failed
CallCentric_T.38 with code 900 - count -1/-1/1, state UP

2012-02-09 00:22:05.167744 [WARNING] sofia_reg.c:474 HL7611 Failed
Registration [0], setting retry to 90 seconds.
2012-02-09 00:22:05.167744 [WARNING] sofia_reg.c:474 CallCentric_T.38 Failed
Registration [0], setting retry to 60 seconds.
2012-02-09 00:22:05.167744 [WARNING] sofia.c:4717 Unregister QS8002
2012-02-09 00:22:05.167744 [WARNING] sofia.c:4730 Ping failed QS8002 with
code 900 - count -1/-1/1, state UP

2012-02-09 00:22:07.171680 [WARNING] sofia_reg.c:474 QS8002 Failed
Registration [0], setting retry to 60 seconds.
2012-02-09 00:22:07.171680 [WARNING] sofia.c:4717 Unregister HL7519
2012-02-09 00:22:07.171680 [WARNING] sofia.c:4730 Ping failed HL7519 with
code 900 - count -1/-1/1, state UP

One of the gateways is SIPBroker, and calls through that gate starting
failing after the update.  I realized that the gateway was configured to
ping SIPBroker unnecessarily and restarting the gateway would restore
service until the ping.  I disabled the ping for that gateway and calls kept
working after that.

Any ideas as to what might be going on?  There was no such problem before
the FS update/attempt to use mod_opal.  I can provide additional/more
detailed info if needed.

Thanks!

Phil Quesinberry
Q Systems Engineering, Inc.
Electronic Controls and Embedded Systems Development
(410) 969-8002
http://www.qsystemsengineering.com