[asterisk-bugs] [JIRA] (ASTERISK-26782) PJSIP Registration/Endpoint not loaded when outbound_proxy is set to IP instead of URI

[Peter Sokolov (JIRA)]

Peter Sokolov created ASTERISK-26782:
----------------------------------------

             Summary: PJSIP Registration/Endpoint not loaded when outbound_proxy is set to IP instead of URI
                 Key: ASTERISK-26782
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26782
             Project: Asterisk
          Issue Type: Bug
      Security Level: None
    Affects Versions: 14.2.1
            Reporter: Peter Sokolov
            Severity: Minor


In chan_sip the outbound proxy could be entered as IP address. Howewer with PJSIP when
outbound_proxy=80.x.x.152
is used, the registration section will not load.

Using URI as proxy, the problem is solved:
outbound_proxy=sip:80.x.x.152:5060

While this requirement is valid and partially documented, there are the following problems:
1.
The other items in pjsip.conf that have to contain URI have _uri in their name, so they are self-explanatory. For outbound_proxy, the URI requirement is only documented for endpoint in the pjsip.conf.sample, but not for registration and aor.

2.
The error end debug messages generated when an IP instead of URI is used does not really give any hint about the problem and makes solving this very difficult:
[Feb  5 15:58:27] DEBUG[3957]: res_pjsip_outbound_registration.c:1289 sip_outbound_registration_apply: Applying configuration to outbound registration 'sip_via_proxy'
[Feb  5 15:58:27] DEBUG[3957]: res_pjsip_outbound_registration.c:962 sip_outbound_registration_state_destroy: Destroying registration state for registration to server 'sip:80.x.x.104' from client 'sip:12345 at 80.x.x.104'
[Feb  5 15:58:27] ERROR[3957]: res_sorcery_config.c:307 sorcery_config_internal_load: Could not create an object of type 'registration' with id 'sip_via_proxy' from configuration file 'pjsip.conf'

3.
Registration/endpoint/aor item is not (re)loaded when the IP is used as outbound_proxy. However on PJSIP reload the old configuration for the Registration/Endpoint remains active and no changes from pjsip.conf are applied for this Registration/Endpoint. On restart of asterisk, the whole Registration/Endpoint is not loaded. This gives an inconsistent behavior. Depending whether reload or restart is done, the registration/endpoint/aor is there or not. I would expect in both cases the complete Registration/endpoint/aor to be removed from the active configuration instead of keeping the old state in the case of reload with errors in pjsip.conf.



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