INVITE field "to" with letters

[enio.eltz]

Hello

I am running some tests with a SIP provider. System is OXE R11.0.1-k1.520-42-br-c0s1.

I configured SIP External Gateway and OXE is registering and making calls properly. My situation is with the incoming calls, OXE is replying 404 not found. I know the reason, or at least I think I know.

The number of my account is 560001.

Due to the SIP provider topology, it sends the INVITE with a name before the number 560001, as I can see on the traces. The INVITE lands on OXE with the field to this way:

To: <sip:name-560001@IP_address;transport=UDP>.

After sip: and the account number, the SIP provider sends name-.

Then, I understand OXE sends 404 not found because DDI translation table does not have name-560001 but just 560001.

The question is: Is there a way to configure the value name- to be reconized by OXE? Has anybody ever faced this situation?

I looked for something about that on this forum and OXE configuration, but no success.

Best Regards.

[cavagnaro]

Jummm I guess that even that name is no fixed length... So...
I guess you have to ask them to stick to a valid RFC and not do that

Enviado de meu E6633 usando Tapatalk

[enio.eltz]

Hi cavagnaro

I think the same. First time I see an INVITE this way. Usually it is just numbers. But it is just a test, and there is no a need to run immediately, I can play with that.

Best regards.

[cavagnaro]

Not only numbers, but the username as declared, which can be anything, letters and numbers. But the weird thing is that they alter that username by adding a name...which should be at <> brackets in the correct way following RFCs

Enviado de meu E6633 usando Tapatalk