On Mon, Sep 12, 2016 at 2:31 PM, George Joseph <gjoseph at digium.com> wrote:> > > On Mon, Sep 12, 2016 at 2:14 PM, Carlos Chavez <cursor at telecomabmex.com> > wrote: > >> Has anyone successfully used Mysql realtime PJSIP with Asterisk >> 13.11? I have tried 13.11, 13.11.1 and 13.11.2 but I always get the >> following error now: >> >> Sep 12 14:42:35] WARNING[24498]: res_config_mysql.c:1162 require_mysql: >> Realtime table general at ps_contacts: column 'qualify_timeout' cannot be >> type 'int(10)' (need char) >> [Sep 12 14:42:35] WARNING[24498]: res_config_mysql.c:1162 require_mysql: >> Realtime table general at ps_contacts: column 'expiration_time' cannot be >> type 'bigint(20)' (need char) >> [Sep 12 14:42:35] WARNING[24498]: res_config_mysql.c:1246 require_mysql: >> Possibly unsupported column type 'enum('yes','no')' on column >> 'authenticate_qualify' >> [Sep 12 14:42:35] WARNING[24498]: res_config_mysql.c:1162 require_mysql: >> Realtime table general at ps_contacts: column 'via_port' cannot be type >> 'int(11)' (need char) >> [Sep 12 14:42:35] ERROR[24498]: res_pjsip_registrar.c:411 >> register_aor_core: Unable to bind contact 'sip:2001 at 192.168.2.165:5060;transport=udp' >> to AOR '2001' >> == Contact 2001/sip:2001 at 192.168.2.165:5060;transport=udp has been >> deleted >> >> Up until 13.10 everything was working despite the warnings about >> field types. Now my phones will not register. I can make calls but not >> receive. All database modifications are done through alembic so they are >> supposed to be up to date. The only way I can find to solve this issue >> right now is to restore a 13.10 backup for both the database and Asterisk. >> > > res_config_mysql has been in "extended" support for some time now and it's > possible it just will no longer work. We only test alembic changes with > postgres or odbc now. Your best bet is to convert to res_odbc. >Oh yeah, if you really do need res_config_mysql, go ahead and open an issue at issues.asterisk.org and we'll take a look. Since we don't test with it though, we might not notice if it gets broken again in the future unless someone reports it.> > >> >> -- >> Telecomunicaciones Abiertas de M?xico S.A. de C.V. >> Carlos Ch?vez >> +52 (55)9116-91161 >> >> >> -- >> _____________________________________________________________________ >> -- Bandwidth and Colocation Provided by http://www.api-digital.com -- >> >> Join the Asterisk Community at the 13th AstriCon, September 27-29, 2016 >> http://www.asterisk.org/community/astricon-user-conference >> >> New to Asterisk? Start here: >> https://wiki.asterisk.org/wiki/display/AST/Getting+Started >> >> asterisk-users mailing list >> To UNSUBSCRIBE or update options visit: >> http://lists.digium.com/mailman/listinfo/asterisk-users > > > > > -- > George Joseph > Digium, Inc. | Software Developer > 445 Jan Davis Drive NW - Huntsville, AL 35806 - US > Check us out at: www.digium.com & www.asterisk.org > >-- George Joseph Digium, Inc. | Software Developer 445 Jan Davis Drive NW - Huntsville, AL 35806 - US Check us out at: www.digium.com & www.asterisk.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20160912/a7f6a007/attachment.html>
On 9/12/16 3:39 PM, George Joseph wrote:> > > On Mon, Sep 12, 2016 at 2:31 PM, George Joseph <gjoseph at digium.com > <mailto:gjoseph at digium.com>> wrote: > > > > On Mon, Sep 12, 2016 at 2:14 PM, Carlos Chavez > <cursor at telecomabmex.com <mailto:cursor at telecomabmex.com>> wrote: > > Has anyone successfully used Mysql realtime PJSIP with > Asterisk 13.11? I have tried 13.11, 13.11.1 and 13.11.2 but I > always get the following error now: > > Sep 12 14:42:35] WARNING[24498]: res_config_mysql.c:1162 > require_mysql: Realtime table general at ps_contacts: column > 'qualify_timeout' cannot be type 'int(10)' (need char) > [Sep 12 14:42:35] WARNING[24498]: res_config_mysql.c:1162 > require_mysql: Realtime table general at ps_contacts: column > 'expiration_time' cannot be type 'bigint(20)' (need char) > [Sep 12 14:42:35] WARNING[24498]: res_config_mysql.c:1246 > require_mysql: Possibly unsupported column type > 'enum('yes','no')' on column 'authenticate_qualify' > [Sep 12 14:42:35] WARNING[24498]: res_config_mysql.c:1162 > require_mysql: Realtime table general at ps_contacts: column > 'via_port' cannot be type 'int(11)' (need char) > [Sep 12 14:42:35] ERROR[24498]: res_pjsip_registrar.c:411 > register_aor_core: Unable to bind contact > 'sip:2001 at 192.168.2.165:5060 > <http://sip:2001 at 192.168.2.165:5060>;transport=udp' to AOR '2001' > == Contact 2001/sip:2001 at 192.168.2.165 > <mailto:sip%3A2001 at 192.168.2.165>:5060;transport=udp has been > deleted > > Up until 13.10 everything was working despite the warnings > about field types. Now my phones will not register. I can > make calls but not receive. All database modifications are > done through alembic so they are supposed to be up to date. > The only way I can find to solve this issue right now is to > restore a 13.10 backup for both the database and Asterisk. > > > res_config_mysql has been in "extended" support for some time now > and it's possible it just will no longer work. We only test > alembic changes with postgres or odbc now. Your best bet is to > convert to res_odbc. > > > Oh yeah, if you really do need res_config_mysql, go ahead and open an > issue at issues.asterisk.org <http://issues.asterisk.org> and we'll > take a look. Since we don't test with it though, we might not notice > if it gets broken again in the future unless someone reports it. > >I have solved the problem for the moment by changing the ps_contacts table with the "recommendations" res_config_mysql is giving. I just modified all the fields to varchar and now my phones are registering. Obviously this is not a solution as the database needs to be modified by alembic on future versions and it will keep breaking. I tried to migrate to res_config_odbc about 6 months ago but my Asterisk kept crashing. I was told that the crashes were due to the version of ODBC distributed by CentOS 7 and that I would have to compile my own to be able to solve the issue. Has this been solved? Is the RPM ODBC package included with CentOS 7 still bugged? I try to avoid using packages not included in the distribution as they make upgrades a pain later on. -- Telecomunicaciones Abiertas de M?xico S.A. de C.V. Carlos Ch?vez +52 (55)9116-91161 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20160912/a62819ae/attachment.html>
Hello Carlos, I'm testing CentOS 7 ODBC packages with PJSIP Realtime without problems. Maybe you use a different configuration? Regards El 12/09/2016 a las 16:01, Carlos Chavez escribi?:> > On 9/12/16 3:39 PM, George Joseph wrote: > >> >> >> On Mon, Sep 12, 2016 at 2:31 PM, George Joseph <gjoseph at digium.com >> <mailto:gjoseph at digium.com>> wrote: >> >> >> >> On Mon, Sep 12, 2016 at 2:14 PM, Carlos Chavez >> <cursor at telecomabmex.com <mailto:cursor at telecomabmex.com>> wrote: >> >> Has anyone successfully used Mysql realtime PJSIP with >> Asterisk 13.11? I have tried 13.11, 13.11.1 and 13.11.2 but >> I always get the following error now: >> >> Sep 12 14:42:35] WARNING[24498]: res_config_mysql.c:1162 >> require_mysql: Realtime table general at ps_contacts: column >> 'qualify_timeout' cannot be type 'int(10)' (need char) >> [Sep 12 14:42:35] WARNING[24498]: res_config_mysql.c:1162 >> require_mysql: Realtime table general at ps_contacts: column >> 'expiration_time' cannot be type 'bigint(20)' (need char) >> [Sep 12 14:42:35] WARNING[24498]: res_config_mysql.c:1246 >> require_mysql: Possibly unsupported column type >> 'enum('yes','no')' on column 'authenticate_qualify' >> [Sep 12 14:42:35] WARNING[24498]: res_config_mysql.c:1162 >> require_mysql: Realtime table general at ps_contacts: column >> 'via_port' cannot be type 'int(11)' (need char) >> [Sep 12 14:42:35] ERROR[24498]: res_pjsip_registrar.c:411 >> register_aor_core: Unable to bind contact >> 'sip:2001 at 192.168.2.165:5060 >> <http://sip:2001 at 192.168.2.165:5060>;transport=udp' to AOR '2001' >> == Contact 2001/sip:2001 at 192.168.2.165 >> <mailto:sip%3A2001 at 192.168.2.165>:5060;transport=udp has been >> deleted >> >> Up until 13.10 everything was working despite the >> warnings about field types. Now my phones will not >> register. I can make calls but not receive. All database >> modifications are done through alembic so they are supposed >> to be up to date. The only way I can find to solve this >> issue right now is to restore a 13.10 backup for both the >> database and Asterisk. >> >> >> res_config_mysql has been in "extended" support for some time now >> and it's possible it just will no longer work. We only test >> alembic changes with postgres or odbc now. Your best bet is to >> convert to res_odbc. >> >> >> Oh yeah, if you really do need res_config_mysql, go ahead and open an >> issue at issues.asterisk.org <http://issues.asterisk.org> and we'll >> take a look. Since we don't test with it though, we might not notice >> if it gets broken again in the future unless someone reports it. >> >> > I have solved the problem for the moment by changing the > ps_contacts table with the "recommendations" res_config_mysql is > giving. I just modified all the fields to varchar and now my phones > are registering. Obviously this is not a solution as the database > needs to be modified by alembic on future versions and it will keep > breaking. > > I tried to migrate to res_config_odbc about 6 months ago but my > Asterisk kept crashing. I was told that the crashes were due to the > version of ODBC distributed by CentOS 7 and that I would have to > compile my own to be able to solve the issue. Has this been solved? > Is the RPM ODBC package included with CentOS 7 still bugged? I try to > avoid using packages not included in the distribution as they make > upgrades a pain later on. > -- > Telecomunicaciones Abiertas de M?xico S.A. de C.V. > Carlos Ch?vez > +52 (55)9116-91161 > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20160912/1487dc7d/attachment.html>
On Mon, Sep 12, 2016 at 3:01 PM, Carlos Chavez <cursor at telecomabmex.com> wrote:> On 9/12/16 3:39 PM, George Joseph wrote: > > > > On Mon, Sep 12, 2016 at 2:31 PM, George Joseph <gjoseph at digium.com> wrote: > >> >> >> On Mon, Sep 12, 2016 at 2:14 PM, Carlos Chavez <cursor at telecomabmex.com> >> wrote: >> >>> Has anyone successfully used Mysql realtime PJSIP with Asterisk >>> 13.11? I have tried 13.11, 13.11.1 and 13.11.2 but I always get the >>> following error now: >>> >>> Sep 12 14:42:35] WARNING[24498]: res_config_mysql.c:1162 require_mysql: >>> Realtime table general at ps_contacts: column 'qualify_timeout' cannot be >>> type 'int(10)' (need char) >>> [Sep 12 14:42:35] WARNING[24498]: res_config_mysql.c:1162 require_mysql: >>> Realtime table general at ps_contacts: column 'expiration_time' cannot be >>> type 'bigint(20)' (need char) >>> [Sep 12 14:42:35] WARNING[24498]: res_config_mysql.c:1246 require_mysql: >>> Possibly unsupported column type 'enum('yes','no')' on column >>> 'authenticate_qualify' >>> [Sep 12 14:42:35] WARNING[24498]: res_config_mysql.c:1162 require_mysql: >>> Realtime table general at ps_contacts: column 'via_port' cannot be type >>> 'int(11)' (need char) >>> [Sep 12 14:42:35] ERROR[24498]: res_pjsip_registrar.c:411 >>> register_aor_core: Unable to bind contact 'sip:2001 at 192.168.2.165:5060;transport=udp' >>> to AOR '2001' >>> == Contact 2001/sip:2001 at 192.168.2.165:5060;transport=udp has been >>> deleted >>> >>> Up until 13.10 everything was working despite the warnings about >>> field types. Now my phones will not register. I can make calls but not >>> receive. All database modifications are done through alembic so they are >>> supposed to be up to date. The only way I can find to solve this issue >>> right now is to restore a 13.10 backup for both the database and Asterisk. >>> >> >> res_config_mysql has been in "extended" support for some time now and >> it's possible it just will no longer work. We only test alembic changes >> with postgres or odbc now. Your best bet is to convert to res_odbc. >> > > Oh yeah, if you really do need res_config_mysql, go ahead and open an > issue at issues.asterisk.org and we'll take a look. Since we don't test > with it though, we might not notice if it gets broken again in the future > unless someone reports it. > > > > I have solved the problem for the moment by changing the ps_contacts > table with the "recommendations" res_config_mysql is giving. I just > modified all the fields to varchar and now my phones are registering. > Obviously this is not a solution as the database needs to be modified by > alembic on future versions and it will keep breaking. > > I tried to migrate to res_config_odbc about 6 months ago but my > Asterisk kept crashing. I was told that the crashes were due to the > version of ODBC distributed by CentOS 7 and that I would have to compile my > own to be able to solve the issue. Has this been solved? Is the RPM ODBC > package included with CentOS 7 still bugged? I try to avoid using packages > not included in the distribution as they make upgrades a pain later on. >Although CentOS7 is still on 2.3.1 for unixodbc, there were changes made in 13.10.0 that should prevent the crashes. http://lists.digium.com/pipermail/asterisk-dev/2016-June/075582.html> > -- > Telecomunicaciones Abiertas de M?xico S.A. de C.V. > Carlos Ch?vez > +52 (55)9116-91161 > > > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > Join the Asterisk Community at the 13th AstriCon, September 27-29, 2016 > http://www.asterisk.org/community/astricon-user-conference > > New to Asterisk? Start here: > https://wiki.asterisk.org/wiki/display/AST/Getting+Started > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >-- George Joseph Digium, Inc. | Software Developer 445 Jan Davis Drive NW - Huntsville, AL 35806 - US Check us out at: www.digium.com & www.asterisk.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20160912/d35270f6/attachment.html>