[asterisk-dev] pjsip - retry handling - faulty warning message?

George Joseph gjoseph at digium.com
Mon Aug 24 09:32:33 CDT 2020


On Mon, Aug 17, 2020 at 12:51 PM Joshua C. Colp <jcolp at sangoma.com> wrote:

> On Sat, Aug 15, 2020 at 12:25 PM Michael Maier <m1278468 at mailbox.org>
> wrote:
>
>> Hello!
>>
>> I got the following warning in the asterisk log:
>>
>> [2020-08-15 16:16:03] WARNING[14367] res_pjsip_outbound_registration.c:
>> No response received from 'sip:tel.t-online.de' on registration attempt
>> to 'sip:+49... at tel.t-online.de', retrying in '60'
>>
>>
>> What really happened (according pcap trace):
>>
>> Register                        Aug 15, 2020 16:16:03.946677000 CEST
>> Register                        Aug 15, 2020 16:16:03.973710000 CEST    ~
>> 27 ms (Retry)
>> Security agreement required     Aug 15, 2020 16:16:04.066745000 CEST    ~
>> 92 ms
>> ...
>> Ok                              Aug 15, 2020 16:16:04.081487000 CEST    ~
>> 14 ms (finish)
>>
>>
>> (Usual duration of a Register is ~ 22.8 ms)
>>
>> Okay, provider was a bit lazy to answer, but Register has been working
>> fine after one retry 27 ms later. Therefore, I don't understand the
>> warning, especially because the registration timeout is 660s and asterisk
>> starts reregistration 10s before the expiry of the registration - so there
>> wasn't any problem with the Registration de facto. Especially as there
>> couldn't be seen any Retry after 60 s as stated in the log. Maybe the log
>> entry is somewhat hasty?
>>
>
>
Check your timer_t1 setting in pjsip.conf.  That's what would control
pjproject's decision on when to return back to us if there's no response to
a request.  It's also unclear who's doing the retry, us or pjproject.  It's
odd that either one of us would wait only 27ms before retrying a request
though.   As Josh says below, the debug stuff would be needed for further
analysis.




> Without debug level and trace information and such it's hard to say. It
> may be that the security agreement response wasn't counted for some reason
> and confused the code, resulting in the transaction thinking it got no
> response.
>
> --
> Joshua C. Colp
> Asterisk Technical Lead
> Sangoma Technologies
> Check us out at www.sangoma.com and www.asterisk.org
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev



-- 
George Joseph
Asterisk Software Developer
direct/fax +1 256 428 6012
Check us out at www.sangoma.com and www.asterisk.org
[image: image.png]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20200824/731f8b1e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 5142 bytes
Desc: not available
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20200824/731f8b1e/attachment.png>


More information about the asterisk-dev mailing list