I’m at wits end, hoping HN knows how this works and how to go about troubleshooting:

8 years ago I signed up with Tropo for our then-start-up's Canadian phone number (area code 403 with a number meaningful to our business).

Around the same time, I also signed-up with Twilio; we have our US number there.

Tropo was acquired by Cisco & on Oct 1 announced a wind-down of all services by Nov 30. Since then I’ve been trying to port our 403 number from Tropo over to Twilio.

Twilio support says the port request is being rejected because the address on file at the losing carrier doesn't match. For weeks now, all they say is: "contact your provider for the CSR on file which contains the needed address."

I've repeatedly told them that the only provider I've ever dealt with for the 403 number is Tropo, who provided a CSR that DOES confirm the address on the port request. Tropo denies even receiving any port request, as does their upstream provider of the 403 number, Voxbone.

I suspect the losing carrier is upstream still from Voxbone & the address they have on file is not even ours (perhaps Voxbone’s?) I suspect the carrier is Iristel (they seem to operate other numbers in the same 403 subrange) but I can’t be sure.

Twilio refuses to say who's rejecting the port request, citing NDAs with their carrier partners. They will not even confirm whether by “my provider” they mean Tropo.

I've asked Twilio and Tropo email support to liaise directly, with no luck. No one from either company will reach out to me via phone to get to the bottom of this. I’ve reached out to Iristel for info, I’ve even tried to communicate to both them and Voxbone that I'm open to taking this number as a SIP trunk until the port can be resolved, but radio silence.

Where do I go from here? Are we seriously going to lose our business phone number with an 8-year collateral history, because telecoms companies are refusing to, erm, communicate?