Caller ID based Distinctive Ring
QBZappy:
Bob.
Welcome Bob (with a dot)
Each SP has the choice of 2 possible ring profiles. Conceptually it might be possible to route incoming calls based on a CID list from a specific SP1 to SPX with a different ring tone profile. Note that a SP can be sip/GV/Obi/PSTN (OBi110). The list would be separated using pipe symbol '|'.
QBZappy:
Ian,
Let me run this by you. I suspect that the above mentioned approach can also be applied using a sip uri to another SP account on the Obi itself. The second SP acct can be used with the register setting 'disabled' and routing the call using 'ipaddress:port#'. This might work as the dependency is that at least one acct is set up for sip. What do you think?
ianobi:
QBZ,
Yes, it's really just a form of "call forking". I have not tested this exact type of configuration, but something like this should work:
Voice Services > SP1 Service > X_InboundCallRoute:
{(1222222222|1333333333|1444444444):sp1(Obi@192.168.1.13:5061)},{ph}
Where 12222222222 etc are the friends and family numbers and Obi@192.168.1.13:5061 is the local ip address of say sp2. Matched numbers incoming on sp1 would use another session of sp1 to be sent on to sp2 where they would use sp2's distinctive ring. All other calls would ring "ph" using sp1's distinctive ring.
If there are a lot of "friends and family" then the rule becomes rather long and it would be best to store them in a user defined digit map. Even that has a maximum limit of 512 characters.
This method is quite resource heavy as it uses two sessions on sp1 and one session on sp2 for each call. That might be a problem for a busy OBi device.
Bob.:
Quote from: QBZappy on May 24, 2013, 05:04:52 pm
Bob.
Welcome Bob (with a dot)
Each SP has the choice of 2 possible ring profiles. Conceptually it might be possible to route incoming calls based on a CID list from a specific SP1 to SPX with a different ring tone profile. Note that a SP can be sip/GV/Obi/PSTN (OBi110). The list would be separated using pipe symbol '|'.
Good catch on the dot. The forum required a minimum 4 digit name. While adding another o to the middle of my name might have accurate, it wouldn't have been appropriate.
I wasn't sure of how to do what you suggested. I see that you asked Ian to help. I'm trying his suggestion now.
Thanks,
Bob
Bob.:
Quote from: ianobi on May 25, 2013, 08:52:43 am
Voice Services > SP1 Service > X_InboundCallRoute:
{(1222222222|1333333333|1444444444):sp1(Obi@192.168.1.13:5061)},{ph}
Where 12222222222 etc are the friends and family numbers and Obi@192.168.1.13:5061 is the local ip address of say sp2.
This method is quite resource heavy as it uses two sessions on sp1 and one session on sp2 for each call. That might be a problem for a busy OBi device.
I think I understand this, mostly. I have tried this using my cell phone number for the incoming number. I changed the IP address and port to the actual IP and port numbers of my SP2. I couldn't get it to work.
Should I actually be using "Obi" before the @, or is that a place holder for something else I should be using?
Under Voice Services -> SP2 what entries do I need, other than changing the port to 5061?
Do I need anything in SIP Credentials?
I really appreciate any help you can give me.
Thanks,
Bob
Navigation
[0] Message Index
[#] Next page
[*] Previous page