News:

On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT

Main Menu

Obi110 possible to route incoming call based on called (aka callee) number?

Started by DeanUK, May 08, 2019, 06:24:16 AM

Previous topic - Next topic

DeanUK

Hi folks,

I would like to know if it's possible on an Obi110 to route the call based on the called number, which is also known as the callee number in the Obi Admin guide.

My set up is that I am based in the UK and I'm using two different UK numbers registered to one Sipgate basic UK account (using this account as the UK DID numbers are free). I'm currently forwarding all of these calls to my CallCentic account iNum number, as i'm getting a large number of scam calls on one of these DID numbers, the one that was ported from Talktalk, and I like to use the extensive call treatments available in CC. The other DID number receives no scam calls.

On my Obi 110 the inbound call route is set to:
{>245512345:SP1(883510001112345@sip.inum.net;ui=$1)}

where 245512345 is my Sipgate AuthUserName (using this Oleg method to thwart SIP scanners).

what I would like to do is route one of the DID numbers to a second CallCentric INum, which could have a different set of call treatments. Is this possible?

I'm confused because in the Obi admin guide the number after the ">" is referred to as the Called/Callee number, but in practice this seems to the the AuthUserName. Is there some syntax to use the Called/Callee number instead of the AuthUserName?

I am already 100% sure that the Called/Callee number is passed from Sipgate to the Obi110, because i've just made a call and looked at the Obi syslog, which shows in the SIP invite message:

From: "01234567890" <sip:01234567890@sipgate.co.uk>;tag=as05fc9999
To: <sip:00441987654321@sipgate.co.uk>
Contact: <sip:01234567890@212.9.99.99:5060>
Call-ID: 457b1ecd787cc7be099abac225739999@sipgate.co.uk
CSeq: 103 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces
Content-Type: application/sdp
Content-Length: 437

This does include the Called/callee number which is 00441987654321
The PSTN calling number is 01234567890

(some address anonymisation used)

I should add that in the Obi110 call history, both the Peer Name and the Peer Number appear as the PSTN calling number 01234567890. The Called/callee number is not shown.

I have also searched the forums and found this post, which was inconclusive: http://www.obitalk.com/forum/index.php?topic=5449.0

azrobert

Variable $1 contains the callerid and $2 contains the called/callee number.

To see the called/callee number, temporarily change the inbound call route to:
sp1($2@192.168.1.199)

Use any IP address.
Now call the OBi110 and then look at the Call History.

DeanUK

Thank you for your quick reply.

I just tested this by changing the inbound call route to:
sp1($2@192.168.1.199)

but when I looked at the OBi110 Call History, it did not show the called/callee number. What it showed was:
In left hand column:
Peer Name: 01234567890
Peer Number: 01234567890

In right hand column:
Peer Name:
Peer Number: 245512345@192.168.1.199
(i.e. Peer Name is blank, as it is for all calls I receive, while 245512345@192.168.1.199 replaces the 883510001112345@sip.inum.net which is normally there)

It seems the OBi110 is unable to extract the proper Called/callee number from the SIP Invite message. I'm not sure what to try next.

azrobert


azrobert

Does your call history show you're routing the call to sip.inum.net, but it's not working? I believe there were problems with sip.inum.net. I don't know if these were corrected.

You can route calls to your CC account like this:
{>245512345:SP1(1777xxxxxxx@in.callcentric.com;ui=$1)}

Replace 1777xxxxxxx with your CC account number.

DeanUK

In the Call History the OBi110 shows 245512345 is the called/callee number, but the real called/callee number is 00441987654321, so that's not right. What I am looking for is to pass the number 00441987654321 to CallCentric, where it can be acted on by the call treatments.

Other than that, the inbound call route:
{>245512345:SP1(883510001112345@sip.inum.net;ui=$1)}

is working fine. It's been working since I started using it about two years ago.

I did just try using
{>245512345:SP1(1777xxxxxxx@in.callcentric.com;ui=$1)}

and this works perfectly well too - with the same result that the proper called/callee number is not shown in the Call History. The Peer Number is now shown as 1777xxxxxxx@in.callcentric.com in the right hand column.