[asterisk-users] Asterisk 13.11 realtime problem registering phones

[Carlos Chavez]

On 2016-09-04 10:11, Max Grobecker wrote:
> Hi,
> 
> 
> Am 02.09.2016 um 22:48 schrieb Carlos Chavez:
>>     I upgraded my office installation from 13.10 to 13.11 yesterday 
>> and now I am having problems registering phones.  Here is what I get 
>> on the CLI:
>> 
>> [Sep  2 15:38:46] WARNING[2098]: res_config_mysql.c:1162 
>> require_mysql: Realtime table general at ps_contacts: column 
>> 'qualify_timeout' cannot be type 'int(10)' (need char)
>> [Sep  2 15:38:46] WARNING[2098]: res_config_mysql.c:1162 
>> require_mysql: Realtime table general at ps_contacts: column 
>> 'expiration_time' cannot be type 'bigint(20)' (need char)
>> [Sep  2 15:38:46] WARNING[2098]: res_config_mysql.c:1246 
>> require_mysql: Possibly unsupported column type 'enum('yes','no')' on 
>> column 'authenticate_qualify'
>> [Sep  2 15:38:46] WARNING[2098]: res_config_mysql.c:1162 
>> require_mysql: Realtime table general at ps_contacts: column 'via_port' 
>> cannot be type 'int(11)' (need char)
>> [Sep  2 15:38:46] ERROR[2098]: res_pjsip_registrar.c:411 
>> register_aor_core: Unable to bind contact 
>> 'sip:2001 at 192.168.2.203:57776;transport=UDP;rinstance=48d5c7d09b9f2525' 
>> to AOR '2001'
>>   == Contact 
>> 2001/sip:2001 at 192.168.2.203:57776;transport=UDP;rinstance=48d5c7d09b9f2525 
>> has been deleted
>> 
>>     The mysql warnings have always been there since version 13.0 and 
>> the "Unable to bind contact..." error has also been present since I 
>> started using PJSIP realtime with Asterisk 13 (13.5 at least).
> 
> I hope you find this concerning...
> 
> Have you upgraded your MySQL realtime tables to the new schema as
> introduced with Asterisk 13?
> ->
> https://wiki.asterisk.org/wiki/display/AST/Upgrading+to+Asterisk+13#UpgradingtoAsterisk13-RealTime
> 
> It's likely a database error (i.e. a required, but missing table
> field) causes this issue.
> But even if not, you are getting rid of the warning messages ;-)
> 

Hi Max, I do find it concerning ;) (please do not take it the wrong way, 
I just found the usage of the word here funny).

I am using alembic to configure all my database tables so in theory that 
is the "official" way to do it.  Even so mysql keeps sending those 
warnings.  I guess the res_mysql_config code does not follow the same 
standards as odbc.  Like I mentioned, the warnings have been there since 
Asterisk 13.0 but everything was working at least.  I always run the 
alembic upgrade when installing a new version of Asterisk 13 to make 
sure realtime tables are up to date.

I not only had to go back to Asterisk 13.10 but had to revert to a 
previous backup of the database so I guess what really broke things was 
the database update.

-- 
Telecomunicaciones Abiertas de México S.A. de C.V.
Carlos Chávez
dCAP #1349
+52 (55)9116-91161