03-06-2011 01:36 AM - edited 03-21-2019 09:34 AM
Hi,
I am trying to configure a SPA2102 ATA so that when a call is received from a specific phone number (e.g. 123-456-7890) a different ring pattern is used. Using the device Web interface http://x.x.x.x/voice/ > User 1 > Distinctive Ring Settings I have tried different formats but none of the ones I have used seem to do the trick. Here is a list of formats I have tried:
123-456-7890
1234567890
1-123-456-7890
11234567890
To make sure I was receiving the right caller ID information I enabled syslogging and verified the "From" field content of an inbound INVITE.
By changing the default ring value under http://x.x.x.x/voice/ > User 1 > Ring Settings I was also able to confirm that the phone I was using was capable of handling the different ring patterns.
Any idea why this feature isn't working for me?
Thanks,
Spc
Solved! Go to Solution.
03-09-2011 06:10 PM
Problem Solved!
Since my VoIP service provider does not insert an Alert-Info header in the inbound INVITE I thought that it was OK to leave the "Dist Ring Serv" option to No, which by the way is the value set by them through the provisioning feature. By setting this option to Yes the distinctive ring setting worked beautifully.
Spc
03-08-2011 03:49 PM
Hi there,
Initial and top level question: Are you enabling that feature by dialing the default *26?
You may also need to see if the specific cadence/voltage you are specifying is supported by your phone equipment.
I would think that syntax would be standard (ie 1234567890).
Let me know what happens and thanks for posting,
-Lindsey
03-09-2011 02:31 AM
Thanks for your feed back!
> Initial and top level question: Are you enabling that feature by dialing the default *26?
According to Dist Ring Setting under section Supplementary Service Settings on page http://
> You may also need to see if the specific cadence/voltage you are specifying is supported by your phone equipment
As mentioned in my original post "by changing the default ring value under http://
> I would think that syntax would be standard (ie 1234567890).
OK. Actually I have tried scores of different combinations, to not avail. I am getting the impression that this feature does not work at all. Note that I have upgraded the firmware to the latest (5.2.12) so I am really not sure what to do next.
Spc
03-09-2011 06:10 PM
Problem Solved!
Since my VoIP service provider does not insert an Alert-Info header in the inbound INVITE I thought that it was OK to leave the "Dist Ring Serv" option to No, which by the way is the value set by them through the provisioning feature. By setting this option to Yes the distinctive ring setting worked beautifully.
Spc
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide