Single stage dialing based on SIP number dialed on OBI202
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:
Quote from: Hortoristic on September 13, 2013, 08:52:16 am
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.
Quote from: Hortoristic
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 ;))
Quote
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.
Quote
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.
Navigation
[0] Message Index
[#] Next page
[*] Previous page