[asterisk-bugs] [JIRA] (ASTERISK-26266) SIP Outbound Registration is not working correct

[Joshua Colp (JIRA)]

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

Joshua Colp commented on ASTERISK-26266:
----------------------------------------

Thank you for taking the time to report this bug and helping to make Asterisk better. Unfortunately, we cannot work on this bug because your description did not include enough information. Please read over the Asterisk Issue Guidelines [1] which discusses the information necessary for your issue to be resolved and the format that information needs to be in. We would be grateful if you would then provide a more complete description of the problem. At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the problem.
2. The behavior you expected and the location of documentation that led you to that expectation.
3. The behavior you actually encountered.

To demonstrate the issue in detail, please include Asterisk log files generated per the instructions on the wiki [2]. If applicable, please ensure that protocol-level trace debugging is enabled, e.g., 'sip set debug on' if the issue involves chan_sip, and configuration information such as dialplan and channel configuration.

Thanks!

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

[2] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information

In this case the complete SIP interaction with the remote server would be needed.

> SIP Outbound Registration is not working correct
> ------------------------------------------------
>
>                 Key: ASTERISK-26266
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26266
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/Registration
>    Affects Versions: 11.23.0
>         Environment: Centos 6 64bit
>            Reporter: Antonis Psaras
>            Severity: Critical
>
> It seems that Asterisk when acting as user to a sip provider does not respect the expiration proposed by sip provider. Moreover, even if expiration offered is within the ranges of the provider, instead of using the registration specific expiration configured at the registration string with ~expiry, is using the defaultexpiry general sip configuration.
> To re-produce it, create a registration string with expiration ie 600 
> register => 123:123 at 1.1.1.1~600
> and set defaultexpiry to 3600.
> On the sip trace you will see that Asterisk offers 600 expiration but when you run sip show registry you see that refresh is at 3600 which can be check that is true from the sip trace which has no re-registration with in 10 minutes.



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