[asterisk-bugs] [JIRA] (ASTERISK-28705) chan_sip: Phones loose abiltiy to work, core restarting asterisk fixes issue

[Dan (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-28705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249626#comment-249626 ] 

Dan  edited comment on ASTERISK-28705 at 1/31/20 8:49 AM:
----------------------------------------------------------

So questions,   Could this be a UDP only issue?     I'm going to up the receive window. 
I've lost 342190 packets.  
Udp:
    1247999928 packets received
    1032070 packets to unknown port received.
    342190 packet receive errors
    1269965803 packets sent
    342190 receive buffer errors
    0 send buffer errors

Anything else or other ideas?  



was (Author: dwsiemens):
So questions,   Could this be a UDP only issue?     I'm going to up the receive window. 
I've lost 342190 packets.  
Udp:
    1247999928 packets received
    1032070 packets to unknown port received.
    342190 packet receive errors
    1269965803 packets sent
    342190 receive buffer errors
    0 send buffer errors

Anything else?  


> chan_sip: Phones loose abiltiy to work,  core restarting asterisk fixes issue
> -----------------------------------------------------------------------------
>
>                 Key: ASTERISK-28705
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28705
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General
>    Affects Versions: 16.7.0
>         Environment: I have a Redhat HA cluster running with 2 Rhel 7 nodes with asterisk 16.7.0
>            Reporter: Dan 
>            Assignee: Unassigned
>
> Incoming calls on Chan sip still come into the sytem.    Calls in flight stay running.  
> Endpoints get a "x" on them being ploycom phone model vvx310, 311, soundpoint 430, 450's and  zoipe soft phones. 
> THere are no messages about phones loosing registration. 
> A core restart now on asterisk fixes the issue. 
> I think the problem started around asterisk 16.4.0     



--
This message was sent by Atlassian JIRA
(v6.2#6252)