Now this leads to another question. If I am monitoring an extension which is running a socket application or playback or something like that, I can't do this: <action application="set" data="presence_id=44@$${domain}"/> because that really "hijacks" the channel from whoever it actually belongs to, who might have a valid presence_id of their own (i.e. might be a registered set which others are monitoring). (That also might explain why I was seeing the "direction" backwards when monitoring a FS app). Is the complete solution then to use a bridge application with data="loopback/app=socket...", and set the presence_id of the application extension on the far side of the bridge? i.e. something like this: <action application="bridge" data="presence_id=44@$${domain};loopback/app=playback..."/> On a somewhat related note, how does monitoring of conference and park extensions work? Does the presence_id have to be set in the dialplan, or is it done automatically for these applications? When a registered user calls into a conference, would PRESENCE_IN events be generated for both ends of the call? Carolyn
-----Original Message----- From: freeswitch-dev-bounces@lists.freeswitch.org [mailto:freeswitch-dev-bounces@lists.freeswitch.org] On Behalf Of Beeton, Carolyn (Carolyn) Sent: Thursday, November 11, 2010 3:25 PM To: freeswitch-dev@lists.freeswitch.org Subject: Re: [Freeswitch-dev] Question about presence_id
Ok - I think I see now. Changed my dialplan to this:
<extension name="47"> <condition field="destination_number" expression="^47$"> <action application="bridge" data="{presence_id=47@$${domain}}sofia/cbeetonscs.ca.nortel.co m/47%cbeetonscs.ca.nortel.com"/> </condition> </extension> <extension name="49"> <condition field="destination_number" expression="^49$"> <action application="bridge" data="{presence_id=49@$${domain}}sofia/cbeetonscs.ca.nortel.co m/49%cbeetonscs.ca.nortel.com"/> </condition> </extension>
That sets the presence ID for the outgoing legs properly. The presence ID for the incoming leg is set by default by registration. And events are generated as expected and lights work as expected. I just didn't find this bit of info anywhere in the docs!
Carolyn _______________________________________________ FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org