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?