[asterisk-bugs] [JIRA] (ASTERISK-29079) Issue Syncing PJSIP Endpoint Statuses across multiple asterisk Instances/PBX

Asterisk Team (JIRA) noreply at issues.asterisk.org
Sun Sep 13 20:06:43 CDT 2020


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

Asterisk Team commented on ASTERISK-29079:
------------------------------------------

We appreciate the difficulties you are facing, however information request type issues would be better served in a different forum.

The Asterisk community provides support over IRC, mailing lists, and forums as described at http://asterisk.org/community. The Asterisk issue tracker is used specifically to track issues concerning bugs and documentation errors.

If this issue is actually a bug please use the Bug issue type instead.

Please see the Asterisk Issue Guidelines [1] for instruction on the intended use of the Asterisk issue tracker.

Thanks!

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

> Issue Syncing PJSIP Endpoint Statuses across multiple asterisk Instances/PBX
> ----------------------------------------------------------------------------
>
>                 Key: ASTERISK-29079
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29079
>             Project: Asterisk
>          Issue Type: Information Request
>      Security Level: None
>          Components: pjproject/pjsip
>    Affects Versions: 16.9.0
>         Environment: REDHAT7
>            Reporter: Ahmed Raza Jaswal
>            Severity: Critical
>
> Hi,
> I have been trying to follow the below link and was successfully ale to exchange PJSIP device (endpoint) states across two asterisk instances on separate machines:
> https://wiki.asterisk.org/wiki/display/AST/Exchanging+Device+and+Mailbox+State+Using+PJSIP
> e.g if there is a PJSIP endpoint (XX1) on asterisk instance A is UNREGISTERED/BUSY/UNREACHABLE then the device state of PJSIP endpoint (XXX1) on asterisk instance B becomes the same.
> However, when the asterisk instance A crashes or is shutdown, the device states on asterisk instance B stay stuck as they were with instance A and i have to restart asterisk on instance B to make the endpoints available again.
> Is there any expire message that i can include or any module i can ass with the inbound and outbound publish modules that would render the device states of the other asterisk instance being stuck if the first instance goes down.
> Ideas?



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



More information about the asterisk-bugs mailing list