[Freeswitch-users] Re: Confusing about FreeSWITCH callID variables

Israel Fink ifink at machshevet.com
Sun Nov 9 13:33:47 MSK 2014


Thanks for your clear answer.

But I find thinks a bit different. we do collect the FS events during ESL mod event_socket, and find that the Unique-ID changes by channel.

What I try to do is, we have a FS server, each call comes in via the server, there were made some logic like answer, greeting etc. and also saving the call in DB. from there it goes to a client extension to get the call, speak, hang up etc. when it comes to the client I need to know which call it is in the server and in the DB. 

The only variable the client gets from the server is sip_call_id, and now after your explanation I understand why, since this is outbound.

My problem is that this variable also changes when bridging, it begins with one value then when bridging it changes to another value. the client gets the second value after bridging, and I cannot find this new value in early events like 'CHANNEL_CREATE' or 'CHANNEL_ORIGINATE', it  only appears in later events like 'CHANNEL_PROGRESS' when the client already ringing, and this is a bit late.

In short, I need a unique variable to can recognize the incoming call to the client with the incoming call to the server.





Israel Fink - Developer
Machshevet team





From: Brian West
Sent: ‎Friday‎, ‎November‎ ‎7‎, ‎2014 ‎12‎:‎23‎ ‎AM
To: freeswitch-users at lists.freeswitch.org





1. Unique-ID is the session UUID, this won't change at all during the session (aka call).



2. Channel-Call-UUID is either the same as Unique-ID or the Unique-ID of the session you're bridged to by looking at the source code.




3. sip_call_id will be the sip call_id of an inbound/outbound SIP call, More than likely the outbound would match Unique-ID and on inbound it would be what ever the remote party sets/sends.




The bigger question is what exactly are you trying to solve/understand?



On Thu, Nov 6, 2014 at 7:52 AM, Israel Fink <ifink at machshevet.com> wrote:





I'm a bit confusing about the channel variables that represent the call ID.

I find that there are three variables, 1) Unique-ID 2) Channel-Call-UUID 3) variable_sip_call_id, what is the different between this.

The value of Channel-Call-UUID seems to be stable during the entire call, the value of Unique-ID in the begin it is the same as Channel-Call-UUID but when bridging it changes it value to another ID, then it comes back to the beginning value, i.m not clear when and why.

The variable variable_sip_call_id many time don't have any value, and also it changes the value when bridging and then comes back to the previous value.

I have looked for an explanation in FreeSWITCH wiki, but don't find.

In the mailing list a have found an explanation here: http://lists.freeswitch.org/pipermail/freeswitch-users/2013-August/099035.html, but still not enough.
Can someone give a good explanation about this variables,what is their purpose, and so on.






Israel Fink - Developer
Machshevet team




_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting at freeswitch.org
http://www.freeswitchsolutions.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://confluence.freeswitch.org
http://www.cluecon.com

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





-- 



Brian West
brian at freeswitch.org

 


Twitter: @FreeSWITCH , @briankwest
http://www.freeswitchbook.com
http://www.freeswitchcookbook.com

T:+19184209001 | F:+19184209002 | M:+1918424WEST (9378)
iNUM:+883 5100 1420 9001 | ISN:410*543 | Skype:briankwest
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20141109/c7b4e612/attachment-0001.html 


Join us at ClueCon 2016 Aug 8-12, 2016
More information about the FreeSWITCH-users mailing list