Passing CID

(1/2) > >>

MurrayB:
I have a number of Obi 110. When a unit is forwarding a call, incoming on SP1 outgoing on SP2 both on voip.ms, is there a way to pass the incoming CID rather than the forwarding Obi name?

I also have a couple set up for simultaneous ring in two locations via the ObiTalk network again is there a way to set up the outgoing Obi110 to pass the incoming CID via voip.ms rather than the forwarding Obi name appearing on the second Obi110?

Thanks!

azrobert:
How and who are you forwarding the call to?
If it's by using the ITSP A X_InboundCallRoute to a VOIP.ms user change it to:
{ph,sp2(Their_Number@sip.voip.ms;ui=$1)}

I got the URI format here:
http://wiki.voip.ms/article/SIP_URI

Calls routed over OBiTalk should pass CallerID.
How are you doing it?

MurrayB:
Hi Azrobert - Thanks for the quick response.

The call forwarding is via *72 it goes to my cell phone on unanswered or busy showing the Obi110 CID. The use of the star code allows me to turn forwarding on/off at will.

The incoming call dual ring between two different Obi110 is via ObiTalk and is accomplished by an inbound call route from RonR. The CID shows the name of the other Obi110 whichever direction.

Thanks again!

azrobert:
When you use a service provider to forward a call by placing a new outbound call, the callerid will be the service provider's and not the original callerid.
If you can forward the call directly to the person via SIP URI the original callerid can be passed.

I assume you have CallForwardUncondionalNumber set to a number like 18005551212.
This will use the service provider on the primary line to make a new call to forward the number and the callerid of your service provider will be used.

Does the person you're forwarding to have an account at a SIP service provider?
If yes, change CallForwardUncondionalNumber to something like:
sp2(Their_Number@sip.voip.ms;ui=$1)

$1 is a variable that contains the inbound callerid.

Are you using an inbound route like the following to forward over OBiTalk?
{ph,pp(ob200123456)}

Then on the other OBi are you sending the call to the phone port?

When I did this in the past the original callerid was used.

MurrayB:
Hi Azrobert

The call forwarding is purely to my cell phone: voip.ms to AT&T so that answers that. But you provided good information and food for thought how to route the forwarded calls. I wonder if I set up another SIP account on Voip.ms forward via *72 to that account per your string and via voip.ms to the AT&T cell phone. I am not sure if the $1 variable is the incoming CID.

The other condition to a second Obi via ObiTalk I forgot was called forking. I have not used this service since I changed to Voip.ms from Verizon. I plan to make use of it again. I will have to change the inbound call route on the SP. The line port which is no longer active inbound call route: {ph,pp1(obxxxxxxxxx)}. This provided the name of the Obi on the other end of the forked call.

Navigation

[0] Message Index

[#] Next page