-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Poly Phones
- Desk and IP Conference Phones
- Can I override external ring tone URL behavior?

Create an account on the HP Community to personalize your profile and ask a question

09-03-2014 09:47 AM
I am working with a softswitch that provides the following Alert-Info field in the SIP Invite to identify calls outside of a specific group:
Alert-Info: <http://127.0.0.1/bellcore-dr2>
When a call is received, I can see the delay as the phone attempts and fails to retrieve this file. After the delay, the default ring tone plays. I have tried applying a variety of alternate ring class using voIpProt.SIP.alertInfo.1.value to match this field as described in the FAQ, but from what I can see, the URL is taking precedence over this setting, and the phone always attempts to retrieve the external ring tone before falling back to the default.
Is it possible to apply an alternate ring class based on this Alert-Info value?
Edit: UC Software Version 4.1.3
Solved! Go to Solution.
Accepted Solutions
09-03-2014 10:01 AM
Hello CTC,
welcome back to the Polycom Community.
It is always useful to include the currently used software version as issues experienced may already be addressed in a newer release.
This also allows yourself and others to check against current software release notes.
Therefore the Polycom VoIP FAQ contains this post here:
Question: How can I find out my SIP UC Software Version or the BootROM Version of my Phone?
Resolution: Please check here
I quickly tested this with an SSIP7000 running UCS 4.0.7 and I do get the error message the phone rings straight away.
Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.
Best Regards
Steffen Baier
Polycom Global Services
Notice: I am an HP Poly employee but all replies within the community are done as a volunteer outside of my day role. This community forum is not an official HP Poly support resource, thus responses from HP Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge.
If you need immediate and/or official assistance for former Poly\Plantronics\Polycom please open a service ticket through your support channels
For HP products please check HP Support.
Please also ensure you always check the General VoIP , Video Endpoint , UC Platform (Microsoft) , PSTN
09-03-2014 10:01 AM
Hello CTC,
welcome back to the Polycom Community.
It is always useful to include the currently used software version as issues experienced may already be addressed in a newer release.
This also allows yourself and others to check against current software release notes.
Therefore the Polycom VoIP FAQ contains this post here:
Question: How can I find out my SIP UC Software Version or the BootROM Version of my Phone?
Resolution: Please check here
I quickly tested this with an SSIP7000 running UCS 4.0.7 and I do get the error message the phone rings straight away.
Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.
Best Regards
Steffen Baier
Polycom Global Services
Notice: I am an HP Poly employee but all replies within the community are done as a volunteer outside of my day role. This community forum is not an official HP Poly support resource, thus responses from HP Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge.
If you need immediate and/or official assistance for former Poly\Plantronics\Polycom please open a service ticket through your support channels
For HP products please check HP Support.
Please also ensure you always check the General VoIP , Video Endpoint , UC Platform (Microsoft) , PSTN

09-03-2014 10:27 AM
The issue was on a VVX 500 running 4.1.3
I haven't been able to find the entry in the release notes, but after some further testing, it looks like this is working correctly on other models running 4.1.4. Thank you for the response on this.