VOIP Tech Chat → [Anveo Direct] Launches Innovative Call Termination Service

I was hoping that someone would take a look at the HELP TAB and will share it :-) I guess not many users read HELP section these days :-)

Where is Innovations ?
We did not invent LCR, we did not invent multi-carrier model, we did not invent NO PROXY MEDIA...
But the real innovation is in the HELP Section :-)

On more serious note Innovations are:
1) Ability to control LCR model not only from the portal but also from special SIP Headers

I am sure each service provider had cases where a simple mistake in the rate table results in huge loses when someone sends calls to exploit that error. Anveo Direct can help service providers by supporting a special set of SIP INVITE Header to control Anveo Direct LCR Model ( like setting CAP to the rate you charge your end users and the call will not go though it there is no route found with acceptable call rate :)

2) REALTIME call details notification via SIP MESSAGE or HTTP CALLBACK as the call progresses (which includes which carrier is used, calling rate, call duration, custom data etc).

----------

COPY/PASTE from Anveo Direct HELP tab

Anveo Direct Call Termination service provides access to multiple carriers with various rates and service levels. Anveo Direct customers can take advantage of using flexible multi-carrier options to route their calls through carriers (and even with failover) using flexible and customizable LCR model to achieve desired quality/price ration with excellent reliability.
Anveo Direct LCR provides flexible LCR model which can be configured through the portal or via X-ANVEO-LCR SIP Header in SIP INVITE

How Anveo LCR works
Anveo LCR configuration includes PREFIX, IP Addresses, Rate Cap, Carrier routes, Selection Depth and Route Call/Failover Order.

Here is how Anveo LCR works. When a call is received Anveo will perform the following steps:
1. - locate Anveo Call Termination Trunk based on IP address from which the call was received and Prefix
2. - Select Carrier Routes configured for the Trunk with call rates within Rate Cap
3. - Sort Carrier Routes based on the rate (lowest first)
4. - Keep top N results from the sorted list of Carrier Routes
5. - re-sort the list of Carrier Routes based on the option configured (cost, or random or service tier order)
6. - Send the call to the first route
7. - If the call fails then taiolver to the next route etc.
SIP Invite and X-ANVEO-LCR header
In addition to the LCR model configuration from the portal it is also possible to send SIP Invite to Anveo and dynamically configure LCR model by including a specially formatted text in the X-ANVEO-LCR SIP header.
The format for X-ANVEO-LCR string is as follows:

cap=N.NNNN|routes=id1,id3,id4|depth=N|order=ORDERTYPE

where
• cap is a rate cap. For example: 0.01
• routes is a list of carrier routes (their id) separated by comma. For example: carriers=1,2,3,4
• depth is a the number of carrier routes to keep for the call routing and failover: For example: depth=3
• order - is the call order either 'cost' or 'random' or 'tier'. For example: order=random

cap,routes,depth,order are optional parameners and you can only specify those needed for a particular call. For example; you can only specify cap=N.NNN where N.NNN is your target rate.

Realtime Call Details Notifications via SIP MESSAGE or HTTP CALLBACKS
Anveo Direct can automatically notify your SIP server which carrier route is used and the call rate for the connected call as well as call progress status and when the call ends the total amount deducted as well as call duration in seconds.

X-ANVEO-LCR-NOTIFICATION-TYPE SIP Header
To activate realtime in-call notification X-ANVEO-LCR-NOTIFICATION-TYPE SIP INVITE header needs to be set either to 'SIP' (for SIP MESSAGE) or to 'HTTP'.
When X-ANVEO-LCR-NOTIFICATION-TYPE is set to HTTP you need to also set X-ANVEO-LCR-NOTIFICATION-URL SIP INVITE header to URL on your web server where you want to receive realtime Call Details information.
Example:
X-ANVEO-LCR-NOTIFICATION-TYPE: HTTP
X-ANVEO-LCR-NOTIFICATION-URL: »www.myserver.com/httpcal ··· back.php

X-ANVEO-LCR-NOTIFICATION-MEMO SIP Header
When Anveo sends realtime Call Details notifications it can include in the data any custom information which you set in X-ANVEO-LCR-NOTIFICATION-MEMO SIP INVITE header. For example; it could some kind of CALL KEY within your system, userid or anything else.
Example:
X-ANVEO-LCR-NOTIFICATION-MEMO: 123456789

X-ANVEO-LCR-NOTIFICATION-EVENTS SIP Header
You can select when Anveo will send realtime Call Details information as call progresses (ALL, CONNECT, END). To set that information you need to use X-ANVEO-LCR-NOTIFICATION-EVENTS header and set it to either: ALL (for all notifications), CONNECT (only when Call was answered), END (only when call ended)
Example:
X-ANVEO-LCR-NOTIFICATION-EVENTS: ALL

Realtime Call Details Notifications
After all notifications fields are configured Anveo will send the following call details to either HTTP URL provided or as SIP MESSAGE back to SIP UA originating the call:


Payload={'event.type': 'CALL.STATE','event.name':'EVENTNAME', 'notification-memo': YOURCUSTOMMEMOPROVIDED,'rate.jurisdiction':CALLJURISDICTION,'carrier.id':ROUTECARRIERID,'rate':ANVEOCALLRATE,'duration':CALLDURATIONSECONDS}

where
• EVENTNAME - either CONNECT when the call is answered, END when the call ended
• YOURCUSTOMMEMOPROVIDED - a value from X-ANVEO-LCR-NOTIFICATION-MEMO
• CALLJURISDICTION - either INTER or INTRA which identifis a call jurisdiction
• ROUTECARRIERID - Carrier/RouteID which is handling the call
• ANVEOCALLRATE - Anveo Direct Calling rate for the call
• CALLDURATIONSECONDS - Call Duration in seconds

Payload string will be either sent to Notification URL or as SIP MESSAGE body.

----------
So much for Anveo Direct reselling LCR services from some mysterious company LOL

If that's the case you need to have a serious chat with your webmaster.

I'm sure you can recognize what provider the screenshots (last six digits replaced with X for privacy reasons) below are from.