[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Linphone-users] Invalid contact field - possible bug

From: Aymeric Moizard
Subject: Re: [Linphone-users] Invalid contact field - possible bug
Date: Thu, 18 May 2017 23:28:03 +0200

Hi Jean, Hi list!

I'm answering as the author of eXosip.
-first, your questions refers to very old linphone and very old eXosip-

In theory, if (null) appears in the contact header
it means the API "eXosip_masquerade_contact" was
called with "(null)" as the parameter.

I guess this was the result of the printf with a NULL value.

I would supsect some kind of STUN failure or some other
failure when checking ip.

In theory, eXosip_masquerade_contact must never be called...

So, if you can find out where it's called, just remove the code. Or
configure your linphone in order to avoid the API call (disable stun?)

That's only ideas.


2017-05-18 21:56 GMT+02:00 Jean Cérien <address@hidden>:


Anyone can help ?


On Wed, May 17, 2017 at 2:47 PM, Jean Cérien <address@hidden> wrote:

I am using Linphone/3.6.1 (eXosip2/4.1.0) on Linux Mint, and the INVITE packet sent has a weird contact field:
Contact: <sip:mylinuxuser@(null)>
While it should be Contact: <sip:address@hiddenne>

Is this known ? Is there a way to have this populated correctly by config, or is it a bug ?


Linphone-users mailing list

Antisip -

reply via email to

[Prev in Thread] Current Thread [Next in Thread]