Originate and Conference
Hello, when I originate a call via event socket and transfer it to a conference, it doesn't ask for a PIN. Example: originate sofia/default/222331 &conference(222500) The same happens when I originate a call and transfer it to the 222500 destination, which then transfers the call to the conference. originate sofia/default/222331 &transfer(222500) If I manually dial from the phone (222331) to the conference it correctly asks for the PIN. Anybody has a clue why this happens and how to enable the PIN while originating? Best regards Peter
On Thu, Mar 26, 2009 at 1:50 PM, Peter P GMX <Prometheus001@gmx.net> wrote:
Hello,
when I originate a call via event socket and transfer it to a conference, it doesn't ask for a PIN. Example: originate sofia/default/222331 &conference(222500) The same happens when I originate a call and transfer it to the 222500 destination, which then transfers the call to the conference. originate sofia/default/222331 &transfer(222500)
If I manually dial from the phone (222331) to the conference it correctly asks for the PIN.
Anybody has a clue why this happens and how to enable the PIN while originating?
Is 222500 part of your dialplan? If so try this: originate sofia/default/222331 222500 Let us know if that works. -MC
Hello Michael, I tried this, but received the same behaviour. It does not ask for the defined PIN. Best regards Peter Michael Collins schrieb:
On Thu, Mar 26, 2009 at 1:50 PM, Peter P GMX <Prometheus001@gmx.net> wrote:
Hello,
when I originate a call via event socket and transfer it to a conference, it doesn't ask for a PIN. Example: originate sofia/default/222331 &conference(222500) The same happens when I originate a call and transfer it to the 222500 destination, which then transfers the call to the conference. originate sofia/default/222331 &transfer(222500)
If I manually dial from the phone (222331) to the conference it correctly asks for the PIN.
Anybody has a clue why this happens and how to enable the PIN while originating?
Is 222500 part of your dialplan? If so try this:
originate sofia/default/222331 222500
Let us know if that works.
-MC
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
It's defined via XML-Curl, and manual dialling and transfering do trigger the same xml-curl request. This means that this conference number is not defined in the any xml conf file. If I transfer a call (without PIN) and then manually dial with another phone into this conf with PIN, both calls are in the same conference. I have SVN rev 12796. Best regards Peter Michael Collins schrieb:
On Thu, Mar 26, 2009 at 4:09 PM, Peter P GMX <Prometheus001@gmx.net> wrote:
Hello Michael,
I tried this, but received the same behaviour. It does not ask for the defined PIN.
Just curious - where do you define the PIN for this conference? -MC
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
I get similar behavior as Peter when trying to enter a locked conference. If I am just dialing from a phone to a conference (on a dialplan), it will properly lock me out. But if I do an originate command (originate sofia/internal/1001 &conference(3000)), it will drop me into the conference, even though it is suppose to be locked. I am using the released 1.0.3 tag. On Fri, Mar 27, 2009 at 4:27 AM, Peter P GMX <Prometheus001@gmx.net> wrote:
It's defined via XML-Curl, and manual dialling and transfering do trigger the same xml-curl request. This means that this conference number is not defined in the any xml conf file. If I transfer a call (without PIN) and then manually dial with another phone into this conf with PIN, both calls are in the same conference.
I have SVN rev 12796.
Best regards Peter
Michael Collins schrieb:
On Thu, Mar 26, 2009 at 4:09 PM, Peter P GMX <Prometheus001@gmx.net> wrote:
Hello Michael,
I tried this, but received the same behaviour. It does not ask for the defined PIN.
Just curious - where do you define the PIN for this conference? -MC
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Update again to svn trunk... btw 1.0.4 pre3 is out on files.freeswitch.org /b On Mar 30, 2009, at 6:44 PM, Dan Le wrote:
I get similar behavior as Peter when trying to enter a locked conference.
If I am just dialing from a phone to a conference (on a dialplan), it will properly lock me out. But if I do an originate command (originate sofia/internal/1001 &conference(3000)), it will drop me into the conference, even though it is suppose to be locked.
I am using the released 1.0.3 tag.
Brian West brian@freeswitch.org -- Meet us a ClueCon! http://www.cluecon.com
Hello Brian, I tried this (on trunk 12862), but still the same behaviour. It does not aks for a PIN. Neither when transfering directly to the conference nor by transfering to the dialplan extension where conference is handled. Best regards Peter Brian West schrieb:
Update again to svn trunk... btw 1.0.4 pre3 is out on files.freeswitch.org
/b
On Mar 30, 2009, at 6:44 PM, Dan Le wrote:
I get similar behavior as Peter when trying to enter a locked conference.
If I am just dialing from a phone to a conference (on a dialplan), it will properly lock me out. But if I do an originate command (originate sofia/internal/1001 &conference(3000)), it will drop me into the conference, even though it is suppose to be locked.
I am using the released 1.0.3 tag.
Brian West brian@freeswitch.org <mailto:brian@freeswitch.org>
-- Meet us a ClueCon! http://www.cluecon.com <http://www.cluecon.com/>
------------------------------------------------------------------------
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
pin checks and lock checks are both intentionally skipped on outbound calls transferred back to the conference. The idea is if you purposely placed an outbound call that was intended to land in the conference you would not want to do so only to tell them it's locked. I added a patch to trunk so you can override this with a variable originate {conference_enforce_security=true}sofia/internal/1001 &conference(3000) the same var can be used on inbound calls for the opposite effect <action application="set" data="conference_enforce_security=false"/> <action application="conference" data="3000"/> On Wed, Apr 1, 2009 at 6:41 AM, Peter P GMX <Prometheus001@gmx.net> wrote:
Hello Brian,
I tried this (on trunk 12862), but still the same behaviour. It does not aks for a PIN. Neither when transfering directly to the conference nor by transfering to the dialplan extension where conference is handled.
Best regards Peter
Brian West schrieb:
Update again to svn trunk... btw 1.0.4 pre3 is out on files.freeswitch.org
/b
On Mar 30, 2009, at 6:44 PM, Dan Le wrote:
I get similar behavior as Peter when trying to enter a locked conference.
If I am just dialing from a phone to a conference (on a dialplan), it will properly lock me out. But if I do an originate command (originate sofia/internal/1001 &conference(3000)), it will drop me into the conference, even though it is suppose to be locked.
I am using the released 1.0.3 tag.
Brian West brian@freeswitch.org <mailto:brian@freeswitch.org>
-- Meet us a ClueCon! http://www.cluecon.com <http://www.cluecon.com/>
------------------------------------------------------------------------
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ AIM: anthm MSN:anthony_minessale@hotmail.com <MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com<PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org <sip%3A888@conference.freeswitch.org> iax:guest@conference.freeswitch.org/888 googletalk:conf+888@conference.freeswitch.org<googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:213-799-1400
2009/4/1 Anthony Minessale <anthony.minessale@gmail.com>
pin checks and lock checks are both intentionally skipped on outbound calls transferred back to the conference. The idea is if you purposely placed an outbound call that was intended to land in the conference you would not want to do so only to tell them it's locked.
I added a patch to trunk so you can override this with a variable
originate {conference_enforce_security=true}sofia/internal/1001 &conference(3000)
the same var can be used on inbound calls for the opposite effect
<action application="set" data="conference_enforce_security=false"/> <action application="conference" data="3000"/>
FYI this is now in the wiki: http://wiki.freeswitch.org/wiki/Channel_Variables#conference_enforce_securit... -MC
You're one very fine janitor Michael! On the topic of the Janitor Project, this is how it should be. Devs give user feature => user documents new feature/behaviour. Even André On 1. april. 2009, at 18.34, Michael Collins wrote:
2009/4/1 Anthony Minessale <anthony.minessale@gmail.com> pin checks and lock checks are both intentionally skipped on outbound calls transferred back to the conference. The idea is if you purposely placed an outbound call that was intended to land in the conference you would not want to do so only to tell them it's locked.
I added a patch to trunk so you can override this with a variable
originate {conference_enforce_security=true}sofia/internal/1001 &conference(3000)
the same var can be used on inbound calls for the opposite effect
<action application="set" data="conference_enforce_security=false"/> <action application="conference" data="3000"/>
FYI this is now in the wiki: http://wiki.freeswitch.org/wiki/Channel_Variables#conference_enforce_securit...
-MC _______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
2009/4/1 Even André Fiskvik <grevenx@me.com>
You're one very fine janitor Michael!
How DARE you call me a janitor! :)
On the topic of the Janitor Project, this is how it should be. Devs give user feature => user documents new feature/behaviour.
Thanks. This is totally reasonable. Power users and newbies both can add to the documentation. If anyone has questions about how to help or would like some pointers then by all means contact me off list. -MC
participants (6)
-
Anthony Minessale
-
Brian West
-
Dan Le
-
Even André Fiskvik
-
Michael Collins
-
Peter P GMX