Caller ID based Distinctive Ring
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
ianobi:
Quote
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.
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 :)
QBZappy:
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.
ianobi:
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.
QBZappy:
Ian
+1
Navigation
[0] Message Index
[#] Next page
[*] Previous page