[asterisk-users] Asterisk realtime in combination with ARI - error while trying to prepare SQL statement for writing into database

[Joshua Colp]

On Thu, Jul 13, 2017, at 10:01 AM, Floimair Florian wrote:
> Hey guys!
> 
> I successfully got Asterisk realtime (14.6.0) with MariaDB (MySQL fork)
> running on Debian 9.
> 
> I will document the steps to do so shortly (the main difference is
> default encoding and the odbc connector & its configuration).
> 
> What I’m trying to do now is to use ARI to create PJSIP endpoints as
> outlined in this wiki article:
> https://wiki.asterisk.org/wiki/display/AST/ARI+Push+Configuration
> 
> So far so good. Excecuting the examples using curl PUT aor and auth was
> working fine, when I ran the line for the endpoint object I got an error
> in the Asterisk CLI and log stating:

<snip>

> 
> Carefully comparing the attributes from the JSON output of the curl
> statement (which was successfully completed) and the columns in the
> database I found the culprit:
> 
> The database is missing the following attribute: „dtls_fingerprint“
> I prepared my database using the alembic scripts from the 14.6.0 source.
> After manually adding the column to the database and restarting Asterisk
> the statement was successfully executed and everything works fine now.
> 
> In addition to the missing attribute there are few columns in the
> database table that do not match to a JSON attribute in the pjsip
> endpoint object.
> These are:
> 
> -          contact_deny
> 
> -          contact_permit
> 
> -          contact_user
> 
> -          deny
> 
> -          disallow
> 
> -          external_media_address
> 
> -          permit
> 
> -          redirect_method
> 
> 
> So far to my findings.
> 
> Should I file a bug-report for this?

Yes, an issue should be reported for this.

-- 
Joshua Colp
Digium, Inc. | Senior Software Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - US
Check us out at: www.digium.com & www.asterisk.org