I am current jumping to a different extension when a limit is reached and the limit_exceeded condition is hit by changing the 'dialed_ext' and calling: <action application="bridge" data="${sofia_contact($${domain}/${dialed_ext}@$${domain})}"/> I hit a problem when it hits the 'second line' for the user. I would like it to check via mod_limit if that extension is on the phone and respond appropriately at that point but it doesn't seem to hit the mod_limit for that second extension when it is called that way. Is there another way to call an extension and have it go through the limit process again? Thanks, Brian -- View this message in context: http://www.nabble.com/mod_limit-fall-through-tp16128842p16128842.html Sent from the Freeswitch-users mailing list archive at Nabble.com.
Let me give you some hints here. <action application="set_user" data="${dialed_ext}@${domain}"/> somewhere up stream. As it sets all the variables in that user on the current session. Then in the user set a variable for say ${failover_ext} like below: User 1000 with failover_ext set as 1001. <include> <user id="1000" mailbox="1000"> <params> ... </params> <variables> <variable name="failover_ext" value="1001"/> </variables> </user> </include> This is what I was planning on using in the error condition that the first line was busy. application="set" data="transfer_ringback=${uk-ring}" <- Chang transfer_ringback tone application="transfer" data="${failover_ext} XML default" <-- Transfer to ${failover_ext} from user ${dialed_ext}@${domain} This is an example of what you could do. /b On Mar 18, 2008, at 2:27 PM, bsnipes wrote:
I am current jumping to a different extension when a limit is reached and the limit_exceeded condition is hit by changing the 'dialed_ext' and calling:
<action application="bridge" data="${sofia_contact($${domain}/${dialed_ext}@$${domain})}"/>
I hit a problem when it hits the 'second line' for the user. I would like it to check via mod_limit if that extension is on the phone and respond appropriately at that point but it doesn't seem to hit the mod_limit for that second extension when it is called that way. Is there another way to call an extension and have it go through the limit process again?
Thanks, Brian -- View this message in context: http://www.nabble.com/mod_limit-fall-through-tp16128842p16128842.html Sent from the Freeswitch-users mailing list archive at Nabble.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
Btw you can also use the var on the user ie "max_calls" to apply the limits. /b On Mar 18, 2008, at 2:40 PM, Brian West wrote:
Let me give you some hints here.
<action application="set_user" data="${dialed_ext}@${domain}"/> somewhere up stream. As it sets all the variables in that user on the current session.
Then in the user set a variable for say ${failover_ext} like below:
User 1000 with failover_ext set as 1001. <include> <user id="1000" mailbox="1000"> <params> ... </params> <variables> <variable name="failover_ext" value="1001"/> </variables> </user> </include>
This is what I was planning on using in the error condition that the first line was busy.
application="set" data="transfer_ringback=${uk-ring}" <- Chang transfer_ringback tone application="transfer" data="${failover_ext} XML default" <-- Transfer to ${failover_ext} from user ${dialed_ext}@${domain}
This is an example of what you could do.
/b
Brian West wrote:
Let me give you some hints here.
Always appreciated! Brian West wrote:
<action application="set_user" data="${dialed_ext}@${domain}"/> somewhere up stream. As it sets all the variables in that user on the current session.
Then in the user set a variable for say ${failover_ext} like below:
User 1000 with failover_ext set as 1001. <include> <user id="1000" mailbox="1000"> <params> ... </params> <variables> <variable name="failover_ext" value="1001"/> </variables> </user> </include>
Done and with the eval application I can check the variable and it is working fine. Brian West wrote:
This is what I was planning on using in the error condition that the first line was busy.
application="set" data="transfer_ringback=${uk-ring}" <- Chang transfer_ringback tone application="transfer" data="${failover_ext} XML default" <-- Transfer to ${failover_ext} from user ${dialed_ext}@${domain}
Done and it works fine. Based on your examples and a better understanding now, I've setup the rollover for the limit_exceeded condition. The only snag I've hit is that when it hits is that when the 3rd call comes into the extension it continues to loop to trying the failover_ext which hits the limit_exceeded and tries the failover_ext which... you get the point. Any ideas on how to check if a call is active on the failover extension and if it is send it on to the voicemail? Brian -- View this message in context: http://www.nabble.com/mod_limit-fall-through-tp16128842p16178962.html Sent from the Freeswitch-users mailing list archive at Nabble.com.
Post your configs... I think I can provide an example of how to handle this one error condition. I think the fail over extension shouldn't have a limit set on it so they can fail over to the receptionist since she'll have either a sidecar or a better ability to take multiple calls at once. /b On Mar 20, 2008, at 9:10 AM, bsnipes wrote:
Brian West wrote:
Let me give you some hints here.
Always appreciated!
Brian West wrote:
<action application="set_user" data="${dialed_ext}@${domain}"/> somewhere up stream. As it sets all the variables in that user on the current session.
Then in the user set a variable for say ${failover_ext} like below:
User 1000 with failover_ext set as 1001. <include> <user id="1000" mailbox="1000"> <params> ... </params> <variables> <variable name="failover_ext" value="1001"/> </variables> </user> </include>
Done and with the eval application I can check the variable and it is working fine.
Brian West wrote:
This is what I was planning on using in the error condition that the first line was busy.
application="set" data="transfer_ringback=${uk-ring}" <- Chang transfer_ringback tone application="transfer" data="${failover_ext} XML default" <-- Transfer to ${failover_ext} from user ${dialed_ext}@${domain}
Done and it works fine. Based on your examples and a better understanding now, I've setup the rollover for the limit_exceeded condition. The only snag I've hit is that when it hits is that when the 3rd call comes into the extension it continues to loop to trying the failover_ext which hits the limit_exceeded and tries the failover_ext which... you get the point. Any ideas on how to check if a call is active on the failover extension and if it is send it on to the voicemail?
Brian -- View this message in context: http://www.nabble.com/mod_limit-fall-through-tp16128842p16178962.html Sent from the Freeswitch-users mailing list archive at Nabble.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
Brian West wrote:
Post your configs... I think I can provide an example of how to handle this one error condition. I think the fail over extension shouldn't have a limit set on it so they can fail over to the receptionist since she'll have either a sidecar or a better ability to take multiple calls at once.
I think it would be best if it went to voicemail of the original dialed extension if possible. Thanks, Brian --- directory/default/317.xml <include> <user id="317" mailbox="317"> <params> </params> <variables> <variable name="accountcode" value="317"/> <variable name="user_context" value="default"/> <variable name="failover_ext" value="417"/> </variables> </user> </include> --- directory/default/417.xml <include> <user id="417" mailbox="317"> <params> </params> <variables> <variable name="accountcode" value="317"/> <variable name="user_context" value="default"/> <variable name="failover_ext" value="317"/> </variables> </user> </include> --- dialplan/default.xml <extension name="limit" continue="true"> <condition> <action application="limit" data="inbound ${destination_number} 1"/> </condition> </extension> <extension name="limit_exceeded"> <condition field="destination_number" expression="^limit_exceeded$"> <action application="eval" data="Limit exceeded!!!!"/> <action application="set_user" data="${rdnis}@$${domain}"/> <action application="eval" data="[${failover_ext}]"/> <action application="eval" data="[${rdnis}]"/> <application="set" data="transfer_ringback=${uk-ring}"/> <action application="transfer" data="${failover_ext} XML default"/> </condition> </extension> -- View this message in context: http://www.nabble.com/mod_limit-fall-through-tp16128842p16180941.html Sent from the Freeswitch-users mailing list archive at Nabble.com.
Move the limits per user into the directory vars too.. then you can raise the limit for the receptionist. /b On Mar 20, 2008, at 10:12 AM, bsnipes wrote:
Brian West wrote:
Post your configs... I think I can provide an example of how to handle this one error condition. I think the fail over extension shouldn't have a limit set on it so they can fail over to the receptionist since she'll have either a sidecar or a better ability to take multiple calls at once.
I think it would be best if it went to voicemail of the original dialed extension if possible.
Thanks, Brian --- directory/default/317.xml <include> <user id="317" mailbox="317"> <params>
</params> <variables> <variable name="accountcode" value="317"/> <variable name="user_context" value="default"/> <variable name="failover_ext" value="417"/> </variables> </user> </include>
--- directory/default/417.xml <include> <user id="417" mailbox="317"> <params>
</params> <variables> <variable name="accountcode" value="317"/> <variable name="user_context" value="default"/> <variable name="failover_ext" value="317"/> </variables> </user> </include>
--- dialplan/default.xml <extension name="limit" continue="true"> <condition> <action application="limit" data="inbound $ {destination_number} 1"/> </condition> </extension>
<extension name="limit_exceeded"> <condition field="destination_number" expression="^limit_exceeded$"> <action application="eval" data="Limit exceeded!!!!"/> <action application="set_user" data="${rdnis}@$${domain}"/> <action application="eval" data="[${failover_ext}]"/> <action application="eval" data="[${rdnis}]"/> <application="set" data="transfer_ringback=${uk-ring}"/> <action application="transfer" data="${failover_ext} XML default"/> </condition> </extension>
-- View this message in context: http://www.nabble.com/mod_limit-fall-through-tp16128842p16180941.html Sent from the Freeswitch-users mailing list archive at Nabble.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
participants (2)
-
Brian West
-
bsnipes