[Freeswitch-users] Does this configuration make sense?

[Michael Jerris]

if you are building dial strings dynamically and dial plan dynamically it is at least possible to still do that, although a bit trickier to do right, if you use the alternate auth-username method Brian refers to.

> On Aug 15, 2017, at 3:48 PM, Michael Avers <michael at mailworks.org> wrote:
> 
> Yes I agree it's much simpler, the issue is I need to be able to send calls to specific user devices at times. For example a user may not want mod fifo calls to go to anything but the deskphone, etc. Or users want to ring them sequentially even when dialed internally as an extension.
> 
> 
> On Tue, Aug 15, 2017, at 12:33 PM, Brian West wrote:
>> You're better off making them all register as the same, it makes everything easier.  Change the auth-username so you can tell them apart possibly.
>> 
>> /b
>> 
>> 
>> On Tue, Aug 15, 2017 at 2:35 AM, Igor Olhovskiy <igorolhovskiy at gmail.com <mailto:igorolhovskiy at gmail.com>> wrote:
>> Hi!
>> 
>> Actually, you can use a ring groups here.
>> 
>> Like 
>> 
>> condition - destination_number - 3005
>> action - bridge - user/3005_mobile,{leg_delay_start=10}user/3005_desktop
>> 
>> More on this - https://freeswitch.org/confluence/display/FREESWITCH/Dialplan+FollowMe <https://freeswitch.org/confluence/display/FREESWITCH/Dialplan+FollowMe>
>> 
>> Regards, Igor
>> 
>> On 14 авг. 2017 г., 4:09 +0200, Michael Avers <michael at mailworks.org <mailto:michael at mailworks.org>>, wrote:
>> 
>>> I'm trying to ditch multiple registrations and go with a concept where a user (say identified internally as extension # 3005) can register any number of devices/softphones using unique SIP credentials for each one, and so extension would end up having these extensions configured:
>>> 
>>> 3005 at domain - primary extension, but no one registers it directly. It is used for presence and its dial_string will define what other extensions are supposed to ring
>>> 
>>> 3005_desktop at domain
>>> 3005_mobile1 at domain
>>> 3005_yealink at domain
>>> 
>>> and so 3005's dial_string can define that the Yealink and Mobile1 extensions will ring for the first 10 seconds, and only then 3005_desktop starts to ring as well.
>>> 
>>> They will all have 3005's VM box as their voicemail box.
>>> 
>>> When they call out they will set presence_id to be 3005 at domain and also presence_id will be set when they are called via 3005's dial_string.
>>> 
>>> Anybody ever did this kind of set up?
>>> 
>>> The whole idea is to have the user control which of their devices ring, if at all. Because I see more and more users registering on 3+ devices and they don't always want them to all to ring right away.
>>> 
>>> Mike

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20170815/54c7c295/attachment.html>