Has anyone done interop with a provider that requires From:, To: and URI to be in e.164? The problem we are having is that if our customers dial a ten-digit number, the To: is written by the UA as NXXXXXXXXX@site.com but we have no way to rewrite that as +1NPANXXXXXX@site.com before we send the message out. All the mailing list messages I have found suggest that it's a bad idea to rewrite To:. It looks like we could do it with a b2bua, but I want to avoid adding that extra complexity for what seems (on the surface) to be a simple problem. Anybody been through this? Thanks.
-Keith
TSS Support writes:
Has anyone done interop with a provider that requires From:, To: and URI to be in e.164?
i suggest you don't do interop with such a provider. to header contains what user dialed and it is highly unlikely that it contains an e.164 number or any number at all.
-- juha