Could be a few things. Do a caller ID lookup and see who the number is showing registered to. Make sure the number is removed from the pbx it moved from. If it’s showing the correct carrier and the number isn’t in the original pbx routing table. If that’s all clear than it’s the winning carrier NOC team you’ll need to talk to.

Telnyx sent me an email about a month ago saying their api keys may have been compromised. Maybe that.

Look at groundwire. Looks like it will do what you need it to. https://faq.acrobits.net/set-up-your-web-callback-web-service

Here is a forum post I found that might be helpful. Has some python scripts to try and do what you want. http://forum.yealink.com/forum/archive/index.php?thread-40689.html But seems they were having issues with it. But were trying with a T46.

I’d be interested if you find a way to get it to work.

Should be interesting to see what happens. Was at kazoocon when it was announced. Seems like ooma runs off 2600hz platform. From my understanding 2600hz is going to be ooma’s wholesale division.

Yah I’d try this. Also there is another option in the web ui that allows you to adjust volume but might just be adjusting this in the config.

Usually with polycoms depending on the cloud pbx *0 then the ext will intercom. Which is different from paging . But to do intercom you need to change some settings/config. You don’t want intercom to barge in while someone is on a call putting them on hold so the intercom caller gets priority. You might also want there to be an audible ring before it connects the intercom.