SIP contact header during SIP Registration

5. Configuration Configuration
1

Hello Everyone,

Wanted to request if anyone has any ideas on how to overcome this problem we are facing.

Our provider is forcing us to use a “contact header” like user (at) freesbc_ip_address during SIP registration.

However, from FreeSBC, the contact header is going as interfacename (at) freesbc_ip_address.

Specifically, in our case, it is sending voip1 (at) 10.0.67.134, but should be 68249999 (at) 10.0.67.134.

On FreeSBC, the interface name cannot be an integer, so, we can’t even rename voip1 to 68249999.

I’m attaching the image we received from our SIP trunk provider as well as what we are seeing from our side.

Any help or ideas on overcoming this will be greatly appreciated. Thank you very much.

2

image
image1024×576 72.6 KB

image

3

Hi

There is no way to manipulate the Contact header in Register messages at the moment.

Thanks.

4

Thank you very much for your reply. I had a couple of questions:

  1. Would this be a possibility sometime in the future?

  2. Would it be possible to allow us, through FreeSBC, to set the interface name to an integer? Because, presently, the contact header is being sent as interface_name (at) ip_address (voip1 (at) 10.0.67.134).

We are keen to get this to work with our SIP trunk provider.

5

Hi

We already have tracking for manipulation of the Register messages. But I cannot give you a date yet.

You cannot enter an integer value for the interface name.

6

Thank you very much for your reply. It’s great that you have tracking for manipulation of the Register messages. I look forward to it.

7

Hai,
Any update on this request.
Our ISP also require same way?

Thank you

8

It is not solved but as a workaround, you can change the interface name. For example, if your ISP wants to see 123456789 in contact header user part please change the interface name to 123456789f, sbc will ignore the f and send 123456789 in the contact header