[asterisk-bugs] [JIRA] (ASTERISK-26597) func_pjsip_contact: PJSIP_CONTACT function references MD5ed AOR contact

Niklas Larsson (JIRA) noreply at issues.asterisk.org
Tue Jan 17 05:21:03 CST 2023


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

Niklas Larsson commented on ASTERISK-26597:
-------------------------------------------

Bumping this as well - doing an ugly workaround of setting the hashes as "static" variables and checking status on the contact before dialing (and failing to a Reachable contact)

We use one AOR with multiple contacts and dialing using: 
Dial(PJSIP/${SIPTRUNK}/sip:${DIALNUMBER}@X.X.X.X:5060,${DIALTIME},${PSTN_DIALOPTS}) 

And to get some kind of working failover, is to look at ${PJSIP_CONTACT(${SIPTRUNK_X_X_X_X_HASH},status)} before trying to dial

> func_pjsip_contact: PJSIP_CONTACT function references MD5ed AOR contact
> -----------------------------------------------------------------------
>
>                 Key: ASTERISK-26597
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26597
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Channels/chan_pjsip
>    Affects Versions: 13.12.2
>         Environment: n/a
>            Reporter: sharan h
>
> In reference to:
> https://community.asterisk.org/t/cant-get-pjsip-contact-function-to-work/68740/2
> I am requesting a change in the PJSIP_CONTACT function to reference the actual contact from the aor.  Currently, using the PJSIP_CONTACT function requires the use of the PJSIP_AOR function to return the exact dynamic URI.  
> It's not intuitive, and the documentation doesn't clarify how to use the function clearly.



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



More information about the asterisk-bugs mailing list