That seems strange to me... but I would need to dig to confirm.
On Jun 13, 2016, at 3:29 AM, Florent Krieg <flokrrr@gmail.com> wrote:
Hi Michael,
The raw sdp is actually available, but the thing is that it doesn't look like the one I see in the re-invite when I capture on the host. It looks as if it has already been processed by the SIP stack, depending on the media configuration of the sip profile and/or the current channel. Is it possible?
Florent
2016-06-10 19:14 GMT+02:00 Michael Jerris <mike@jerris.com <mailto:mike@jerris.com>>: I don't think we have the sdp parsed and processed at the point we get that callback. Check the variables to see if the raw sdp is available in the var yet or not.
On Jun 10, 2016, at 4:40 AM, Florent Krieg <flokrrr@gmail.com <mailto:flokrrr@gmail.com>> wrote:
Hello everybody,
My use case is pretty simple: I would like to react on SIP Re-INVITE without sdp (empty body/content-length 0) so I have put an execute_on_sip_reinvite instruction in my bridge string.
I have tried both to call the 'info' app and to call a custom shell system script, passing the ${uuid} var and calling fs_cli uuid_dump $uuid, but unfortunately it seems that when the SIP message reaches the application it has been processed by the Sofia stack and I can't detect if there is an SDP or not (using sdp variables, or any other actually). Sometimes it gives me 0.0.0.0 as the remote_media_ip, sometimes it just builds an SDP based on the previous one. I have also tried to modify the re-INVITE by adding custom headers or putting information in any mandatory SIP header (like, say, Via), but these updates doesn't seem to be available via any channel variable.
Is there any FS configuration parameter I could change to be able to access this information? Is there any other way I could do what I want?
Thanks in advance if you have any clue :)
Florent