Calls are not processing in queue though IVR still can be processed (sip_autodestruct messages found)

VitalPBX Community Support General Discussion Calls are not processing in queue though IVR still can be processed (sip_autodestruct messages found)

  • Post
    yazarlwin
    Participant

    We face the call issue yesterday after seeing below error in master server. All calls are failed to proceed to queue but IVR still can be processed. It had never happened before. Only when we rebooted master server manually and swapped to secondary server, the call were back to normal. Please help check how to prevent this issue.

    Apr 29 13:49:49 voice01 asterisk: [2020-04-29 13:49:49] #033[1;31mWARNING#033[0m[25074]: #033[1;37mchan_sip.c#033[0m:#033[1;37m4387#033[0m #033[1;37m__sip_autodestruct#033[0m: Autodestruct on dialog ‘isbciigffzhltor4ptqreqeqtqogoitenfnz@10.18.5.64_b2b-1’ with owner SIP/outbound-000788bb in place (Method: BYE). Rescheduling destruction for 10000 ms
    Apr 29 13:49:55 voice01 asterisk: [2020-04-29 13:49:55] #033[1;31mWARNING#033[0m[25074]: #033[1;37mchan_sip.c#033[0m:#033[1;37m4387#033[0m #033[1;37m__sip_autodestruct#033[0m: Autodestruct on dialog ‘isbciigffzhltor4ptqreqeqtqogoitenfnz@10.18.5.64_b2b-1’ with owner SIP/outbound-000788bb in place (Method: BYE). Rescheduling destruction for 10000 ms
    Apr 29 13:50:02 voice01 asterisk: [2020-04-29 13:50:02] #033[1;31mWARNING#033[0m[25074]: #033[1;37mchan_sip.c#033[0m:#033[1;37m4387#033[0m #033[1;37m__sip_autodestruct#033[0m: Autodestruct on dialog ‘isbciigffzhltor4ptqreqeqtqogoitenfnz@10.18.5.64_b2b-1’ with owner SIP/outbound-000788bb in place (Method: BYE). Rescheduling destruction for 10000 ms

    0
Viewing 4 replies - 1 through 4 (of 4 total)
  • Replies
    Up
    0
    Down

    Are these two servers in HA? Right?

     

    0
    yazarlwin
    Participant
    Up
    0
    Down

    Yes. They are in HA. There were more than 13000 sip_autodestruct messages on master server at the time of incident.

    0
    yazarlwin
    Participant
    Up
    0
    Down
    We assumed this problem was related to chan_sip and we migrated all extensions and trunks to pjsip. Later we found warning messages that says ‘task processors exceed 500 scheduled task’ messages and found AMI stopped and PJSIP endpoint registration decreased. Finally we increased asterisk max file to 50K and MWI value to double. So far it seems fine.
    0
    Up
    0
    Down
    Where did you change the MWI?
    0
Viewing 4 replies - 1 through 4 (of 4 total)

Tagged: 

  • You must be logged in to reply to this topic.