Changes made to Call Creation?

[lorsungcu]

Prior to upgrading to 5.5, a customer was using the call creation API to initiate calls for remote workers' cell phones. We upgraded last night, and today, caller ID is incorrect. It seems that regardless of what we change the user's call rule to (preserve/don't preserve, etc), the call is sent out as 1<extension number>. Both the first and second legs of the call are this way, so the called party sees 1<extension number> as well. Everything worked fine, as I said, before upgrading to 5.5. Do I now need to set the caller ID name/number in the response?

[lorsungcu]

Apparently this is a known issue with 5.5. We would not have updated this customer had we know this was the case. Once again, either post these issues to the Switchvox Today page, or create an issue tracker that reflects what's actually going wrong. The agent I spoke to, after waiting literally an hour on hold, told me Digium has known about this for a week now.

http://www1.digium.com/en/products/swit ... hvox-today

[cculver]

This issue was first reported to Digium tech support on 3/12/12. The issue has been addressed and should be released in the very near future. As mentioned, the issue is posted on Switchvox Today:

http://www1.digium.com/en/products/swit ... hvox-today


As with EVERY update, we do offer a beta program to all select resellers. I would strongly recommend testing these beta versions moving forward so there aren't any 'surprises' for your installs.

[lorsungcu]

I don't have time to test for every situation, nor do my customers. Test the software before you release it. It's that simple.