Single stage dialing based on SIP number dialed on OBI202

[Hortoristic]

How can I set up single stage dialing to also consider the number that was dialed?

I'm using this X_InboundCallRoute settings:
Voice Services > SP2 Service > X_InboundCallRoute:
{(13605551212):sp2(011441179123456)},{ph}

My DID forwarding settings at Callcentric:
19142961111@mydomain.dyndns.info:5061
19142961222@mydomain.dyndns.info:5061

If for example; if I call either  of these numbers (19142961111 or 19142961222); and my incoming caller id is: 13605551212, it then will dial out using SP2 and dial: 011441179123456 – this works great.

What I really want is to re-dial another number based on which number was called.

If I dial 19142961111, I want it to call 011441179123456:
Voice Services > SP2 Service > X_InboundCallRoute: {(13605551212):sp2(011441179123456)},{ph}
If I dial 19142961222, I want it to call 011441179128888:
Voice Services > SP2 Service > X_InboundCallRoute: {(13605551212):sp2(011441179128888)},{ph}

At first I thought that I would need to have each DID seperately ring a different SP; forwarding to SP1 and SP2 –which I think is just merely controlled by what port I use – isn't SP1=5060 and SP2=5061?  

Then my separate rules would be applied at the incoming SP they called into - my Callcentric DID forwarding would look like:
19142961111@mydomain.dyndns.info:5061
19142961222@mydomain.dyndns.info:5062

Is this the best approach?

[ianobi]

Hortoristic,

This is a long shot as I don't know exactly what Callcentric is forwarding to the OBi.

Voice Services > SP2 Service > X_InboundCallRoute:
{(13605551212)>(19142961111):sp2(011441179123456)},{(13605551212)>(19142961222):sp2(011441179128888)},{ph}

In the unlikely event that this works, please report back - I would like to try making the rules easier to read by deleting some of the parentheses.

[Hortoristic]

This worked wonderful!  The numbers dialed (19142961111, 19142961122) are both numbers with Callcentric forwarded to port 5062 - which for some reason my OBI says is SP4?

Voice Services > SP4 Service > X_InboundCallRoute:
{(13604530000)>(19142961111):sp2(13607255514)},{(13604708888)>(19142961122):sp1(13604703655)},{(x|xx|xxx|xxxx|xxxxx|xxxxxx):},{ph}

OR:

Voice Services > SP4 Service > X_InboundCallRoute:
{(Number Calling From)>(Number Dialed):sp2(Redial This number using SP2)},
{(Number Calling From)>(Number Dialed):sp1(Redial This number using SP1)},
{(x|xx|xxx|xxxx|xxxxx|xxxxxx):},{ph}

The above rule: {(x|xx|xxx|xxxx|xxxxx|xxxxxx):} - is to stop the SIP scanners which has been 100% for me for some time.  Probably don't need it - since the rule is looking for a specific caller id number to redial another number.

How can I add a rule that forwards (re-dials another number) any call to a specific number?
{(anybody's Number)>(011441267410200):sp2(Redial daughter's cell # using SP2)}

I have a UK number where family can call and it would redial my daughters cell number.  We want anybody that dials the specific UK did to redial her cell.

[ianobi]

This worked wonderful!  The numbers dialed (19142961111, 19142961122) are both numbers with Callcentric forwarded to port 5062 - which for some reason my OBI says is SP4?

If settings are at default, then I would expect 5062 to be sp3. This is defined by:

Voice Services -> SP3 Service -> X_UserAgentPort : 5062

It may be worth checking all of your UserAgentPorts.

How can I add a rule that forwards (re-dials another number) any call to a specific number?
{(anybody's Number)>(011441267410200):sp2(Redial daughter's cell # using SP2)}

To allow any caller you should leave the "Caller" section blank, but you must put the ">" in to show OBi that the next number is the "Callee" section. This should work:

{>011441267410200:sp2(Redial daughter's cell # using SP2)}


In some of your routings you have incoming and outgoing calls on the same spX, which is fine for two calls, but you are in danger of running out of sessions if you also use call hold/transfer etc. I would increase the sessions on the "busy" spX's like so:

Voice Services -> SP2 Service -> MaxSessions : 4


As always you have come up with interesting configurations. You certainly get full value from your OBi202   

[Hortoristic]

Well the: {>011441267410200:sp2(Redial daughter's cell # using SP1)} did not work because the UK DID when called is passing in the callers number, not the DID, which makes sense.

Would moving to an open SP for just this purpose and forward all calls to cell look like this?

Forward all calls to cell on this SP dialing out on SP1:
{sp1(Redial daughter's cell # using SP1)}

I guess what I'm really wanting is this local UK DID my daughter can give her family, where if anyone calls it - it always goes to her cell number here in USA - so it really is just re-forwarding it - but trying to get it to work on our my existing SP2 isn't practical - so moving it to SP4 removes all the other rules I need for the DID on SP2 to work right.

[ianobi]

Yes, this would work:

Voice Services > SP4 Service > X_InboundCallRoute:
{sp1(12345678912)}

Where 12345678912 is your daughter's cell phone number. However, that does mean any incoming call on sp4 would be forwarded including sip scanners. I would prefer:

Voice Services > SP4 Service > X_InboundCallRoute:
{>(17770001234):sp1(12345678912)}

17770001234 is whatever appears in this value:
Voice Services > SP4 Service > SIP Credentials > AuthUserName

[Hortoristic]

I'm not registering the SIP on the SP - I'm following instructions from RonR about just enabling the SP with a dummy ProxyServer.  This allows my me to use SIP routing like this: 19142961111@mydomain.dyndns.info:5063, or 442032982000@176.192.123.1.

So there is no AuthUserName or password needed - my phone rings on anything sent to that specific 506x port.

This rule has never let a SIP scanner through: {(x|xx|xxx|xxxx|xxxxx|xxxxxx):}

Is the CallerID only controlled by the place who gives me the DID number(s) - or is their a way to tell the OBI to pass through the number dialed as the caller ID instead of the phone number that called the DID number?  If I could get it to do this - I'm back to being able to use the rule below, with a bunch of DID's ringing SP4, and based on the DID dialed, determine what rule to use.

Below would work great if caller ID was showing the DID number called, instead of the persons caller ID that called the DID.

Based on any of my DID(s) called, from ANY number, redial another number: - will only work if I can get the caller ID to show the DID #, not the caller's number:

Voice Services > SP4 Service > X_InboundCallRoute:
{>MyDIDNmbr1:sp2(Redial some number via SP2)},
{>MyDIDNmbr2:sp3(Redial some number via SP3)},
{ph}

[Shale]

This rule has never let a SIP scanner through: {(x|xx|xxx|xxxx|xxxxx|xxxxxx):}

I think you are saying that rule has not let a SIP scanner through to you yet. I am thinking I read a post or two that reported getting a SIP scanner call that used a longer caller ID.
http://www.obitalk.com/forum/index.php?topic=4067.20 Reply #26
http://www.obitalk.com/forum/index.php?topic=4411.0
http://www.obitalk.com/forum/index.php?topic=2427.0

There may be others than 555-0000, but my search methods were simple.

Is the CallerID only controlled by the place who gives me the DID number(s) - or is their a way to tell the OBI to pass through the number dialed as the caller ID instead of the phone number that called the DID number?  If I could get it to do this - I'm back to being able to use the rule below, with a bunch of DID's ringing SP4, and based on the DID dialed, determine what rule to use.

Below would work great if caller ID was showing the DID number called, instead of the persons caller ID that called the DID.

Based on any of my DID(s) called, from ANY number, redial another number: - will only work if I can get the caller ID to show the DID #, not the caller's number:

See if http://www.obitalk.com/forum/index.php?topic=5810.0  inspires you.

[Hortoristic]

That link is really great! Thanks!

How does one discover all the codes and patterns to accomplish different things - the manual doesn't seem detailed enough?  How would I decode what "(@@.|?)" does (you somewhat did), or more importantly figure out that some odd code like: "(%&" would instead insert the number dialed into my caller ID string, which could be manipulated before the rules for X_InboundCallRout are parsed against?

Quote:
"Voice Services > SP1 Service > X_InboundCallRoute:
{(<**1>(@@.|?)):ph}

This allows any alphanumeric CallerID or anonymous (no CallerID) and prepends **1 to it. If the CallerID is 12345678912, then the phone will display **112345678912. The **1 showing the call has come in on sp1."

[ianobi]

Yes CallerIDs can be changed, but that's not the issue here! (But it is quite interesting  )

Voice Services > SP4 Service > X_InboundCallRoute:
{>MyDIDNmbr1:sp2(Redial some number via SP2)},
{>MyDIDNmbr2:sp3(Redial some number via SP3)},
{ph}

The above rules do not use CallerID at all, so it does not matter who is making the call.

MyDIDNmbr1 is a callee. The basic InboundCallRoute rule is:
{caller>callee:target}

If we use {>callee:target} then any CallerID is accepted so long as the callee matches the rule.

19142961111@mydomain.dyndns.info:5063

In the above when 19142961111 arrives at the OBi it is the callee.

In the above cases, if 19142961111 = MyDIDNmbr1, then this rule should work:

{>19142961111:sp2(Redial some number via SP2)}


This should work for a registered spX or the dummy spX.

[Hortoristic]

Is there any way to capture the "callee" information?  If I have 3 DID's calling SP4, how can I tell which "callee" or number was dialed?  Doesn't seem to be in call history.

[ianobi]

I guess we could combine this with the post Shale pointed out (modified):

Voice Services > SP4 Service > X_InboundCallRoute:
{(<@.:19142961111>)>19142961111:sp2(Redial some number via SP2)}

This should take any CallerID and replace it with 19142961111, which should show in Call History. It would only be for information, the call matching would still be done by the 19142961111 in the callee section of the rule. It also means that you would not see the original CallerID in Call History.

I don't have time to try this today. Friday evening here time to go out  

[ianobi]

My idea in Reply #11 does not work.

Call Status and Call History only show the original CallerID. I can prepend codes to the CallerID as we knew before using:

Voice Services > SP4 Service > X_InboundCallRoute:
{(<**4>@.)>19142961111:sp2(Redial some number via SP2)}

This prepends **4 to any CallerID in a call where the callee is 19142961111 and sends the spoofed CallerID on to the target. This assumes you have checked X_SpoofCallerID. However, OBi does not show the spoofed CallerID in any record.

There are other ways of spoofing CallerID, but that's not really what this thread is about.