Realtime SIP Peers Do Not Register Any More After Upgrade To Asterisk 13

Home » Asterisk Users » Realtime SIP Peers Do Not Register Any More After Upgrade To Asterisk 13
Asterisk Users 5 Comments

Hello

after I have upgraded from Asterisk 12 to asterisk-certified-13.8-cert1
none of my realtime SIP peers (saved in MySQL DB) register anymore.

[Aug 15 22:03:43] NOTICE[30098]: chan_sip.c:28451
handle_request_register: Registration from
‘‘ failed for ‘78.119.140.190:5076’ – Wrong password
[Aug 15 22:04:13] NOTICE[30098]: chan_sip.c:28451
handle_request_register: Registration from
‘‘ failed for ‘78.119.140.190:5072’ – Wrong password
[Aug 15 22:04:43] NOTICE[30098]: chan_sip.c:28451
handle_request_register: Registration from
‘‘ failed for ‘78.119.140.190:5062’ – Wrong password
[Aug 15 22:04:46] NOTICE[30098]: chan_sip.c:28451
handle_request_register: Registration from
‘‘ failed for ‘78.119.140.190:5060’ – Wrong password
[Aug 15 22:04:53] NOTICE[30098]: chan_sip.c:28451
handle_request_register: Registration from
‘‘ failed for ‘78.119.140.190:5060’ – Wrong password

Is this a known problem ??

Second question I have : can I get the complete list of columns that can be used in realtime database for sip peers somewhere (update for Ast 13)
? Are columns like dtlsenable, dtlsverify, dtlscertfile, dtlscafile, dtlssetup possible ??

Thanks for the help.

Kind regards.

Jonas.

5 thoughts on - Realtime SIP Peers Do Not Register Any More After Upgrade To Asterisk 13

  • The first thing you need to test is if you are properly loading the realtime data. The best way would be to enable “rtcachefriends=yes” and then “sip show peer XXX load”. If you are not getting anything then there is a problem with your realtime setup. I used realtime sip until
    13.7 before switching to PJSIP so it should work.

    I highly recommend that you use alembic to set up your database as this will make sure you are always using the correct database schema.
    You should be able to find the “official” structure in the contrib/realtime/mysql directory of the Asterisk source.

  • Hello

    in contrib/realtime/mysql I see a table ‘sippeers’ with a column
    “transport ENUM(‘udp’,’tcp’,’tls’,’ws’,’wss’,’udp,tcp’,’tcp,udp’) ” but I see no columns dtlsenable, dtlsverify, dtlscertfile, dtlscafile, dtlssetup ?

    So if we can define a sip peer with transport ‘ws’ or ‘wss’, then why are there no columns for the ‘dtls’-part (which is kinda mandatory) ?

    Kind regards.