[asterisk-bugs] [JIRA] (ASTERISK-30078) ari / pjsip: Push "identify" with hostname "match", fails due to invalid SQL query generation

[Joshua C. Colp (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-30078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joshua C. Colp updated ASTERISK-30078:
--------------------------------------

    Summary: ari / pjsip: Push "identify" with hostname "match", fails due to invalid SQL query generation  (was: ARI Push "identify" with hostname "match", fails due to invalid SQL query generation)

> ari / pjsip: Push "identify" with hostname "match", fails due to invalid SQL query generation
> ---------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-30078
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-30078
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_ari_applications, Resources/res_pjsip
>    Affects Versions: 18.12.1
>         Environment: CentOS 7 using packages from Tucny asterisk-18.12.1-1.el7.x86_64 and asterisk-pjsip-18.12.1-1.el7.x86_64
>            Reporter: Ron Lockard
>
> ARI pushing a PJSIP "identify" that contains a hostname with multiple IPs for the "match", results in the generation of an invalid SQL insert query.
> res_config_odbc.c: SQL Prepare failed! [INSERT INTO ps_endpoint_id_ips (id, match, match, match, match, srv_lookups, endpoint, match_header) VALUES (?, ?, ?, ?, ?, ?, ?, ?)]
> This was for a hostname that resolved to 4 IP addresses.  I believe the desired behavior should be, the push should directly insert the hostname rather than resolved IP addresses so that future DNS changes would be picked up.



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