[asterisk-bugs] [JIRA] Status Changed to Waiting for Development: (ASTERISK-20418) peer Call-ID change after core reload

[Rusty Newton (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-20418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rusty Newton updated ASTERISK-20418:
------------------------------------

    Status: Open  (was: Triage)

> peer Call-ID change after core reload
> -------------------------------------
>
>                 Key: ASTERISK-20418
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20418
>             Project: Asterisk
>          Issue Type: New Feature
>      Security Level: None
>          Components: Channels/chan_sip/General, Channels/chan_sip/Interoperability
>    Affects Versions: 10.7.0
>         Environment: FreePBX distro (Asterisk 10.7.0 built by root @ jenkins6.schmoozecom.net on a x86_64 running Linux on 2012-08-13 19:26:17 UTC)
>            Reporter: Edwin
>
> registration Call-ID changes after core reload
> [Moved the following from the Reference Notes section]
> Each time we execute an core reload (on asterisk 10.7.0 / FreePBX distro) the registration Call-ID changes (new CSeq).
> This behavior causes problems with our sip provider. Every time a core reload has been given this is a new binding on the provider side (opensips). So for incomming calls a INVITE is sent per binding (as long as the expire time is set for the former registration).
> We think this behavior was different in asterisk 1.4 because we never had complaints about strange behavior after reloading asterisk.
> Would it be possilble to keep the same registration Call-ID after an core reload or set a static Call-ID for peer registrations?.
> Also see ticket http://www.freepbx.org/trac/ticket/5967

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira