asterisk users - May 2023 - Problems with inbound connection and registering phone

I have two problems. The first is that when I dial my number from a 
phone on the Internet or any phone outside my LAN, Asterisk does not 
respond in any way, which means somehow my system is not picking up the 
fact that there's an incoming call to it.


The second problem is that I thought I'd try an internal phone to see if 
I could get the hello-world stuff working at the least. I thought I'd 
try Zoiper, but none of the download buttons at 
https://www.zoiper.com/en/voip-softphone/download/current did anything 
when clicked, so I set up a spare line on a Yealink TA33 phone that is 
connected to another much much older Asterisk implementation running a 
piece of amateur radio gear called Allstar. The version of Asterisk used 
in the Allstar project is ancient--like 1.4 or 1.6--and the 
configuration syntax and options are quite different, so I didn't get 
lulled into thinking I'd just clone that configuration on my newer 
Asterisk implementation.


The "Definitive Guide" shows everything about adding phones as SQL 
statements, so I made some educated guesses as to what to put into 
pjsip.conf. Something's obviously wrong because the phone won't 
authenticate (see below).


Here's how I set it up in pjsip.


[yealink]
transport=udp
type=auth
auth_type=userpass
username=Steve
password=Steve

[yealink]
type = endpoint
transport = transport-udp
context = phones
disallow = all
allow = ulaw
; allow=g729                 ; uncomment if you support g729
auth = yealink
aors = yealink


Here's how I set it up in extensions:


[phones]
exten => 101,1,Dial(PJSIP/yealink)

Here's the error I get on the Asterisk console:


[May 23 13:42:56] NOTICE[45189]: res_pjsip/pjsip_distributor.c:676 
log_failed_request: Request 'REGISTER' from '"Steve" 
<sip:Steve at 192.168.1.185>' failed for '192.168.1.228:5060'
(callid:
0_1554187534 at 192.168.1.228) - Failed to authenticate


What did I omit?

On Tue, 23 May 2023, Steve Matzura wrote:
> ...when I dial my number from a phone on the Internet or any phone 
> outside my LAN, Asterisk does not respond in any way, which means 
> somehow my system is not picking up the fact that there's an incoming 
> call to it.
Or that you are not receiving any packets.

Enabling SIP debugging in Asterisk can yield clues.

`sudo tcpdump -i any -s 0 -v port 5060` can yield more clues. Note that 
tcpdump sees packets before iptables and Asterisk sees packets after 
iptables.

If you're getting packets, sngrep and wireshark can yield even more clues.

-- 
Thanks in advance,
-------------------------------------------------------------------------
Steve Edwards       sedwards at sedwards.com      Voice: +1-760-468-3867 PST
             https://www.linkedin.com/in/steve-edwards-4244281

On Tue, 23 May 2023, Steve Matzura wrote:
> The "Definitive Guide" shows everything about adding phones as
SQL
> statements...
I'd look for another guide.

-- 
Thanks in advance,
-------------------------------------------------------------------------
Steve Edwards       sedwards at sedwards.com      Voice: +1-760-468-3867 PST
             https://www.linkedin.com/in/steve-edwards-4244281

On Tue, May 23, 2023 at 02:24:02PM -0400, Steve Matzura
wrote:
> I have two problems. The first is that when I dial my number from a phone
on
> the Internet or any phone outside my LAN, Asterisk does not respond in any
> way, which means somehow my system is not picking up the fact that
there's
> an incoming call to it.
> 
> 
> The second problem is that I thought I'd try an internal phone to see
if I
> could get the hello-world stuff working at the least. I thought I'd try
> Zoiper, but none of the download buttons at
> https://www.zoiper.com/en/voip-softphone/download/current did anything when
> clicked, so I set up a spare line on a Yealink TA33 phone that is connected
> to another much much older Asterisk implementation running a piece of
> amateur radio gear called Allstar. The version of Asterisk used in the
> Allstar project is ancient--like 1.4 or 1.6--and the configuration syntax
> and options are quite different, so I didn't get lulled into thinking
I'd
> just clone that configuration on my newer Asterisk implementation.
> 
> 
> The "Definitive Guide" shows everything about adding phones as
SQL
> statements, so I made some educated guesses as to what to put into
> pjsip.conf. Something's obviously wrong because the phone won't
authenticate
> (see below).
> 
> 
> Here's how I set it up in pjsip.
> 
> 
> [yealink]
> transport=udp
> type=auth
> auth_type=userpass
> username=Steve
> password=Steve
>
[yealink]
type=aor


 
> [yealink]
> type = endpoint
> transport = transport-udp
> context = phones
> disallow = all
> allow = ulaw
> ; allow=g729                 ; uncomment if you support g729
> auth = yealink
> aors = yealink
> 
> 
> Here's how I set it up in extensions:
> 
> 
> [phones]
> exten => 101,1,Dial(PJSIP/yealink)
> 
> Here's the error I get on the Asterisk console:
> 
> 
> [May 23 13:42:56] NOTICE[45189]: res_pjsip/pjsip_distributor.c:676
> log_failed_request: Request 'REGISTER' from '"Steve"
> <sip:Steve at 192.168.1.185>' failed for
'192.168.1.228:5060' (callid:
> 0_1554187534 at 192.168.1.228) - Failed to authenticate
> 
> 
> What did I omit?
> 
> 
> -- 
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> 
> Check out the new Asterisk community forum at:
https://community.asterisk.org/
> 
> New to Asterisk? Start here:
>      https://wiki.asterisk.org/wiki/display/AST/Getting+Started
> 
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
-- 
Henning Follmann           | hfollmann at itcfollmann.com