VoIP Mailing List Archives

[c.wallace777 at gmail.com]

We are working on implementing STIR/SHAKEN and have run into a snag when passing calls through our FreeSwitch LCR which sits between our call feature server and our SBC's. Our call feature server is passing parameters in the Contact for attestation-info and origination-id. It is intended that our SBC's will extract this data from the Contact and use it to generate an identity header before leaving our network. Ideally this information would be passed via X-Header(s) but unfortunately this is what we have to work with at the moment.


We have tried to use both the "sip_invite_contact_params" and "sip_contact_params" channel variables but neither of them seem to get any data from the Contact within the inbound INVITE. We had success testing with "sip_contact_user" and dumping that data to an X-Header but we can't seem to get FreeSwitch to recognize or dump the other parameters.


When debugging an active call and dumping the channel variable data for each leg of the call we don't see any of the additional parameters that are in the Contact listed in the channel variables that are dumped for either call leg's UUID.

[david.villasmil.work a...]

Have you tried just using “sip_h_[whatever]” to read from the A leg and setting it on the bridge as nolocal?

On Tue, 22 Jun 2021 at 17:25, Chris Wallace <c.wallace777@gmail.com (c.wallace777@gmail.com)> wrote:

[brian at freeswitch.com]

Have you used the info app or the uuid_dump to investigate where it is in the variables?

/b




On Tue, Jun 22, 2021 at 11:56 AM Chris Wallace <c.wallace777@gmail.com (c.wallace777@gmail.com)> wrote:

[brian at freeswitch.com]

There are no X Headers if done correctly, I suspect if you uuid_dump or use the info app, you'll find what you'll need for this task.

/b




On Tue, Jun 22, 2021 at 12:22 PM David Villasmil <david.villasmil.work@gmail.com (david.villasmil.work@gmail.com)> wrote:

[c.wallace777 at gmail.com]

Yes, we dumped the channel variables using the info application, unfortunately it didn't expose the contact parameters that were in the Contact.


We did end up with a work around by enabling the "parse-all-invite-headers" in the sofia config and then that did indeed dump the full Contact to the "sip_i_contact" variable. We were then able to export that as a new X-Header to pass along to the SBC. Kind of messy

 but it got us working in the meantime.


Ideally we would still like to be able to extract that info and place it back in the outbound contact of the b-leg. However, I have seen a couple of older posts that indicate it may be difficult because we are using the bridge application after the LCR lookup and it is difficult to manipulate the Contact because of the outbound configuration.


Thoughts?


--Chris



On Tue, Jun 22, 2021 at 1:46 PM Brian West <brian@freeswitch.com (brian@freeswitch.com)> wrote: