Displaying 4 results from an estimated 4 matches for "unsuccessfuli".
Did you mean:
unsuccessful
2020 Aug 27
2
PJSIP trunk is down when DNS was not available during the Asterisk start.
I see that pjsip_resolver.c tries unsuccessfuly to resolve the
hostname each 10 seconds:
[Aug 27 07:51:36] DEBUG[595] res_pjsip.c: 0x7f75282eb150: Wrapper created
[Aug 27 07:51:36] DEBUG[595] res_pjsip.c: 0x7f75282eb150: Set timer to 2000
msec
[Aug 27 07:51:36] DEBUG[595] res_pjsip/pjsip_resolver.c: Performing SIP DNS
resolution of target 'rpi6.in.xorcom.com'
[Aug 27 07:51:36] DEBUG[595]
2020 Aug 27
0
PJSIP trunk is down when DNS was not available during the Asterisk start.
On Thu, Aug 27, 2020 at 8:58 AM Leonid Fainshtein <
leonid.fainshtein at xorcom.com> wrote:
> I see that pjsip_resolver.c tries unsuccessfuly to resolve the
> hostname each 10 seconds:
>
> [Aug 27 07:51:36] DEBUG[595] res_pjsip.c: 0x7f75282eb150: Wrapper created
> [Aug 27 07:51:36] DEBUG[595] res_pjsip.c: 0x7f75282eb150: Set timer to
> 2000 msec
> [Aug 27 07:51:36]
2020 Aug 27
2
PJSIP trunk is down when DNS was not available during the Asterisk start.
I deleted the res_resolver_unbound.so module, and now it works as expected.
So, the problem is related to the 'unbound' resolver?
FYI: I'm using Asterisk 16.2 installed from Debian 10 repository.
Best regards,
Leonid Fainshtein
On Thu, Aug 27, 2020 at 3:01 PM Joshua C. Colp <jcolp at sangoma.com> wrote:
> On Thu, Aug 27, 2020 at 8:58 AM Leonid Fainshtein <
>
2020 Aug 27
2
PJSIP trunk is down when DNS was not available during the Asterisk start.
Hi,
I have Asterisk 16.x with a trunk configured with a hostname in PJSIP AOR.
The registration is not required for this trunk.
I paid attention that Asterisk performs DNS resolving of the hostname that
is configured in the AOR 'contact' parameter only upon the Asterisk start
only.
Thus, if Asterisk is started when the DNS server is unreachable due to the
Internet connection failure then