[asterisk-bugs] [JIRA] (ASTERISK-26210) chan_sip: NOTIFYs for BLF start queuing up and fail to be sent out, Asterisk 13
George Joseph (JIRA)
noreply at issues.asterisk.org
Fri Aug 12 10:37:57 CDT 2016
[ https://issues.asterisk.org/jira/browse/ASTERISK-26210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
George Joseph updated ASTERISK-26210:
-------------------------------------
Assignee: Steven Sedory (was: George Joseph)
Status: Waiting for Feedback (was: Open)
The patch that fixed the issue in ASTERISK-21677 was definitely applied to 13 so we're probably looking at a different cause.
Were you able to get an actual packet trace against a problem phone? Also could you do a {{sip show settings}} and attach it? I'm interested in timer_t1, timer_b and the subscription timers. If they're set per peer, the the settings for one of the peers in question would help.
thanks
> chan_sip: NOTIFYs for BLF start queuing up and fail to be sent out, Asterisk 13
> -------------------------------------------------------------------------------
>
> Key: ASTERISK-26210
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-26210
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Channels/chan_sip/Subscriptions
> Affects Versions: 13.9.1
> Environment: ESXi Host VM, CentOS 6.6 (FreePBX's Current Distro: 10.13.66-64bit), Quad Core Intel Xeon E5530 2.4GHz, 4GB RAM
> Reporter: Steven Sedory
> Assignee: Steven Sedory
> Attachments: afterreboot_000001, afterreboot_000002, afterreboot_000003, afterreboot_000004, afterreboot_000005, afterreboot_000006, afterreboot_000007, debug_log_123456
>
>
> The issue we are experiencing seems exactly the same as the one already "fixed" here: ASTERISK-21677
> The initial description there is exactly what we're experiencing. The main difference is that we're on CentOS 6.6, and Asterisk 13.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list