SOLVED Anveo Direct - Updated IP address and (Context?)

[CTSFO]

Hey All,

I have had a ton of weird issues with Anveo and have gone back to basics. As other members have said, they have had change around on their IP addresses.

In my logs I see:

[2021-01-08 17:13:24] VERBOSE[15837][C-00000026] pbx.c: Executing [s@from-sip-external:7] Log("SIP/169.48.232.158-00000039", "WARNING,"Rejecting unknown SIP connection from 169.48.232.158"") in new stack

So I cloned one of the other Anveo trunks and used this IP address shown in the logs. And I have also found that you need to have:
context=from-trunk
(I don't know why this works and if there is any security risks. Hope someone more knowledgeable can chime in here...)

rather than:
context=from-anveo


Once I did this, everything has sprung to life.

@wardmundy For Anveo, please can you update the inbound trunks to be the following four:
67.212.84.21
176.9.39.206
169.48.232.158
72.9.149.25


Source:

Anveo Direct: FAQ

Anveo Direct Service FAQ.

anveodirect.com

Hope this helps!

 

[wardmundy]

@CTSFO: All four of those IP addresses already are in the Incredible PBX 2021 whitelist.

The from-anveo context needs to be added to /etc/asterisk/extensions_custom.conf AT THE BOTTOM OF THE FILE. Then use it in the anveo trunk settings, not from-trunk.

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

It is used to identify the incoming DID from Anveo. Then simply add an inbound route with your 10-digit Anveo DID.

 

[CTSFO]

Ah - Cool.

Thank you!

 

[jerrm]

I don't know of any reason to bother with the "from-anveo" context.

I assume it was needed at one point, but I go back 5+ years at least to FreePBX12 with Anveo-Direct and have never used it.

 

[kenn10]

I don't know of any reason to bother with the "from-anveo" context.

I assume it was needed at one point, but I go back 5+ years at least to FreePBX12 with Anveo-Direct and have never used it.

I agree. I just use from-pstn-e164-us and it works just fine. I set the Anveo Direct DID to send it to me in e164 format.

 

[thecyber.ninja]

@CTSFO: All four of those IP addresses already are in the Incredible PBX 2021 whitelist.

The from-anveo context needs to be added to /etc/asterisk/extensions_custom.conf AT THE BOTTOM OF THE FILE. Then use it in the anveo trunk settings, not from-trunk.

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

It is used to identify the incoming DID from Anveo. Then simply add an inbound route with your 10-digit Anveo DID.

SOOO I am having the same problem, but I have added the following in accordance with your guides:

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

@wardmundy your guides say add your 11 digit anveo direct DID to the inbound route, but above you say 10, neither worked for me

I followed your latest Debian guide ...

Relevant, I hope logs below:

367[2021-01-16 19:39:17] VERBOSE[1733][C-00000001] netsock2.c: Using SIP RTP TOS bits 184
32368[2021-01-16 19:39:17] VERBOSE[1733][C-00000001] netsock2.c: Using SIP RTP CoS mark 5
32369[2021-01-16 19:39:17] VERBOSE[4418][C-00000001] pbx.c: Executing [14431231234@from-sip-external:1] NoOp("SIP/169.48.232.158-00000000", "Received incoming SIP connection from unknown peer to 14431231234") in new stack
32370[2021-01-16 19:39:17] VERBOSE[4418][C-00000001] pbx.c: Executing [14431231234@from-sip-external:2] Set("SIP/169.48.232.158-00000000", "DID=14435954242") in new stack
32371[2021-01-16 19:39:17] VERBOSE[4418][C-00000001] pbx.c: Executing [14431231234@from-sip-external:3] Goto("SIP/169.48.232.158-00000000", "s,1") in new stack
32372[2021-01-16 19:39:17] VERBOSE[4418][C-00000001] pbx_builtins.c: Goto (from-sip-external,s,1)
32373[2021-01-16 19:39:17] VERBOSE[4418][C-00000001] pbx.c: Executing [s@from-sip-external:1] GotoIf("SIP/169.48.232.158-00000000", "1?setlanguage:checkanon") in new stack
32374[2021-01-16 19:39:17] VERBOSE[4418][C-00000001] pbx_builtins.c: Goto (from-sip-external,s,2)
32375[2021-01-16 19:39:17] VERBOSE[4418][C-00000001] pbx.c: Executing [s@from-sip-external:2] Set("SIP/169.48.232.158-00000000", "CHANNEL(language)=en") in new stack
32376[2021-01-16 19:39:17] VERBOSE[4418][C-00000001] pbx.c: Executing [s@from-sip-external:3] GotoIf("SIP/169.48.232.158-00000000", "1?noanonymous") in new stack
32377[2021-01-16 19:39:17] VERBOSE[4418][C-00000001] pbx_builtins.c: Goto (from-sip-external,s,5)
32378[2021-01-16 19:39:17] VERBOSE[4418][C-00000001] pbx.c: Executing [s@from-sip-external:5] Set("SIP/169.48.232.158-00000000", "TIMEOUT(absolute)=15") in new stack
32379[2021-01-16 19:39:17] VERBOSE[4418][C-00000001] func_timeout.c: Channel will hangup at 2021-01-16 19:39:32.148 EST.
32380[2021-01-16 19:39:17] VERBOSE[4418][C-00000001] pbx.c: Executing [s@from-sip-external:6] Set("SIP/169.48.232.158-00000000", "receveip=recvip") in new stack
32381[2021-01-16 19:39:17] VERBOSE[4418][C-00000001] pbx.c: Executing [s@from-sip-external:7] Log("SIP/169.48.232.158-00000000", "WARNING,"Rejecting unknown SIP connection from 169.48.232.158"") in new stack
32382[2021-01-16 19:39:17] WARNING[4418][C-00000001] Ext. s: "Rejecting unknown SIP connection from 169.48.232.158"
32383[2021-01-16 19:39:17] VERBOSE[4418][C-00000001] pbx.c: Executing [s@from-sip-external:8] Answer("SIP/169.48.232.158-00000000", "") in new stack
32384[2021-01-16 19:39:17] VERBOSE[4418][C-00000001] pbx.c: Executing [s@from-sip-external:9] Wait("SIP/169.48.232.158-00000000", "2") in new stack
32385[2021-01-16 19:39:19] VERBOSE[4418][C-00000001] pbx.c: Executing [s@from-sip-external:10] Playback("SIP/169.48.232.158-00000000", "ss-noservice") in new stack
32386[2021-01-16 19:39:19] VERBOSE[4418][C-00000001] file.c: <SIP/169.48.232.158-00000000> Playing 'ss-noservice.ulaw' (language 'en')
32387[2021-01-16 19:39:24] VERBOSE[4418][C-00000001] pbx.c: Executing [h@from-sip-external:1] Hangup("SIP/169.48.232.158-00000000", "") in new stack
32388[2021-01-16 19:39:24] VERBOSE[4418][C-00000001] pbx.c: Spawn extension (from-sip-external, h, 1) exited non-zero on 'SIP/169.48.232.158-00000000'

Any ideas on how to fix?

Thanks!

 

[kenn10]

Anveo is clearly sending you eleven digits for the incoming DID number. Just look at my post #5 above. Set your trunk context to from-pstn-e164-us instead of from-anveo. Save the change and reload the configuration and it should just work. Your inbound route should have the 11-digit DID number shown (14431231234 in your example above.)

Also, your system acts like the latest Anveo Direct IP address is not whitelisted on your system. Have you logged out of the Linux command line and logged back in? The auto-update for IncrediblePBX should run and add the new IP addresses to the whitelist. If you have the ports set correctly on the Anveo site to send you the call, it should not be saying the call is from sip-external. It should show the call coming from the Anveo trunk.

On the Anveo portal, just set your inbound settings like below. I don't do anything but point it at my servers and the port number. Adjust the port number according to whether you are using PJSIP or chan_SIP and your local port numbers.


.

 

[kenn10]

There is a great deal of discussion about Anveo in this thread. I go into minute detail on how to set up a single PJSIP trunk that will handle everything on one trunk instead of using the old chan_sip trunks. My posts start at message #10 on that topic.

 

[thecyber.ninja]

Thanks for the suggestions... I ended up fixing the problem.

As mentioned above, anveo changed one of their ip's from 50.22.102.242 to 169.48.232.158

The recent tutorial I followed had the "Anveo-4" trunk with the old IP. I updated the IP and all is well.

My box is up to date, so probably a problem others will face as well...

 

[krzykat]

Yes, according to their site:

You need to allow the following IP addresses to reach your network:
67.212.84.21 - SIP Signaling
176.9.39.206 - SIP Signaling
169.48.232.158 - SIP Signaling
72.9.149.25 - SIP Signaling

I had the first 2, but the last 2 I did not. Instead I had two IP's listed as:
50.22.101.14 and 50.22.102.242 ... seems these are both dead replaced with the 169.48.232.158 and 72.9.149.25

Now I must update and PBX that has inbound DID's from Anveo-Direct

 

[thecyber.ninja]

I don't mean to be a broken record, but I just did a fresh install on Debian 10, ssh'd into the box to force all the updates, particularly for the:
"Checking for updateDEB3. INSTALLED: Anveo Direct IP address update"
and the anveo-4 trunk still shows the wrong IP address. Seems to me as if updateDEB3 did not work as intended...