New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Duplicate Identity: Headers on outgoing INVITE #206
Comments
tcpdump captures! Before:
After:
|
Hi @xrobau, |
Correct. Outgoing invite. |
Confirming that I am seeing the duplicate Identity behavior as well. I don't know if @xrobau 's patch will resolve the issue as we decided to work around it. |
My patch simply sets it back to a single header, it doesn't fix the actual problem of two being added. It was the simplest change without having to revert the whole thing, which was not just here 8-( |
As an aside, I'm not actually sure how we're going to be able to set/read two headers ANYWAY. But I was too busy fixing the actual main problem to look into the other ones 8) |
Interesting, we're only forwarding an Identity header and something in FreeSwitch is duplicating it. We're not trying to set an Identity in FreeSwitch. |
@mbrooks the patch from freeswitch-builder will fix it, both setting and forwarding, as it puts it back to Highlander-style "There can be only one" 8) |
I'm getting the same problem... will attempt the patch. This essentially breaks stir/shaken attestation to STI-SA service providers. Hopefully Freeswitch devs can commit a permanent fix. |
Anyone has a PCAP of this misbehaving? |
note sending multiple is 100% legal, reverting back to single is the wrong fix. we need to undrestand why its sending twice, not make it impossible to set 2 |
check
|
Hi @lazedo thanks for your answer. <condition field="${sip_h_Identity}" expression="." break="never">
<action application="log" data="INFO LOG: copy Identity" />
<action application="export" data="sip_h_Identity=${sip_h_Identity}" />
</condition> I have 2 identical Identity headers, Please, can you explain if there is a specific conf to have only 1 Identity header (when we have only 1 identity header in A leg) ? thanks in advance |
OK, I found a solution.... I use <action application="bridge" data="
{
sip_invite_params=user=phone,
sip_cid_type=none,
ignore_display_updates=true,
sip_renegotiate_codec_on_reinvite=true,
sip_contact_user=${caller_id_number},
exclude_outgoing_extra_header=sip_h_Identity ==> HERE
}
sofia/gateway/${distributor LISTPRIVATE ${sofia profile INTERNAL gwlist down}}/${number_dest}"/> and add code: <condition field="${sip_h_Identity}" expression="." break="never">
<action application="log" data="INFO LOG: copy Identity" />
<action application="export" data="sip_h_Identity=${sip_h_Identity}" />
</condition> And I can see only 1 identity header on B leg !
cc @xrobau Answer of Freeswitch on forum: https://forum.signalwire.community/t/problem-with-double-identity-headers-on-b-leg-stir-and-shaken/693 |
After this patch was applied, setting
sip_h_identity
on a call results in the INVITE packet containing TWO identical Identity headers.4398da8
Changing the
SIP_HEADER_CLASS(identity, "Identity", "", id_common, non_compact_append, identity);
line back tosingle
fixes it, and only one Identity header is added.The text was updated successfully, but these errors were encountered: