Here’s my anveodirect configuration using the obi200. This is strictly for outbound calls. Anveodirect does not use auth user/password, instead auth is done using an IP whitelist. If your ip changes often you will have issues.

Under ITSP Profile/SPx/General, digit map is as follows
(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|*xx|*xxx|011xx.|xx.|(Mipd)|[^*#]@@.)

Under ITSP Profile/SPx/Sip, X_PublicIPAddress should be your wan ip address. I could not get obi to properly detect mine. It is required for RTP to work correctly. Anveodirect does NOT proxy media. This means inbound media traffic can come from anywhere.

Under ITSP Profile/SPx/RTP, LocalPortMin/Max specifies UDP port range firewall forwards back to the obi device for media purposes. These are configured as a port forward in the firewall settings.

Under Voice Services/SPx/DirectoryNumber, enter the phone number you want to use as outbound CID (including country code - ie 11231231234)

Under Voice Services/SPx/Authusername, enter the number from DirectoryNumber. I haven’t tested, but probably any value will actually work here.

In your firewall’s NAT setting for the obi device, ensure dynamic ports are not enabled. In pfsense it looks like this.

It is important this rule is placed ABOVE other more generalized NAT rules for that SOURCE IP/network (ie /32 rule must be before /24 rule).

Below are pdf screen shots from the pertinent settings. No audio issues, call length as long as necessary. Was initially having issues with calls disconnecting after 15 min. Was related to reinvite not properly configured and dynamic ports breaking NAT.

CID number used should be verified by anveo - https://voice.anveo.com/accountPreferences.asp , CUSTOM CALLERID NUMBERS . Verification is simple. Anveo will call the number specified and ask you to verify a code using an automated call. After verification, outbound calls receive and attestation level of B .

It would be nice not to have to hard code the public ip, but I haven’t figured out how to get that to work and still respect the RTP port range specified. Seems STUN would be the appropriate mechanism to use, but that mangles port numbers. My ISP is mostly static anyway (IP hasn’t changed in years) so mostly a nonissue.

anveo-voice-services.pdf

1MB

anveo-itsp-profile-rtp.pdf

451kB

anveo-itsp-profile-sip.pdf

2MB

anveo-itsp-profile-general.pdf

542kB

Inbound call traffic is still handled via google voice and callcentric. CC has a tutorial for obi config at https://www.callcentric.com/support/device/obihai/obi202 .