[asterisk-users] TCP transport and BLF

[Alec Davis]

Yes, but we don't use TCP transport.
 
In one site we have about 40 GXP2000/GXP2010's and I've seen this alot.
 
Rebooting the phone fixes the issue for about a while - well a few minutes,
then the old BLF subscription expires on the server with a high 'version'
number, the BLF's stop working at this stage.
A 2nd reboot of the phone is then required.
 
One of our senarios was that phones are randomly rebooted at night from
power glitch, etc.
    The result is phone resubscribes within a few minutes, but before the
previous BLF subscription on the server has expired.
 
    After a while the previous subscription expires on the server, sending
out a final 'timed out' NOTIFY, which the phone happily accepts, with a the
high 'version' number of the last subscription.
    Now the phone is expecting the next NOTIFY to have a higher 'version'
number but it won't come until the server has sent enough updates to be
greater then the previous version number, as new subcriptions start the
'version' number at '0'.
 
Enabling 'syslog on error' on the phone helped me track this down. Didn't
fix anything, just helped me understand.
 
I did write a patch for our system, that doesn't send the timeout NOTIFY,
which is inline with MWI and CALL_COMPLETION
 
If the patch below helps, let me know and I'll get a bug report raised.
 
Index: channels/chan_sip.c
===================================================================
--- channels/chan_sip.c (revision 351705)
+++ channels/chan_sip.c (working copy)
@@ -3822,7 +3822,7 @@
        struct sip_pvt *p = (struct sip_pvt *)data;
 
        /* If this is a subscription, tell the phone that we got a timeout
*/
-       if (p->subscribed && p->subscribed != MWI_NOTIFICATION &&
p->subscribed != CALL_COMPLETION) {
+       if (p->subscribed && p->subscribed != MWI_NOTIFICATION &&
p->subscribed != CALL_COMPLETION && p->subscribed != DIALOG_INFO_XML) {
                transmit_state_notify(p, AST_EXTENSION_DEACTIVATED, 1,
TRUE);   /* Send last notification */
                p->subscribed = NONE;
                append_history(p, "Subscribestatus", "timeout");
@@
 
 
Alec Davis
 


  _____  

From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Bryant
Zimmerman
Sent: Saturday, 28 January 2012 8:03 a.m.
To: asterisk-users at lists.digium.com
Subject: Re: [asterisk-users] TCP transport and BLF


I have some reports from users that are using TCP transport that their BLF
lights are not turning on or getting off hook and ringing notifications.
Has anyone seen this issue.

Asterisk 1.8.x
Phones Grand Stream 2010


Thanks

Bryant Zimmerman (ZK Tech Inc.)
616-855-1030 Ext. 2003

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20120128/57fab656/attachment.htm>