Displaying 7 results from an estimated 7 matches for "_sips".
Did you mean:
_sip
2020 Sep 30
4
some domains resolving issues
...for target 'iptel.org'
res_pjsip/pjsip_resolver.c:177 sip_resolve_add: [0x7f4e740564e8] Added
target 'iptel.org' with record type '35', transport 'Unspecified', and
port '0'
res_pjsip/pjsip_resolver.c:177 sip_resolve_add: [0x7f4e740564e8] Added
target '_sips._tcp.iptel.org' with record type '33', transport 'TLS',
and port '5061'
res_pjsip/pjsip_resolver.c:177 sip_resolve_add: [0x7f4e740564e8] Added
target '_sip._tcp.iptel.org' with record type '33', transport 'TCP', and
port '5060'
res_pjsi...
2015 Mar 03
0
TLS, SRTP, Asterisk11 and Snom870s
...or which services.
>
> We have such records in our DNS zone. They look like this:
>
> ;# Configure sip/sips service records (VOIP)
> ;HOST TTL CLASS TYPE ORDER PREF FLAGS SERVICE REGEXP REPLACEMENT
>
> 300 IN NAPTR 50 50 "s" "SIPS+D2T" "" _sips._tcp.harte-lyne.ca.
>
> 300 IN NAPTR 90 50 "s" "SIP+D2T" "" _sip._tcp.harte-lyne.ca.
>
> 300 IN NAPTR 100 50 "s" "SIP+D2U" "" _sip._udp.harte-lyne.ca.
>
> ;HOST TTL CLASS TYPE ORDER PREF PORT TARGET
>
>...
2015 Mar 03
6
TLS, SRTP, Asterisk11 and Snom870s
...ports the Snom will
listen on for which services.
We have such records in our DNS zone. They look like this:
;# Configure sip/sips service records (VOIP)
;HOST TTL CLASS TYPE ORDER PREF FLAGS SERVICE REGEXP REPLACEMENT
300 IN NAPTR 50 50 "s" "SIPS+D2T" "" _sips._tcp.harte-lyne.ca.
300 IN NAPTR 90 50 "s" "SIP+D2T" "" _sip._tcp.harte-lyne.ca.
300 IN NAPTR 100 50 "s" "SIP+D2U" "" _sip._udp.harte-lyne.ca.
;HOST TTL CLASS TYPE ORDER PREF PORT TARGET
_sips._tcp.harte-lyne.ca. 300 IN...
2020 Aug 27
2
PJSIP trunk is down when DNS was not available during the Asterisk start.
...m'
[Aug 27 07:51:36] DEBUG[595] res_pjsip/pjsip_resolver.c: [0x7f75282fe7f8]
Added target 'rpi6.in.xorcom.com' with record type '35', transport
'Unspecified', and port '0'
[Aug 27 07:51:36] DEBUG[595] res_pjsip/pjsip_resolver.c: [0x7f75282fe7f8]
Added target '_sips._tcp.rpi6.in.xorcom.com' with record type '33',
transport 'TLS', and port '5061'
[Aug 27 07:51:36] DEBUG[595] res_pjsip/pjsip_resolver.c: [0x7f75282fe7f8]
Added target '_sip._tcp.rpi6.in.xorcom.com' with record type '33',
transport 'TCP', and port...
2020 Aug 27
0
PJSIP trunk is down when DNS was not available during the Asterisk start.
...:36] DEBUG[595] res_pjsip/pjsip_resolver.c: [0x7f75282fe7f8]
> Added target 'rpi6.in.xorcom.com' with record type '35', transport
> 'Unspecified', and port '0'
> [Aug 27 07:51:36] DEBUG[595] res_pjsip/pjsip_resolver.c: [0x7f75282fe7f8]
> Added target '_sips._tcp.rpi6.in.xorcom.com' with record type '33',
> transport 'TLS', and port '5061'
> [Aug 27 07:51:36] DEBUG[595] res_pjsip/pjsip_resolver.c: [0x7f75282fe7f8]
> Added target '_sip._tcp.rpi6.in.xorcom.com' with record type '33',
> transport ...
2020 Aug 27
2
PJSIP trunk is down when DNS was not available during the Asterisk start.
...res_pjsip/pjsip_resolver.c: [0x7f75282fe7f8]
>> Added target 'rpi6.in.xorcom.com' with record type '35', transport
>> 'Unspecified', and port '0'
>> [Aug 27 07:51:36] DEBUG[595] res_pjsip/pjsip_resolver.c: [0x7f75282fe7f8]
>> Added target '_sips._tcp.rpi6.in.xorcom.com' with record type '33',
>> transport 'TLS', and port '5061'
>> [Aug 27 07:51:36] DEBUG[595] res_pjsip/pjsip_resolver.c: [0x7f75282fe7f8]
>> Added target '_sip._tcp.rpi6.in.xorcom.com' with record type '33',
>&g...
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