Re: [asterisk-users] PJSIP Weirdness, or just my weirdness?

2016-09-12 Thread Steve Murphy 
SOLVED!

Many THANKS to George and Anthony! See at the very end, my comments...



On Thu, Sep 8, 2016 at 5:58 PM, Anthony Joseph Messina <
amess...@messinet.com> wrote:

> On Thursday, September 8, 2016 1:12:36 PM CDT Steve Murphy wrote:
> > Hello!
> >
> > Oh, wise ones, ponder with me over two of the surprises that
> > populate the universe!
> >
> >
> > I have a phone, that I sometimes cannot reach, connected via pjsip.
> > It can call other extensions just fine, it can call out over a
> > trunk to my cell, all is well, but getting a call? Forget it most of the
> > time.
> >
> > Here is all the config relevant to that phone:
> >
> >
> > [murftest12]
> > type=aor
> > qualify_frequency=1992
> > max_contacts=2
> >
> > [murftest12]
> > type=auth
> > auth_type=userpass
> > username=murftest12
> > password=SjU3
> >
> > [transport-udp]
> > type=transport
> > protocol=udp
> > bind=0.0.0.0:57969
> >
> >
> > [murftest12]; Cisco SPA514G mac=A4:93:4C:FE:1D:A2
> > type=endpoint
> > auth=murftest12
> > transport=transport-udp
> > aors=murftest12
> > moh_suggest=default
> > force_rport=yes
> > rewrite_contact=yes
> > rtp_symmetric=yes
> > dtmf_mode=rfc4733
> > disallow=all
> > allow=ulaw ; from phonetype
> > allow=g722 ; from phonetype
> > allow=alaw ; from phonetype
> > allow=alaw ; from phonetype (G.729 replaced with alaw)
> > direct_media=no
> > context=phone
> > rtp_timeout=120
> > set_var=__phoneid=12
> > set_var=__contacttypeid=4
> > set_var=__phonelineid=78
> > callerid="Steve Murphy" <101>
> > call_group=2
> > pickup_group=2
> > mailboxes=101@murftest
> > language=en
> > send_rpid=yes
> > send_pai=yes
> >
> > ​OK, that completes the config (I hope).
> >
> > Now, when I run "pjsip show endpoints, I get:​
> >
> > SFO02-HostedPBXPJSip-Dev03*CLI> pjsip show endpoints
> >
> >  Endpoint:  
> >   
> > I/OAuth:   ..
> > ...>
> > Aor:  
> > 
> >   Contact:   
> >  
> >   Transport:
> > 
> >Identify:   ..
> > ...>
> > Match:  
> > Channel:  
> >   
> > Exten:   CLCID: 
> >  ===
> > ==
> >
> >  Endpoint:  murftest12/101   Not in
> > use0 of inf
> >  InAuth:  murftest12/murftest12
> > Aor:  murftest12 2
> >   Contact:  murftest12/sip:murftest12@67.215.23.186:54 171a08228b
> > Unavail   0.000
> >   Contact:  murftest12/sip:murftest12@67.215.23.186:21 d9a15f4e35
> > Avail50.514
> >   Transport:  transport-udp udp  0  0  0.0.0.0:57969
> >
> > ​ Note that there are TWO Contact: entries! one Avail, the other
> Unavail...
> > the show endpoints doesn't display all the URL, but the show contacts
> does:
> >
> > ​  Contact:  murftest12/sip:murftest12@67.215.23.186:21800  d9a15f4e35
> > Avail50.514
> >   Contact:  murftest12/sip:murftest12@67.215.23.186:54004  171a08228b
> > Unavail   0.000
> >
> > None of my other phones have two contacts listed and this phone, a
> > cisco-spa-514, has just one sip account...
> >
> > The trouble is, when I try to call it sometimes the INVITE is
> directed
> > to the "Unavail" entry, and the call never completes. The phone doesn't
> > even ring then. Any ideas? I tried to get the "Unavail" entry out... I
> > removed it from the db, I rebooted the phone, restarted asterisk, and it
> is
> > still there.
> >
> > MYSTERY #2:
> >
> > The above cisco-spa, when it calls out over the trunk, all is well,
> > wonderful 2-way audio.
> > But when I do the same operation from my yealink phones, I get my cell
> with
> > one-way audio.
>
> I just resolved a similar issue with a new Yealink phone and PJSIP.  It
> seems
> that Asterisk (depending on many transcoding parameters and types of calls)
> may send out a different codec on leg B than it receives on leg A.  While
> less
> than optimal for the end user, this is allowed by the RFCs.  Yealink
> doesn't
> seem to handle this well.  The firmware referenced in this link fixed the
> issue for me, as least with my T48G and DAHDI/PJSIP calls.
>
> http://forum.yealink.com/forum/showthread.php?tid=8330=39161#pid39161
>
>
> > It's a classic NAT situation: the phone system is in a droplet at digital
> > ocean, but my phones are here at home behind a NAT. I see only 3 NAT
> > related options:
> >
> > force_rport
> > rtp_symmetric
> > rewrite_contact
> >
> > and I set them all to "yes", and they can call each other, but as
> > explained, in
> > dialing out thru a trunk, the yealinks get one-way audio...
> >
> > Any more NAT options?
> >
> > many thanks...
> >
> > murf
>
>
​George's previous message on this thread, plus this one were very helpful
in solving my problems.

I discovered:

1. Mystery #1 was a combination of factors:
   1. The max_contacts=1 and remove_existing=yes did in fact

Re: [asterisk-users] Mysql PJSIP realtime > 13.10?

2016-09-12 Thread George Joseph 
On Mon, Sep 12, 2016 at 3:51 PM, Carlos Chavez 
wrote:

> On 9/12/16 4:21 PM, George Joseph wrote:
>
>
>
> On Mon, Sep 12, 2016 at 3:01 PM, Carlos Chavez 
> wrote:
>
>> On 9/12/16 3:39 PM, George Joseph wrote:
>>
>>
>>
>> On Mon, Sep 12, 2016 at 2:31 PM, George Joseph 
>> wrote:
>>
>>>
>>>
>>> On Mon, Sep 12, 2016 at 2:14 PM, Carlos Chavez 
>>> 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@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@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@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@192.168.2.165:5060
 ;transport=udp' to AOR '2001'
   == Contact 2001/sip:2001@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
>
>
> Ok, thank you for the help.  I'll be trying out ODBC later today and
> test it for a few days.  You should probably mark res_config_mysql as
> deprecated now since it will not work with anything higher than 13.10 as is.
>
>
I created an issue for it anyway:
https://issues.asterisk.org/jira/browse/ASTERISK-26362


> --
>
> 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
-- 
_
-- 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:

Re: [asterisk-users] Mysql PJSIP realtime > 13.10?

2016-09-12 Thread Carlos Chavez 

On 9/12/16 4:21 PM, George Joseph wrote:




On Mon, Sep 12, 2016 at 3:01 PM, Carlos Chavez 
> wrote:


On 9/12/16 3:39 PM, George Joseph wrote:




On Mon, Sep 12, 2016 at 2:31 PM, George Joseph
> wrote:



On Mon, Sep 12, 2016 at 2:14 PM, Carlos Chavez
> 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@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@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@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@192.168.2.165:5060
;transport=udp' to
AOR '2001'
  == Contact 2001/sip:2001@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


Ok, thank you for the help.  I'll be trying out ODBC later today 
and test it for a few days.  You should probably mark res_config_mysql 
as deprecated now since it will not work with anything higher than 13.10 
as is.



--


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

Re: [asterisk-users] Mysql PJSIP realtime > 13.10?

2016-09-12 Thread George Joseph 
On Mon, Sep 12, 2016 at 3:01 PM, Carlos Chavez 
wrote:

> On 9/12/16 3:39 PM, George Joseph wrote:
>
>
>
> On Mon, Sep 12, 2016 at 2:31 PM, George Joseph  wrote:
>
>>
>>
>> On Mon, Sep 12, 2016 at 2:14 PM, Carlos Chavez 
>> 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@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@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@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@192.168.2.165:5060;transport=udp'
>>> to AOR '2001'
>>>   == Contact 2001/sip:2001@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
-- 
_
-- 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

Re: [asterisk-users] Mysql PJSIP realtime > 13.10?

2016-09-12 Thread Annus Fictus 

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 > wrote:




On Mon, Sep 12, 2016 at 2:14 PM, Carlos Chavez
> 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@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@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@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@192.168.2.165:5060
;transport=udp' to AOR '2001'
  == Contact 2001/sip:2001@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.

--
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

Re: [asterisk-users] Mysql PJSIP realtime > 13.10?

2016-09-12 Thread Carlos Chavez 

On 9/12/16 3:39 PM, George Joseph wrote:




On Mon, Sep 12, 2016 at 2:31 PM, George Joseph > wrote:




On Mon, Sep 12, 2016 at 2:14 PM, Carlos Chavez
> 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@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@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@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@192.168.2.165:5060
;transport=udp' to AOR '2001'
  == Contact 2001/sip:2001@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.


--
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

Re: [asterisk-users] Mysql PJSIP realtime > 13.10?

2016-09-12 Thread Carlos Chavez 

On 9/12/16 3:21 PM, Annus Fictus wrote:


Hello,

is there any reason you don't use ODBC with MySQL?

Regards


El 12/09/2016 a las 15:14, Carlos Chavez escribió:
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@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@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@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@192.168.2.165:5060;transport=udp' to AOR '2001'
  == Contact 2001/sip:2001@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.






Unless you use non packaged odbc on CentOS 7, Asterisk keeps crashing.

--
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

Re: [asterisk-users] Mysql PJSIP realtime > 13.10?

2016-09-12 Thread George Joseph 
On Mon, Sep 12, 2016 at 2:31 PM, George Joseph  wrote:

>
>
> On Mon, Sep 12, 2016 at 2:14 PM, Carlos Chavez 
> 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@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@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@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@192.168.2.165:5060;transport=udp'
>> to AOR '2001'
>>   == Contact 2001/sip:2001@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
-- 
_
-- 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

Re: [asterisk-users] Mysql PJSIP realtime > 13.10?

2016-09-12 Thread George Joseph 
On Mon, Sep 12, 2016 at 2:14 PM, Carlos Chavez 
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@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@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@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@192.168.2.165:5060;transport=udp'
> to AOR '2001'
>   == Contact 2001/sip:2001@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.


>
> --
> 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
-- 
_
-- 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

Re: [asterisk-users] Mysql PJSIP realtime > 13.10?

2016-09-12 Thread Annus Fictus 

Hello,

is there any reason you don't use ODBC with MySQL?

Regards


El 12/09/2016 a las 15:14, Carlos Chavez escribió:
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@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@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@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@192.168.2.165:5060;transport=udp' to AOR '2001'
  == Contact 2001/sip:2001@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.





--
_
-- 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

[asterisk-users] Mysql PJSIP realtime > 13.10?

2016-09-12 Thread Carlos Chavez 
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@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@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@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@192.168.2.165:5060;transport=udp' to AOR '2001'
  == Contact 2001/sip:2001@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.


--
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

Re: [asterisk-users] Queue show : failed to extend from 240 to 327

2016-09-12 Thread Richard Mudgett 
On Sat, Sep 10, 2016 at 5:18 AM, Jonas Kellens 
wrote:

> On 10-09-16 09:42, Jonas Kellens wrote:
>
>
> On 10-09-16 00:50, Richard Mudgett wrote:
>
>
>
> On Fri, Sep 9, 2016 at 5:37 PM, Jonas Kellens 
> wrote:
>
>> Hello
>>
>> when I type on the Asterisk CLi 'queue show', I first get a list of my
>> queues and then the following :
>>
>>
>> failed to extend from 240 to 327
>>
>
> 
>
> failed to extend from 240 to 334
>>
>>
>> I could not find any information on this on the web, except this :
>> https://issues.asterisk.org/jira/browse/ASTERISK-8828
>>
>> which is an old 'bug' that should have been fixed meanwhile.
>>
>> Any more thoughts on why I should be getting this message when asking
>> information about queues (I don't see this message on any other command).
>>
>
> That message is a result of trying to build a string where the buffer is
> too
> small to contain it.  I would expect that there is a truncated string in
> the
> 'queue show' output.
>
> You haven't stated which Asterisk version you are using.  It may already
> be fixed.
>
>
> Hello
>
> I have this with asterisk-certified-13.8-cert1 and also with
> asterisk-certified-13.8-cert2
>
> Could it be that the membername value (and interface value) in my realtime
> MySQL table queue_members is too long ??
>
> It looks like this :
>
> Local/01_vlaebidvxcrxrheebdin354@ExternalCallFromQueue
> Local/02_vlaebidvxcrxrheebdin114@ExternalCallFromQueue
> Local/03_vlaebidvxcrxrheebdin329@ExternalCallFromQueue
>
> I have the idea that this is the "problem".
>
> FYI : it also makes that Asterisk restarts (with core dump) whenever a
> queue is addressed. Very *annoying* !
>
>
> So string size too large and buffer too small.
>
> FYI : I do not have this with any version of Asterisk 1.8. This is a
> "problem" that exists only in Asterisk 13.
>
>
>
> How to fix this ??
>
>
> This is an example output for queue show <> on Asterisk version
> asterisk-certified-13.8-cert2 (same on asterisk-certified-13.8-cert1) :
>
>
> sip*CLI> queue show cvikbubohirndceiaetsq
> cvikbubohirndceiaetsq has 0 calls (max unlimited) in 'ringall' strategy
> (0s holdtime, 0s talktime), W:0, C:0, A:0, SL:0.0% within 0s
>Members:
>   cvikbubohirndceiaets012 
> (Local/cvikbubohirndceiaets012@ExternalCallFromQueue
> from Local/cvikbubohirndceiaets012@ExternalCallFromQueue) (ringinuse
> disabled) (realtime) (Not in use) has taken no
>   cvikbubohirndceiaets248 
> (Local/cvikbubohirndceiaets248@ExternalCallFromQueue
> from Local/cvikbubohirndceiaets248@ExternalCallFromQueue) (ringinuse
> disabled) (realtime) (Not in use) has taken no
>   cvikbubohirndceiaets428 
> (Local/cvikbubohirndceiaets428@ExternalCallFromQueue
> from Local/cvikbubohirndceiaets428@ExternalCallFromQueue) (ringinuse
> disabled) (realtime) (Not in use) has taken no
>   cvikbubohirndceiaets461 
> (Local/cvikbubohirndceiaets461@ExternalCallFromQueue
> from Local/cvikbubohirndceiaets461@ExternalCallFromQueue) (ringinuse
> disabled) (realtime) (Not in use) has taken no
>   cvikbubohirndceiaets629 
> (Local/cvikbubohirndceiaets629@ExternalCallFromQueue
> from Local/cvikbubohirndceiaets629@ExternalCallFromQueue) (ringinuse
> disabled) (realtime) (Not in use) has taken no
>No Callers
>
> failed to extend from 240 to 327
> failed to extend from 240 to 327
> failed to extend from 240 to 327
> failed to extend from 240 to 327
> failed to extend from 240 to 327
>

I have created https://issues.asterisk.org/jira/browse/ASTERISK-26360 to
keep track of the
issue.  I have also put a patch up on gerrit to increase the size of the
buffer.  Since it is
unlikely that you have a Digium SLA [1] concerning certified Asterisk, the
fix will not make its
way into certified asterisk.

Richard

[1] https://www.digium.com/products/asterisk/certified-asterisk
-- 
_
-- 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

Re: [asterisk-users] Can't park call more than once

2016-09-12 Thread asterisk 

That did the trick. I can't thank you enough.
Regards;
John

On 2016-09-11 14:35, Doug Lytle wrote:

On 09/11/2016 10:31 AM, aster...@voipbusiness.us wrote:


Has anyone seen this before? Any insight at all would be greatly
appreciated.


 In features.conf, look for parkedcallreparking, I have mine set to =
caller

 Doug



--
_
-- 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

[asterisk-users] Originate Fails inside Dial() M(macro) or U(subroutine)

2016-09-12 Thread Saint Michael 
​Is this by design? ​I execute  a Dial() with a parameter M(macro) or
U(subroutine). Inside either I use the application originate. The variable
${ORIGINATE_STATUS} says "SUCCESS" but no call is actually executed. Should
I file a bug report?
-- 
_
-- 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