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