[asterisk-bugs] [JIRA] (ASTERISK-28211) Path-Header is used for OPTIONS but not for INVITE

[Sebastian Denz (JIRA)]

Sebastian Denz created ASTERISK-28211:
-----------------------------------------

             Summary: Path-Header is used for OPTIONS but not for INVITE
                 Key: ASTERISK-28211
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28211
             Project: Asterisk
          Issue Type: Bug
      Security Level: None
          Components: Resources/res_pjsip
    Affects Versions: 16.0.0
         Environment: Asterisk 16.0.1 on Debian 9
            Reporter: Sebastian Denz


I am using Kamailio as Edgeproxy between my phones and Asterisk.

In this scenario Kamailio terminates a TLS Connections, checks the client certificate and sets a custom Header to help Asterisk to identify the corresponding endpoint. Which is working fine so far.

As Asterisk is not able to reach the phones directly, the Path Header is set by Kamailio.
The AORs for the phones have support_path set to true.

A few days before, the whole setup was running fine, but in the meantime the Handling of the Path-Header stopped working.

I am not aware of any relevant changes in the setup and i tried to rollback to a version which was known to work.
But when calling from one phone to another, Asterisk does not evaluate the Path-Header for the target endpoint anymore...

This is the case for INVITE Routing using Dial(), sending OPTIONS is working fine and the Path leads to a set Route-Header in the outgoing OPTIONS packet...

For debugging purposes i added some more logging in res_pjsip_path.c to see when the functions are called in the CLI.
Due to that i can tell, that the contact Parameter for path_outgoing_request() is NULL in that case...

Unfortunately i am not able to dig deeper to find the reason for that.

Seems to be the same like https://community.asterisk.org/t/wrong-d-uri-for-invites-with-pjsip-and-path/74079

But at least at the moment the problem is reproducable.. So i would appreciate any hints for further debugging or fixes of course! ;)



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