[Freeswitch-users] (no subject)

[Steven Ayre]

It's certainly acceptable:

RFC3261:
Header field          where   proxy ACK BYE CAN INV OPT REG
Contact                2xx           -   -   -   m   o   o

i.e. mandatory in 200 reply to invite but *optional* for 200 reply to register.

I don't know whether currently there's any way to disable it though.
Looking through the source quickly I don't think it's currently
possible, but one of the core developers would be able to give a
better answer.

sofia_reg.c:1452                 nua_respond(nh, SIP_200_OK,
SIPTAG_CONTACT(sip->sip_contact),
sofia_reg.c:1453
TAG_IF(path_val, SIPTAG_PATH_STR(path_val)), NUTAG_WITH_THIS(nua),
SIPTAG_DATE_STR(date), TAG_END());

This seems to be where the response is sent, but the contact header is
always sent - it's not conditional on anything.

Out of interest, what makes you think that it's the contact header
that's the problem? Can you configure your client to send an ip&port
in the contact header instead of *, perhaps that would work better?

-Steve



On 8 November 2010 12:35, Kane, Michael (mkane02) <mkane02 at harris.com> wrote:
> Hi, I've got an issue with the way FreeSwitch is currently handling
> (un)Register requests.
>
> When my SIP client performs a registration to remove all its binding by
> using a Contact header with a value of "*", FS generates a corresponding 200
> / OK response with a Contact header with a value of "*".  My current SIP
> client does not like a Contact header being included the 200 / OK response
> in this particular scenario and flags a failure.  Is there any way to
> configure FreeSwitch (or its embedded Sofia stack) to prevent it from adding
> a Contact header in this particular scenario?
>
> Thanks,
> Mike
>
> _______________________________________________
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org
>
>