[asterisk-bugs] [JIRA] (ASTERISK-26458) res_pjsip: Insufficient handling of dynamic public IP address

[Ray Crumrine (JIRA)]

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

Ray Crumrine commented on ASTERISK-26458:
-----------------------------------------

I'm no expert and maybe I am missing something but wouldn't the use of dnsmgr solve this issue? If the ITSP's address is indeed changing, dnsmgr should run every little while and detect the change? As far as the users side [IP address] goes, if his IP is changing it would seem registration should be occurring every 3 minutes or so on all trunks used for inbound calls anyway(??) I use consumer DSL and never really thought about the ITSP address changing but started using dnsmgr because the SRV records also specify a port number which may be different than 5060. Also Callcentric has a setup that uses 25 or 30 [random?] IP addresses for security.

> res_pjsip: Insufficient handling of dynamic public IP address
> -------------------------------------------------------------
>
>                 Key: ASTERISK-26458
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26458
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip, Resources/res_pjsip_outbound_registration
>    Affects Versions: 13.11.2
>         Environment: FreeBSD 10.3-RELEASE-p9 i386
>            Reporter: Andreas Wetzel
>            Severity: Minor
>
> I have a consumer DSL line which gets disconnected from the ISP's side every 24 hours. When that happens a number of things occur:
> - My IP address changes
> - DNS may return a different IP address for my ITSP's SIP server
> - All outbound registrations need to be renewed, otherwise I get a '401 unauthorized response' from my ITSP's SIP server when trying to place an outbound call prior to the corresponding registration being renewed.
> Currently none of the reloading mechanisms present in asterisk seem to make it refetch the machine's public IP address (the one that is shown in 'pjsip dump endpt' under 'published as'), or to force an immediate renewal of all configured outbound registrations. Only way is to do a full restart of asterisk i.e. 'core restart gracefully'.



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