[asterisk-users] ARI delayed 183 due to device_state lookup

Jöran Vinzens vinzens at sipgate.de
Wed Feb 20 03:28:52 CST 2019

Hi all,

we are searching for shorter post dial delay and we were wondering why the
asterisk takes about 190ms from an ARI Command Playback or Answer until the
SIP Message is send out.

We took the latest code from github and used the python scripts provided by
sangoma in order to start a playback. Using this setup we ensure it is not
our setup which causes the delay.

So we see these likes in the log:

[2019-02-20 10:13:50.985] VERBOSE[3079] res_ari.c: <--- Sending ARI
response to --->
201 Created
Location: /ari/playbacks/a5cb3f78-77db-41f8-9846-147ccb47411d
Content-type: application/json

[2019-02-20 10:13:50.987] DEBUG[3079] http.c: HTTP keeping session open.
[2019-02-20 10:13:51.178] DEBUG[2900] devicestate.c: No provider found,
checking channel drivers for PJSIP - 1111
[2019-02-20 10:13:51.179] DEBUG[2900] devicestate.c: Changing state for
PJSIP/1111 - state 3 (Busy)

As you can see the ARI Command gets acknowledged by the 201 response. now
the asterisk tries to set the device state to busy. It seems to take about
190ms to lookup the provider before it fails.

In our setup we do not use device states al all. Is there any way to
deactivate this internal lookup or to speed it up? We already tried to
unload some modules using device state without any success.

Jöran Vinzens - vinzens at sipgate.de

sipgate GmbH - Gladbacher Str. 74 - 40219 Düsseldorf
HRB Düsseldorf 39841 - Geschäftsführer: Thilo Salmon, Tim Mois
Steuernummer: 106/5724/7147, Umsatzsteuer-ID: DE219349391

www.sipgate.de - www.sipgate.co.uk
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20190220/930fd302/attachment.html>

More information about the asterisk-users mailing list