[Freeswitch-dev] Question about presence_id

Beeton, Carolyn (Carolyn) cbeeton at avaya.com
Thu Nov 11 11:33:33 PST 2010 

I have 47's presence set to 47 and 49's presence set to 49.  Here's my dialplan:

   <extension name="47">
      <condition field="destination_number" expression="^47$">
         <action application="set" data="presence_id=47@$${domain}"/>
         <action application="bridge" data="sofia/cbeetonscs.ca.nortel.com/47%cbeetonscs.ca.nortel.com"/>
      </condition>
   </extension>
   <extension name="49">
      <condition field="destination_number" expression="^49$">
         <action application="set" data="presence_id=49@$${domain}"/>
         <action application="bridge" data="sofia/cbeetonscs.ca.nortel.com/49%cbeetonscs.ca.nortel.com"/>
      </condition>
   </extension>

Should I not be setting the presence_id?  I thought I was told to at one point... Maybe I misunderstood.

Carolyn

> -----Original Message-----
> From: freeswitch-dev-bounces at lists.freeswitch.org 
> [mailto:freeswitch-dev-bounces at lists.freeswitch.org] On 
> Behalf Of Anthony Minessale
> Sent: Thursday, November 11, 2010 1:54 PM
> To: freeswitch-dev at lists.freeswitch.org
> Subject: Re: [Freeswitch-dev] Question about presence_id
> 
> oh,
> 
> Dialplan: sofia/cbeetonscs.ca.nortel.com/49 at cbeetonscs.ca.nortel.com
> Action set(presence_id=47 at cbeetonscs.ca.nortel.com)
> 
> That's cos you are setting it to 47 manually.
> 
> I think the problem you may be having with the paradigm in 
> freeswitch is the each leg of the call is it's own call.  
> There is not proxy concept in FS where the bridge is actually 
> 2 legs of one call.
> 
> When you call into FS to a 1 legged app like a conference 
> then you can set the var to 47, sure.
> But if you are bridging and you want to monitor what you are 
> bridged to, you set the var on THAT LEG.
> 
> When you bridge to 47 use this as the data attr
> 
> {presence_id=47}sofia/cbeetonscs.ca.nortel.com/47%cbeetonscs.c
> a.nortel.com
> 
> 
> 
> 
> On Thu, Nov 11, 2010 at 7:57 AM, Beeton, Carolyn (Carolyn) 
> <cbeeton at avaya.com> wrote:
> > Freeswitch log with EVENT DUMPs is attached.  47 and 49 are 
> registered to freeswitch and both have presence_id set in the 
> dialplan.  Another set is SUBSCRIBEd to 49 (for presence 
> events) but nobody is SUBSCRIBEd to 47. 49 calls 47, 47 
> answers, then hangs up.  The LED for 49 sticks on at the 
> monitoring set.  The "hangup" PRESENCE_IN event for both legs 
> of the call has 47 as the presence_id.
> >
> > Carolyn
> >
> >> -----Original Message-----
> >> From: freeswitch-dev-bounces at lists.freeswitch.org
> >> [mailto:freeswitch-dev-bounces at lists.freeswitch.org] On Behalf Of 
> >> Anthony Minessale
> >> Sent: Wednesday, November 10, 2010 4:06 PM
> >> To: freeswitch-dev at lists.freeswitch.org
> >> Subject: Re: [Freeswitch-dev] Question about presence_id
> >>
> >> do you have a trace?
> >>
> >>
> >> On Wed, Nov 10, 2010 at 1:41 PM, Beeton, Carolyn (Carolyn) 
> >> <cbeeton at avaya.com> wrote:
> >> > I am trying to understand the PRESENCE_IN events that are
> >> sent on call
> >> > init, answer, and hangup.  I have two endpoints registered to 
> >> > Freeswitch, configured in the dialplan with presence_id
> >> set.  One set calls the other.
> >> >
> >> > There is one event for each leg of the call, inbound and 
> outbound.
> >> > The events contain the Channel-Name and the
> >> Channel-Presence-ID, and I
> >> > would expect these to match (i.e. each event contains the
> >> presence_id
> >> > of that leg), but it seems that for the inbound leg, they
> >> only match
> >> > on the "ringing" event, not the "answered" and "hangup" 
> event.  The 
> >> > two events for "answered" and "hangup" both have the 
> presence_id of 
> >> > the callee, regardless of the Call-Direction.  Is this
> >> intentional? (I
> >> > think it is the reason that lights stick on in certain
> >> scenarios - for
> >> > example, if there are subscribers to the caller but not 
> the callee 
> >> > then no notifications are sent on hangup)
> >> >
> >> > Carolyn
> >> > _______________________________________________
> >> > FreeSWITCH-dev mailing list
> >> > FreeSWITCH-dev at lists.freeswitch.org
> >> > http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev
> >> >
> >> 
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-de
> >> v
> >> > http://www.freeswitch.org
> >> >
> >> >
> >>
> >>
> >>
> >> --
> >> Anthony Minessale II
> >>
> >> FreeSWITCH http://www.freeswitch.org/ ClueCon 
> http://www.cluecon.com/
> >> Twitter: http://twitter.com/FreeSWITCH_wire
> >>
> >> AIM: anthm
> >> MSN:anthony_minessale at hotmail.com
> >> GTALK/JABBER/PAYPAL:anthony.minessale at gmail.com
> >> IRC: irc.freenode.net #freeswitch
> >>
> >> FreeSWITCH Developer Conference
> >> sip:888 at conference.freeswitch.org
> >> googletalk:conf+888 at conference.freeswitch.org
> >> pstn:+19193869900
> >>
> >> _______________________________________________
> >> FreeSWITCH-dev mailing list
> >> FreeSWITCH-dev at lists.freeswitch.org
> >> http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev
> >> 
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-de
> >> v
> >> http://www.freeswitch.org
> >>
> > _______________________________________________
> > FreeSWITCH-dev mailing list
> > FreeSWITCH-dev at lists.freeswitch.org
> > http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev
> > 
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev
> > http://www.freeswitch.org
> >
> >
> 
> 
> 
> --
> Anthony Minessale II
> 
> FreeSWITCH http://www.freeswitch.org/
> ClueCon http://www.cluecon.com/
> Twitter: http://twitter.com/FreeSWITCH_wire
> 
> AIM: anthm
> MSN:anthony_minessale at hotmail.com
> GTALK/JABBER/PAYPAL:anthony.minessale at gmail.com
> IRC: irc.freenode.net #freeswitch
> 
> FreeSWITCH Developer Conference
> sip:888 at conference.freeswitch.org
> googletalk:conf+888 at conference.freeswitch.org
> pstn:+19193869900
> 
> _______________________________________________
> FreeSWITCH-dev mailing list
> FreeSWITCH-dev at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev
> http://www.freeswitch.org
>

More information about the FreeSWITCH-dev mailing list