After update trunk won't register - Unable to retrieve PJSIP transport '0.0.0.0-udp'

trunk
Tags: #<Tag:0x00007ff2f9af8a68>

(Volkswagner) #1

After running module updates, yum update, reboot pjsip trunk does not register.

Here is trunk config:
[anveo]
type=registration
transport=0.0.0.0-udp
outbound_auth=anveo
retry_interval=60
fatal_retry_interval=30
forbidden_retry_interval=30
max_retries=10000
expiration=180
auth_rejection_permanent=no
line=yes
endpoint=anveo
contact_user=actualUserName
server_uri=sip:sip.anveo.com:5010
client_uri=sip:[email protected]:5010

I get:
[2021-07-11 09:58:46] ERROR[5085]: res_pjsip.c:3510 ast_sip_set_tpselector_from_transport_name: Unable to retrieve PJSIP transport ‘0.0.0.0-udp’
[2021-07-11 09:58:46] ERROR[5085]: res_pjsip.c:4350 endpt_send_request: Error 320047 ‘No answer record in the DNS response (PJLIB_UTIL_EDNSNOANSWERREC)’ sending OPTIONS request to endpoint anveo

I found an older post that said get rid of transport in trunk config, but that’s not possible in GUI.
I have transport enabled in pjsip “asterisk settings” (udp - 0.0.0.0 - All = yes).

Trunk is with Anveo.com. I notice when I ping sip.anveo.com I get response from 69.prd1.tms.anveo.com (which appears to have no A-record). I tried changing the register string
to use 69.prd1.tms.anveo.com but no change. I also tried changing the “from-domain” setting to 69.prd1.tms.anveo.com, still no change.

I tried adding the following to /etc/hosts (still no change):
72.9.149.69 69.prd1.tms.anveo.com

Is this an Anveo or Asterisk issue?


(David55) #2

This is incomplete. You haven’t included the type=endpoint, which is probably what is affecting the second error.


(Volkswagner) #3

Thanks @david55

I strictly use the GUI for config. The above was from pjsip.registration.conf.
I’m not sure which file to find the setting “type=”.
I didn’t find the setting “type” in the GUI for the pjsip trunk config.


(David55) #4

You won’t find it in the GUI. Every endpoint has a type=endpoint section and the GUI will automatically generate it.


(Volkswagner) #5

I’m not sure what to do now. I saw a warning that Zulu was disabled and needing an update.
I tried enable and update but it seems to just hang. I tried restarting httpd which took a few minutes.

Apply config was still red in gui. When running apply config it appears to hang and I see this
looping in freepbx.log.

[[email protected] asterisk]# tail -f freepbx.log
[2021-07-11 11:58:02] [freepbx.INFO]: Depreciated Function module_getinfo detected in /var/www/html/admin/modules/cxpanel/functions.inc.php on line 71 [] []
[2021-07-11 11:58:02] [freepbx.INFO]: Depreciated Function module_getinfo detected in /var/www/html/admin/modules/cxpanel/functions.inc.php on line 80 [] []
[2021-07-11 11:58:02] [freepbx.INFO]: Depreciated Function module_getinfo detected in /var/www/html/admin/modules/cxpanel/functions.inc.php on line 80 [] []
[2021-07-11 11:58:03] [freepbx.INFO]: Deprecated way to add Console commands for module api, adding console commands this way can have negative performance impacts. Please use module.xml. See: https://wiki.freepbx.org/display/FOP/Adding+fwconsole+commands [] []
[2021-07-11 11:58:03] [freepbx.INFO]: Deprecated way to add Console commands for module backup, adding console commands this way can have negative performance impacts. Please use module.xml. See: https://wiki.freepbx.org/display/FOP/Adding+fwconsole+commands [] []
[2021-07-11 11:58:03] [freepbx.INFO]: Deprecated way to add Console commands for module iotserver, adding console commands this way can have negative performance impacts. Please use module.xml. See: https://wiki.freepbx.org/display/FOP/Adding+fwconsole+commands [] []
[2021-07-11 11:58:03] [freepbx.INFO]: Deprecated way to add Console commands for module pagingpro, adding console commands this way can have negative performance impacts. Please use module.xml. See: https://wiki.freepbx.org/display/FOP/Adding+fwconsole+commands [] []
[2021-07-11 11:58:03] [freepbx.INFO]: Deprecated way to add Console commands for module queuestats, adding console commands this way can have negative performance impacts. Please use module.xml. See: https://wiki.freepbx.org/display/FOP/Adding+fwconsole+commands [] []
[2021-07-11 11:58:03] [freepbx.INFO]: Deprecated way to add Console commands for module qxact_reports, adding console commands this way can have negative performance impacts. Please use module.xml. See: https://wiki.freepbx.org/display/FOP/Adding+fwconsole+commands [] []
[2021-07-11 11:58:03] [freepbx.INFO]: Deprecated way to add Console commands for module voicemail, adding console commands this way can have negative performance impacts. Please use module.xml. See: https://wiki.freepbx.org/display/FOP/Adding+fwconsole+commands [] []
[2021-07-11 11:58:06] [freepbx.INFO]: Depreciated Function module_getinfo detected in /var/www/html/admin/modules/cxpanel/functions.inc.php on line 71 [] []
[2021-07-11 11:58:06] [freepbx.INFO]: Depreciated Function module_getinfo detected in /var/www/html/admin/modules/cxpanel/functions.inc.php on line 80 [] []
[2021-07-11 11:58:07] [freepbx.INFO]: Deprecated way to add Console commands for module api, adding console commands this way can have negative performance impacts. Please use module.xml. See: https://wiki.freepbx.org/display/FOP/Adding+fwconsole+commands [] []
[2021-07-11 11:58:07] [freepbx.INFO]: Deprecated way to add Console commands for module backup, adding console commands this way can have negative performance impacts. Please use module.xml. See: https://wiki.freepbx.org/display/FOP/Adding+fwconsole+commands [] []
[2021-07-11 11:58:07] [freepbx.INFO]: Deprecated way to add Console commands for module iotserver, adding console commands this way can have negative performance impacts. Please use module.xml. See: https://wiki.freepbx.org/display/FOP/Adding+fwconsole+commands [] []
[2021-07-11 11:58:07] [freepbx.INFO]: Deprecated way to add Console commands for module pagingpro, adding console commands this way can have negative performance impacts. Please use module.xml. See: https://wiki.freepbx.org/display/FOP/Adding+fwconsole+commands [] []
[2021-07-11 11:58:07] [freepbx.INFO]: Deprecated way to add Console commands for module queuestats, adding console commands this way can have negative performance impacts. Please use module.xml. See: https://wiki.freepbx.org/display/FOP/Adding+fwconsole+commands [] []
[2021-07-11 11:58:07] [freepbx.INFO]: Deprecated way to add Console commands for module qxact_reports, adding console commands this way can have negative performance impacts. Please use module.xml. See: https://wiki.freepbx.org/display/FOP/Adding+fwconsole+commands [] []
[2021-07-11 11:58:07] [freepbx.INFO]: Deprecated way to add Console commands for module voicemail, adding console commands this way can have negative performance impacts. Please use module.xml. See: https://wiki.freepbx.org/display/FOP/Adding+fwconsole+commands [] []
[2021-07-11 11:59:02] [freepbx.INFO]: Depreciated Function module_getinfo detected in /var/www/html/admin/modules/cxpanel/functions.inc.php on line 71 [] []
[2021-07-11 11:59:02] [freepbx.INFO]: Depreciated Function module_getinfo detected in /var/www/html/admin/modules/cxpanel/functions.inc.php on line 71 [] []
[2021-07-11 11:59:03] [freepbx.INFO]: Depreciated Function module_getinfo detected in /var/www/html/admin/modules/cxpanel/functions.inc.php on line 80 [] []
[2021-07-11 11:59:03] [freepbx.INFO]: Depreciated Function module_getinfo detected in /var/www/html/admin/modules/cxpanel/functions.inc.php on line 80 [] []
[2021-07-11 11:59:04] [freepbx.INFO]: Deprecated way to add Console commands for module api, adding console commands this way can have negative performance impacts. Please use module.xml. See: https://wiki.freepbx.org/display/FOP/Adding+fwconsole+commands [] []
[2021-07-11 11:59:04] [freepbx.INFO]: Deprecated way to add Console commands for module backup, adding console commands this way can have negative performance impacts. Please use module.xml. See: https://wiki.freepbx.org/display/FOP/Adding+fwconsole+commands [] []
[2021-07-11 11:59:04] [freepbx.INFO]: Deprecated way to add Console commands for module iotserver, adding console commands this way can have negative performance impacts. Please use module.xml. See: https://wiki.freepbx.org/display/FOP/Adding+fwconsole+commands [] []
[2021-07-11 11:59:04] [freepbx.INFO]: Deprecated way to add Console commands for module pagingpro, adding console commands this way can have negative performance impacts. Please use module.xml. See: https://wiki.freepbx.org/display/FOP/Adding+fwconsole+commands [] []
[2021-07-11 11:59:04] [freepbx.INFO]: Deprecated way to add Console commands for module queuestats, adding console commands this way can have negative performance impacts. Please use module.xml. See: https://wiki.freepbx.org/display/FOP/Adding+fwconsole+commands [] []
[2021-07-11 11:59:04] [freepbx.INFO]: Deprecated way to add Console commands for module qxact_reports, adding console commands this way can have negative performance impacts. Please use module.xml. See: https://wiki.freepbx.org/display/FOP/Adding+fwconsole+commands [] []
[2021-07-11 11:59:04] [freepbx.INFO]: Deprecated way to add Console commands for module voicemail, adding console commands this way can have negative performance impacts. Please use module.xml. See: https://wiki.freepbx.org/display/FOP/Adding+fwconsole+commands [] []
[2021-07-11 11:59:05] [freepbx.INFO]: Depreciated Function module_getinfo detected in /var/www/html/admin/modules/cxpanel/functions.inc.php on line 71 [] []
[2021-07-11 11:59:05] [freepbx.INFO]: Depreciated Function module_getinfo detected in /var/www/html/admin/modules/cxpanel/functions.inc.php on line 80 [] []
[2021-07-11 11:59:06] [freepbx.INFO]: Deprecated way to add Console commands for module api, adding console commands this way can have negative performance impacts. Please use module.xml. See: https://wiki.freepbx.org/display/FOP/Adding+fwconsole+commands [] []
[2021-07-11 11:59:06] [freepbx.INFO]: Deprecated way to add Console commands for module backup, adding console commands this way can have negative performance impacts. Please use module.xml. See: https://wiki.freepbx.org/display/FOP/Adding+fwconsole+commands [] []
[2021-07-11 11:59:06] [freepbx.INFO]: Deprecated way to add Console commands for module iotserver, adding console commands this way can have negative performance impacts. Please use module.xml. See: https://wiki.freepbx.org/display/FOP/Adding+fwconsole+commands [] []
[2021-07-11 11:59:06] [freepbx.INFO]: Deprecated way to add Console commands for module pagingpro, adding console commands this way can have negative performance impacts. Please use module.xml. See: https://wiki.freepbx.org/display/FOP/Adding+fwconsole+commands [] []
[2021-07-11 11:59:06] [freepbx.INFO]: Deprecated way to add Console commands for module queuestats, adding console commands this way can have negative performance impacts. Please use module.xml. See: https://wiki.freepbx.org/display/FOP/Adding+fwconsole+commands [] []
[2021-07-11 11:59:06] [freepbx.INFO]: Deprecated way to add Console commands for module qxact_reports, adding console commands this way can have negative performance impacts. Please use module.xml. See: https://wiki.freepbx.org/display/FOP/Adding+fwconsole+commands [] []
[2021-07-11 11:59:06] [freepbx.INFO]: Deprecated way to add Console commands for module voicemail, adding console commands this way can have negative performance impacts. Please use module.xml. See: https://wiki.freepbx.org/display/FOP/Adding+fwconsole+commands [] []

#6

Is your system otherwise running ok? I’ve been seeing this crap in the log every minute for months. I’ve never bothered to track it down, because it only wastes a few hundred MB of disk space.

Regarding Anveo, I don’t know what’s wrong but suggest that you delete the trunk and start over. Just for laughs, I set up an Anveo trunk with just 3 non-default settings:

SIP Server: anveo.com
Username: (10-digit Anveo account number)
Secret: (10-character password generated by Anveo)

and it registers just fine. If yours doesn’t, find out why, instead of taking pot shots at the problem.


(Volkswagner) #7

@david55

I rebooted and I’m able to apply config now.

Yes I posted info from pjsip.registrations.conf.

Here is trunk config in pjsip.endpoints.conf

[anveo]
type=endpoint
transport=0.0.0.0-udp
context=from-pstn
disallow=all
allow=ulaw,alaw,gsm,g726,g722
aors=anveo
send_connected_line=false
language=en
outbound_auth=anveo
from_domain=sip.anveo.com
contact_user=actualUserName
user_eq_phone=no
t38_udptl=no
t38_udptl_ec=none
fax_detect=no
trust_id_inbound=no
t38_udptl_nat=no
direct_media=no
rtp_symmetric=yes
dtmf_mode=auto

If needed here is info from pjsip.auth.conf

[anveo]
type=auth
auth_type=userpass
password=actualPassword
username=actualUserName

#8

What’s in pjsip.registration.conf for anveo?

What goes wrong when it tries to register (401, 403, some other error, no response)?


(Volkswagner) #9

@david55 The pjsip.registrations.conf is:

[anveo]
type=registration
transport=0.0.0.0-udp
outbound_auth=anveo
retry_interval=60
fatal_retry_interval=30
forbidden_retry_interval=30
max_retries=10000
expiration=180
auth_rejection_permanent=no
line=yes
endpoint=anveo
contact_user=actualUserName
server_uri=sip:sip.anveo.com:5010
client_uri=sip:[email protected]:5010 

Hmm, it seems the issue is bigger than just trunk registration. I don’t see any endpoints registered. The logging seems nonexistent.

stuartpbx*CLI> pjsip set logger on
PJSIP Logging enabled
[2021-07-11 13:21:18] ERROR[4466]: res_pjsip.c:3510 ast_sip_set_tpselector_from_transport_name: Unable to retrieve PJSIP transport '0.0.0.0-udp'
[2021-07-11 13:21:18] ERROR[4466]: res_pjsip.c:4350 endpt_send_request: Error 320047 'No answer record in the DNS response (PJLIB_UTIL_EDNSNOANSWERREC)' sending OPTIONS request to endpoint anveo
    stuartpbx*CLI> pjsip show aors
    Aor:  <Aor..............................................>  <MaxContact>
    Contact:  <Aor/ContactUri............................> <Hash....> <Status> <RTT(ms)..>
    #ERROR!
    Aor:  100                                                  1
    Aor:  101                                                  1
    Aor:  102                                                  1
    Aor:  104                                                  1
    Aor:  105                                                  1
    Aor:  107                                                  1
    Aor:  108                                                  1
    Aor:  111                                                  1
    Aor:  120                                                  1
    Aor:  909                                                  1
    Aor:  anveo                                                0
    Contact:  anveo/sip:[email protected]:5010      4acdf5619f Unavail         nan
    Objects found: 11
    [2021-07-11 13:22:18] ERROR[4466]: res_pjsip.c:3510 ast_sip_set_tpselector_from_transport_name: Unable to retrieve PJSIP transport '0.0.0.0-udp'
    [2021-07-11 13:22:18] ERROR[4466]: res_pjsip.c:4350 endpt_send_request: Error 320047 'No answer record in the DNS response (PJLIB_UTIL_EDNSNOANSWERREC)' sending OPTIONS request to endpoint anveo
    stuartpbx*CLI>

(Simon Telephonics) #10

Looks like the transport section might be screwed up. Check in Asterisk SIP Settings and save. Then fwconsole restart.


(Volkswagner) #11

Thanks @billsimon and @david55

I sure had an issue with transport. After the update Asterisk is no longer
allowing “bogus” entries for “local networks”. For some unknown reason,
the IT personnel decided it was a good idea to use 35.1.3.1.0/24 subnet for LAN!

I’ve had that subnet listed as an additional local network for nearly two years.
It is now rejected and causes transport to fail.

 [2021-07-10 12:06:21] ERROR[940] res_pjsip_config_wizard.c: Unable to load config file 'pjsip_wizard.conf'
[2021-07-10 12:06:21] ERROR[940] res_pjsip_config_wizard.c: Unable to load config file 'pjsip_wizard.conf'
[2021-07-10 12:06:21] WARNING[940] acl.c: Invalid IP address: 35.1.3.1.0
[2021-07-10 12:06:21] ERROR[940] config_options.c: Error parsing local_net=35.1.3.1.0/24 at line 21 of /etc/asterisk/pjsip.transports.conf
[2021-07-10 12:06:21] ERROR[940] res_sorcery_config.c: Could not create an object of type 'transport' with id '0.0.0.0-udp' from configuration file 'pjsip.conf'
[2021-07-10 12:06:21] NOTICE[940] res_sorcery_config.c: Retaining existing configuration for object of type 'transport' with id '0.0.0.0-udp'
[2021-07-10 12:06:21] ERROR[940] res_pjsip_config_wizard.c: Unable to load config file 'pjsip_wizard.conf'
[2021-07-10 12:06:21] ERROR[940] res_pjsip_config_wizard.c: Unable to load config file 'pjsip_wizard.conf'
[2021-07-10 12:06:21] NOTICE[940] sorcery.c: Type 'system' is not reloadable, maintaining previous values

After removing the offending entry, transports now load and my IP phones are now registering. I still have the issue with trunk though.

With logger set on this is still the only output I get:

[2021-07-11 15:27:30] WARNING[2608]: res_pjsip_outbound_registration.c:841 schedule_retry: No response received from 'sip:sip.anveo.com:5010' on registration attempt to 'sip:[email protected]:5010', retrying in '60'
`[2021-07-11 15:27:32] ERROR[2608]: res_pjsip.c:4350 endpt_send_request: Error 320047 'No answer record in the DNS response (PJLIB_UTIL_EDNSNOANSWERREC)' sending OPTIONS request to endpoint anveo`

I still don’t know if this is an Asterisk issue or Anveo issue.


#12

Wolverines can bite :wink:


(Volkswagner) #13

I don’t actually see any registration attempts. Perhaps there is something wrong with my
tcpdump command (192.168.35.7 is the Freepbx server IP on eth0)

tcpdump -ni eth0 -s0  -w tcpDump.pcap host 192.168.35.7 and udp

I see all other sip traffic between endpoints on the LAN but nothing going outside the LAN.


#14

Start off with

[2021-07-10 12:06:21] WARNING[940] acl.c: Invalid IP address: 35.1.3.1.0

Inform your IT personnel (or yourself) that 35.1.3.1.0/24 is NOT a valid subnet.

Is your external IP address space within the U.MICH asn (36375) ?

AS      | IP               | BGP Prefix          | CC | Registry | Allocated  | AS Name
36375   | 35.1.3.1         | 35.1.0.0/16         | US | arin     | 1994-04-01 | UMICH-AS-5, US


(Volkswagner) #15

Thanks @dicko

Yes that subnet is public routable (horrid idea).

After rebooting the server, I can now register with Anveo. I’m not sure
if it had already stopped trying due to no response or if it was a different issue.

All is well now.

Thanks again.

They will definitely need to change the subnet to a private range. I think there was only one or two devices that were on that LAN (wiring constraints forced them to use the DATA lan vs VOIP vLAN).

Yeah, that poor choice to use 35.1.3.1.0/24 was made over ten years ago!
I love having that conversation… “but it’s been working fine for over ten years”.
:slight_smile:
Cheers!


(system) closed #16

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.