The feature I am looking for is the ability to have the endpoint device assign a ring based on Caller ID.
The device supports provider specified Distinctive Ring ("Alert-Info"), but not many providers offer this service.
Ideally, this would be accomplished by assigning Caller ID patterns to specific Ring Patterns:
8005551212 -> Ring Pattern 2
8005551313 -> Ring Pattern 3
...
and any limit on the number of numbers entered would be large (50 or more).
Thanks!
shadow700,
There is a way to send CID to fast busy tone. It is mentioned on the forum. I'm looking over the Ring Profiles. I'm wondering if we can use the same approach to send a number to a different Ring Pattern.
RonR, do you think this can be done?
I put an order in for two 110 units from Amazon today.
I'm hoping there is (or will be) a way to get distinctive ring working.
Is there anything I can do as a user that would get this feature closer to reality?
Thanks!
Ancient thread, but... anyone ever figure this out?
I don't see anything about it in the admin guide, but
if it were to ever exist, I would think it would be an argument of the "ph" in the inboundcallroute
something like:
x.1212:ph(2);x.1313:ph(3)
That this is just an idea of how they could implement it; I'm 99% sure it doesn't actually work like that...
Adam
I would also like to know if this is possible.
My Linksys PAP2T did this very easily. There was an place to enter a series of telephone numbers next to a ring pattern number. If any of the listed phone numbers showed on the caller ID that ring pattern would ring.
So, my family and friends could have a different ring than everyone else who was calling.
This is a very important feature for me.
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 '|'.
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?
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.
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
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
Quote from: Bob. on May 25, 2013, 01:43:43 PM
Should I actually be using "Obi" before the @, or is that a place holder for something else I should be using?
Just as it is written
Obi@your_ip:port#
Quote from: Bob. on May 25, 2013, 01:43:43 PM
Under Voice Services -> SP2 what entries do I need, other than changing the port to 5061?
Do I need anything in SIP Credentials?
X_ServProvProfile = Something different than the SP it is coming from
X_CodecProfile = Whatever
X_InboundCallRoute = {ph}
X_RegisterEnable = Disabled
X_UserAgentPort = Make it unique
Thanks, but all this does is send my call direct to voice mail.
I'm using CallCentric, if that is any help.
That was an important detail. The second SP slot needs to be empty for this to work. You may still want to fork it over to CC with the different ring pattern. I don't know if this will makes sense with all that implies in your working environment. It might be more trouble than it's worth. (unless you really want it)
If Bob gets it working, I think he is going to write it up with a HowTo summary.
I don't know exactly what you mean when you say the "second SP slot needs to be empty. Do you mean that under Voice Providers -> SP2 that all fields should be blank? Or or your saying the under Service Providers -> ITSP Profile B that everything there should be blank? This seems doubtful with what little I know about the Obi.
I also don't understand what you mean by "fork it over to CC with the different ring pattern."
I don't mind the trouble since I will only need to do this once. I do really want this to work since I get a few business calls on the same number that family calls on. After hours and on weekends I want to know whether to jump up and get the phone or just let it ring.
It was so easy with my Linksys PAP2T. I'm almost thinking of going to the Cisco 112, even with its poor reviews. The Obi sounds like a much better product.
Thanks again for all your help.
Bob
Quote from: Shale on May 25, 2013, 03:36:05 PM
If Bob gets it working, I think he is going to write it up with a HowTo summary.
If Bob gets it working he's going to go out and
get drunk celebrate.
Actually I'll be happy to write a how to if I can.
I'm new to the Obi family. I've had Sipura and Linksys products for a long time and it seems the configuration was much easier. Of course, there may have been a smaller set of features. In this case, however, the feature I need seems difficult to implement.
Bob
QuoteVoice 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.
I have just tested this using my OBi110. Called in on sp1 (Sipgate.co.uk) call rang using sp2 ring pattern. Status > Call Status shows Call 1 incoming on sp1, being bridged back out on sp1 to Obi@192.168.1.13:5061, then Call 2 shows incoming on sp2 and ringing Phone 1.
The only problem I have is that the Peer Number (CallerID) is the AuthUserName of the service provider set up on sp1. This can only be corrected by allowing "Spoof CallerID". Most service providers do not allow that for outgoing calls.
My sp2 service is set as an unregistered "fake" service provider using these settings:
Service Providers -> ITSP Profile B -> SIP -> ProxyServer : 127.0.0.1
Service Providers -> ITSP Profile B -> SIP -> X_SpoofCallerID : checked
Voice Services -> SP2 Service -> Enable : (checked)
Voice Services -> SP2 Service -> AuthUserName : (any letters or numbers)
Voice Services -> SP2 Service -> X_RegisterEnable : (unchecked)
Voice Services -> SP2 Service -> X_ServProvProfile : B
Voice Services -> SP2 Service -> X_UserAgentPort : 5471 (5061 is the default)
Voice Services -> SP2 Service -> CallerIDName : Whatever
Voice Services -> SP2 Service -> MaxSessions : 4
The word Obi in Obi@192.168.1.13:5061 is not really a place holder. There just needs to be something there to suit the digit maps, anything will do.
I'm a bit busy today, but feel free to ask questions - tomorrow is a holiday and the forecast says rain all day - so I'll have plenty of time :)
Quote from: ianobi on May 26, 2013, 04:29:39 AM
The only problem I have is that the Peer Number (CallerID) is the AuthUserName of the service provider set up on sp1. This can only be corrected by allowing "Spoof CallerID". Most service providers do not allow that for outgoing calls.
I don't remember if the OBiTALK service allows for two voice channels. If it does, I know that the OBiTALK service passes the correct CID. If the OBiTALK service can be used it will overcome the CID limitation, otherwise the CallCentric (credit to PC44) work around for a free sip solution will work. Then any OBi model (OBi100/110) with one phone port can be used to get distinctive ring.
This call strategy is probably better suited with an OBi202. I'll explain my idea in a moment. The OBi202 can be set up with two different phones. The call forking (ph1, ph2) can be used to identify each phone as a business or personal call. I believe with most new phones it may be possible to configure a ring tone.
Consider that some cordless phones also allow for different ring tones based on CID.
Bob you are in luck because CC passes CID. You might have a working solution here.
More testing has solved most of the problems. I'm assuming that the incoming call is on sp1 and the aim is to use sp2 to get distinctive ringing for one set of calls.
Case 1: Voip provider allows CallerID spoofing
Use settings as detailed in Reply #16:
Voice Services > SP1 Service > X_InboundCallRoute:
{(1222222222|1333333333|1444444444):sp1(Obi@192.168.1.13:5061)},{ph}
Add:
Service Providers -> ITSP Profile A -> SIP -> X_SpoofCallerID : checked
The incoming call on sp1 will be bridged to sp2 and the sp2 ring pattern will be used to ring the phone. Caller Name and Caller ID should be seen on the phone.
Case 2: Voip provider does not allow CallerID spoofing
Use this setting:
Voice Services > SP1 Service > X_InboundCallRoute:
{(1222222222|1333333333|1444444444):sp1(Obi@192.168.1.13:5061;ui=$1)},{ph}
The incoming call on sp1 will be bridged to sp2 and the sp2 ring pattern will be used to ring the phone. Caller Name will show as whatever is set here:
Voice Services -> SP1 Service -> CallerIDName
Caller ID will be the correct CallerID from the original incoming call on sp1.
Ian
+1
Quote from: ianobi on May 27, 2013, 08:01:04 AM
More testing has solved most of the problems. I'm assuming that the incoming call is on sp1 and the aim is to use sp2 to get distinctive ringing for one set of calls.
Sorry if I've led you down the wrong path. Your assumption is not correct. Let me give you more details of my setup and what I'm trying to accomplish.
I have a Obi202. I have two lines with CallCentric. One account is set to ring on phone1 and the other is set to ring on phone2. I currently have line one set up on the Obi as sp1 and the other line as sp2. Using your earlier directions I just substituted sp3 in place of where ever you said sp2 and using ProfileC where you specified ProfileB.
Family might call in on either line. When any of them call in I want a different ring pattern than the default for that line. So, I can't just direct all family calls on sp1 to sp2 and have that use a different ring pattern.
Does this make it easier or, more likely, more difficult? I can do this on the Linksys/Cisco by entering the family phone numbers into the appropriate text box in the configuration screens.
BTW, I'll trade my house full of relatives today for your rainy day, and I'll through in dinner.
I haven't tried your latest solution since, based on the assumption you used, it won't work for my situation.
Continuing thanks for your efforts.
Bob
Bob,
If you have sp3 set up as a "fake" service provider, then make sure it has a distinctive ring pattern different from sp1 and sp2. Then redirect family calls from sp1 and sp2 using:
Voice Services > SP1 Service > X_InboundCallRoute:
{(1222222222|1333333333|1444444444):sp1(Obi@192.168.1.13:5062)},{ph}
Voice Services > SP2 Service > X_InboundCallRoute:
{(1222222222|1333333333|1444444444):sp2(Obi@192.168.1.13:5062)},{ph2}
5062 is default UserAgentPort for sp3.
Or use the InboundCallRoute suggested for "Case 2" in my previous post suitably modified to 5062.
The ringing pattern used to ring either phone is determined by the spX Service settings independent of any phone settings.
I'll give this a try tomorrow. No more time to experiment today. The relatives are due to start arriving within the next half hour.
I'll report back tomorrow and let you know how this works.
There's still time for you to accept my trade offer.
Bob
Thanks for the offer - I'll stick with the rain option :)
Setting the distinctive ring option for sp3 is a combination of X_RingProfile and X_DefaultRing. If you are really keen you can even design your own ring patterns - feeling musical? 8)
Quote from: ianobi on May 27, 2013, 11:32:28 AM
Thanks for the offer - I'll stick with the rain option :)
Good choice.
Ian and QBZ,
I really want to thank both of you for all the effort you've put in to help me resolve this. I am very appreciative of your work. But I never could get any of your suggestions to work.
I have settled on a much easier way to solve my needs. I'm just going to get a Cisco SPA112. I doesn't have all the features that the Obi does, but it does do the little bit I need.
Thanks again to both of you.
Bob
Bob,
Let this be a lesson for Obihai. Features drive interest in a product. Good luck.
I was very surprised that this was not available on the Obi. Everything I read praised Obi's feature set. I understand that the people behind Obi were part of the Linksys PAP2T development team.
I guess the Obi is an 18 wheeler truck to haul every thing you have and all I need is a mini-van to get to kids to school.
Good news for me. Just before ordering the Cisco, I decided to try another power transformer I had laying around on my dead Linksys PAP2T. To my shock it worked. The old wall wart must have started having some kind of problems.
Maybe when the Linksys does really die I'll check back on the Obi.
Thanks again for everything.
Bob (with a dot)
I'm surprised Distinctive ring based on caller Id isn't available myself. I'm pretty sure my pap2t na has that.
Good work on the fake service provider hack!
QuoteI guess the Obi is an 18 wheeler truck to haul every thing you have and all I need is a mini-van to get to kids to school.
I could live with the mini-van but it's more fun to drive the kids to school in an 18 wheeler. ;D
I was happy to be the test pilot to fly an original idea by QBZappy :)
The hack worked fine for me, but does consume three sessions while in use - so rather resource heavy. The simple answer would be for OBihai to listen and provide what most other devices, cell phones etc provide as standard!
giqcass,
Yes the Linksys PAP2T does do this very easily, as does the Cicso 112/122. You only have to enter the phone numbers into a text box on the appropriate configuration screen. Done.
Ian,
It's entirely possible that I didn't get the setup exactly right. But, it just wasn't worth the fight.
Hopefully the Obi folks will see this thread and implement this in the future. It is certainly a standard feature in many cell phones and even in some Voip providers.
Thanks,
Bob