We’re developing a third-party calling app integration with HubSpot. We have our own validation layer, and we would like to allow non-country code numbers (i.e. for IP numbers).
Basically HubSpot enforces validation for all numbers to fit E164, even though it allows inputting non-formatted numbers. It throws an error whenever a non-E164 number is called, or whenever a call is incoming from a non-E164 number (through the calling-extension SDK).
Is there a way to disable that, or work around it?
Hey, @Sadat 
I don’t think you are missing an option to bypass or workaround this option.
You can look at implanting middleware to preprocess your non-E.164 numbers into a compliant format before sending to HubSpot. And we’ll leave this thread open in case other users have additional suggestions or feedback for you.
Best,
Jaycee
Hmmm. It seems I’ll have to reserve one of the country codes for IP numbers, and strip the country code from it whenever I wanna use it for calls.
@Jaycee_Lewis Do you think this is a valid feature to suggest in ideas (having a toggle in options for enforced country code validation)?
There’s already an option to add non-E164 numbers to contacts, so it seems these two should go hand in hand, no?
@Jaycee_Lewis
Could this possibly be raised as an issue to the SDK developers?
HubSpot allows saving numbers without country code, however the SDK doesn’t allow calling to/from those numbers if they don’t fit have a country code (even tho the numbers are already saved to the contact just fine).
This is related to my other post about phone number extensions, and not being able to report those kinds of issues about the SDK on the repo anymore.