SOLVED Trouble shooting Anveo Direct tutorial set up...

[Robert.Thompson]

Hello:
I have followed this tutorial: http://nerdvittles.com/?p=5680 The SIPaholics Dream.

I stopped at the point:
"Now you’re ready to place your first call, or you can call the number shown above to try out our demo system using Anveo. Ignore the + symbol when dialing calls. It’s not necessary."

I called my Anveo Direct but just get a busy signal.

Can anyone suggest where I should be looking to trouble shoot this problem - PIAF or Anveo Direct?

Thanks,

 

[Robert.Thompson]

Notes:

1. PIAF is running on a Digital Ocean server
2. There are no records in the PIAF CDR report.

 

[Robert.Thompson]

Could it be this:
Step #2: Now access your hardware-based firewall and map incoming UDP port 5060 traffic to the IP address of your PBX in a Flash server. The exact steps vary slightly depending upon the type of router you have. Look for a tab that deals with redirecting Internet traffic through your router to destination IP addresses.

How do I do this on a Digital Ocean server? Do I need to do this at all?

 

[Robert.Thompson]

Port 5060 info:
sudo netstat -plunt
<snip>
udp 0 0 0.0.0.0:5060 0.0.0.0:* 21815/asterisk
<snip>

So, I quess this part is OK.

Also, when I do: iptables -nL, all the Anveo IP's are listed.

 

[Robert.Thompson]

I did: vi /etc/asterisk/extensions_custom.conf and got the following result:

E325: ATTENTION
Found a swap file by the name "/etc/asterisk/.extensions_custom.conf.swp"
owned by: asterisk dated: Thu Aug 13 12:42:05 2015
file name: /etc/asterisk/extensions_custom.conf
modified: YES
user name: root host name: uPBX
process ID: 19164
While opening file "/etc/asterisk/extensions_custom.conf"
dated: Thu Apr 9 09:52:26 2015
(1) Another program may be editing the same file. If this is the case,
be careful not to end up with two different instances of the same
file when making changes. Quit, or continue with caution.
(2) An edit session for this file crashed.
If this is the case, use ":recover" or "vim -r /etc/asterisk/extensions_custom.conf"
to recover the changes (see ":help recovery").
If you did this already, delete the swap file "/etc/asterisk/.extensions_custom.conf.swp"
to avoid this message.
Swap file "/etc/asterisk/.extensions_custom.conf.swp" already exists!
[O]pen Read-Only, (E)dit anyway, (R)ecover, (D)elete it, (Q)uit, (A)bort:

Does anyone know what I should do?

 

[Robert.Thompson]

Recovered : /etc/asterisk/extensions_custom.conf
Deleted: /etc/asterisk/.extensions_custom.conf.swp

So I guess that part of the problem is resolved.

The following is happily living in /etc/asterisk/extensions_custom.conf:

[from-anveo]
exten => _.,1,Ringing
exten => _.,n,Goto(from-trunk,${SIP_HEADER(X-anveo-e164)},1)

 

[Robert.Thompson]

Under "Edit SIP Trunk" for each of the 5 Anveo entries, do I need to fill in "Register String"?
The tutorial seems to say nothing about this so I left it blank.

"There is no registration facility with Anveo Direct. Incoming calls to your DID are routed to SIP URIs of your choice."

 

[Robert.Thompson]

Anyone???

Is there some other info that might help?

 

[briankelly63]

No reg string needed


example
Peer details:

host=67.212.84.21
type=friend
insecure=port,invite
context=from-trunk
canreinvite=yes
qualify=no
disallow=all
allow=ulaw

 

[Robert.Thompson]

No reg string needed


example
Peer details:

host=67.212.84.21
type=friend
insecure=port,invite
context=from-trunk
canreinvite=yes
qualify=no
disallow=all
allow=ulaw

The peer details in the tutorial are:

type=peer
trustrpid=yes
sendrpid=yes
port=5060
insecure=port.invite
host=50.22.101.14
context=from-trunk
canreinvite=yes
qualify=yes

Are you recommending that I change them to yours?

Thanks,

 

[atsak]

/var/log/asterisk/full - sanitize IP's and post a call log for more help . . .

 

[Robert.Thompson]

/var/log/asterisk/full - sanitize IP's and post a call log for more help . . .

Sorry atask, I am not sure that I understand what you want me to do.

I did:

root@uPBX:/# /var/log/asterisk/full
-bash: /var/log/asterisk/full: Permission denied
root@uPBX:/#

There are no records in CDR Report.

Are you asking for something different?

Is this what you want:
[2015-08-14 20:40:01] NOTICE[21838] chan_iax2.c: Restricting registration for peer 'iax-fax2' to 60 seconds (requested 300)
[2015-08-14 20:40:03] NOTICE[21836] chan_iax2.c: Restricting registration for peer 'iax-fax0' to 60 seconds (requested 300)
[2015-08-14 20:40:14] NOTICE[21851] chan_sip.c: -- Registration for '[email protected]' timed out, trying again (Attempt #4629)
[2015-08-14 20:40:14] NOTICE[21851] chan_sip.c: Failed to authenticate on REGISTER to '[email protected]' (Tries 3)
[2015-08-14 20:40:34] NOTICE[21851] chan_sip.c: -- Registration for '[email protected]' timed out, trying again (Attempt #4633)
[2015-08-14 20:40:34] NOTICE[21851] chan_sip.c: Failed to authenticate on REGISTER to '[email protected]' (Tries 3)
[2015-08-14 20:40:54] NOTICE[21851] chan_sip.c: -- Registration for '[email protected]' timed out, trying again (Attempt #4637)
[2015-08-14 20:40:54] NOTICE[21851] chan_sip.c: Failed to authenticate on REGISTER to '[email protected]' (Tries 3)
[2015-08-14 20:40:56] NOTICE[21838] chan_iax2.c: Restricting registration for peer 'iax-fax1' to 60 seconds (requested 300)
[2015-08-14 20:40:56] NOTICE[21840] chan_iax2.c: Restricting registration for peer 'iax-fax3' to 60 seconds (requested 300)
[2015-08-14 20:40:56] NOTICE[21835] chan_iax2.c: Restricting registration for peer 'iax-fax2' to 60 seconds (requested 300)
[2015-08-14 20:40:58] NOTICE[21842] chan_iax2.c: Restricting registration for peer 'iax-fax0' to 60 seconds (requested 300)

 

[Robert.Thompson]

It is now working!

I noticed, in the above, that "Registration for '[email protected]' timed out, trying again (Attempt #4637)" was listed.

Registration for '[email protected]' timed out, trying again (Attempt #4637) was for an Anveo trunk that I was no longer using - I did not think that leaving it in place would matter - I guess that it does!

Should I be doing something to "sanitize" my IP's? I don't know what that means.

Thanks,

 

[atsak]

No you're fine - what that means is that you replace any IP addresses with x.x.x.x that divulge anything about your internal network. Nothing above is a security issue (well, really, since you don't use the account anymore. If you did, you'll want to remove the numbers before Sip.ca.anveo.com).

 

[Robert.Thompson]

No you're fine - what that means is that you replace any IP addresses with x.x.x.x that divulge anything about your internal network. Nothing above is a security issue (well, really, since you don't use the account anymore. If you did, you'll want to remove the numbers before Sip.ca.anveo.com).

Thank you!

I was able to set up outgoing calls as well, thanks to the great tutorial.