[asterisk-users] Extra REGISTER messages sent by Asterisk when subscribe for MWI is defined in zoiper

[Olli Heiskanen]

Hello,

I noticed something that might be a result from the fix suggested here, so
I'll continue a bit on this thread. After removing the callbackextension
field from my realtime sip peer table, the following started happening:  I
issued command 'sip reload' on the cli and get the following warning:

WARNING[24427]: res_config_mysql.c:501 realtime_multi_mysql: MySQL
RealTime: Failed to query database: Unknown column 'callbackextension' in
'where clause'

This must be a result from removing that field from the db, but somewhere
in the code there is a select statement where the callbackextension field
is used in the where clause, resulting to the above warning.

I wonder if this something to be worried about, or is going to cause
problems later? My goal is of coure just to handle calls, save cdrs, do pbx
features etc with this asterisk.

cheers,
Olli



2014-07-15 16:56 GMT+03:00 Olli Heiskanen <ohjelmistoarkkitehti at gmail.com>:

>
> Wow, thanks Joshua, it would've taken me forever to find the answer there.
> It did the trick and the registrations look much better.
>
> Merci beaucoup!
>
> - Olli
>
>
>
> 2014-07-15 16:26 GMT+03:00 Joshua Colp <jcolp at digium.com>:
>
> Olli Heiskanen wrote:
>>
>>>
>>> Thanks, there are no register lines in my sip.conf, but I have defined
>>> callbackextension fields in the realtime table, to be the same value as
>>> the extension name. In this case, extension 771 has callbackextension
>>> value 771. I tried replacing those with null values but that had no
>>> effect on the outcome.
>>>
>>
>> The callbackextension is the reason this is happening.
>>
>> From sip.conf.sample:
>>
>> ; A similar effect can be achieved by adding a "callbackextension" option
>> in a peer section.
>> ; this is equivalent to having the following line in the general section:
>> ;
>> ;        register => username:secret at host/callbackextension
>> ;
>> ; and more readable because you don't have to write the parameters in two
>> places
>> ; (note that the "port" is ignored - this is a bug that should be fixed).
>>
>> Remove that column from your table, restart Asterisk, and it should go
>> away.
>>
>>
>> --
>> Joshua Colp
>> Digium, Inc. | Senior 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 --
>> New to Asterisk? Join us for a live introductory webinar every Thurs:
>>               http://www.asterisk.org/hello
>>
>> asterisk-users mailing list
>> To UNSUBSCRIBE or update options visit:
>>   http://lists.digium.com/mailman/listinfo/asterisk-users
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20140718/65e0b474/attachment.html>