Hello Matt,
I'm having the same problem as you are (i'm using ser 0.8.12).
Please advise if know what is source of this problem.
Thanks
Ri Liang
------------------------
So.. did anyone have any ideas as to what I may be doing wrong? Matt Hess wrote: > I want to send an updated uri to the exec'd script but beyond 2 updates > to the uri ser seems to fail to update the uri.. > > so when the failure route keeps being called the last number it had just > tried is sent but that doesn't seem to happen and I'm wondering if this > is a bug in ser as it would seem so.. to me at least. > > Say the hunt number is dialed.. route(2) is called.. which calls the > script.. the hunt number is sent properly to the script and the script > returns the first number in the hunt properly.. (06 in my example). Now > if that number is busy ser drops to the failure_route[2] and 06 is sent > back to the script and the script returns 07.. ok now if that number is > busy failure_route[2] should be called again. But instead of sending 07 > to the the script as the number last dialed (or current uri) ser sends > 06 again to the script which to me seems like an incorrect behavior..? > > > Kapil Dhawan wrote: > >> could you pls explain ..how are you implementing call hunting.....well >> i am also implementing SER and need same feature by this time i am >> writning it in module...do u have any other possibility.... >> >> >>> From: Matt Hess <mhess at livewirenet.com> >>> To: serusers at iptel.org >>> Subject: [Serusers] hunt groups? >>> Date: Sat, 14 Feb 2004 12:01:04 -0700 >>> >>> I'm trying to do hunt groups in ser.. >>> >>> I've come to the conclusion that to do multiple hunt groups I need to >>> call an external script that replies with the next uri to call when >>> it looks at the current one being sent to it.. ie: >>> sent returned >>> 3039930010 3039930006 >>> 3039930006 3039930007 >>> 3039930007 3039930008 >>> 3039930008 3039930006 >>> >>> However on entering the failure route I have found that the current >>> uri is not being updated to reflect the one it has received.. so ser >>> keeps looping on the first 2 numbers in the hunt.. >>> >>> here are my route blocks.. >>> >>> route[2] { >>> log(1, "LOG: entered hunt route"); >>> t_on_failure("2"); >>> exec_dset("/usr/local/ser/huntgroup.pl"); >>> append_branch(); >>> t_relay(); >>> } >>> >>> failure_route[2] { >>> log(1, "LOG: Hit failure_route 2"); >>> t_on_failure("2"); >>> exec_dset("/usr/local/ser/huntgroup.pl"); >>> append_branch(); >>> t_relay(); >>> } >>> >>> so on the example above it routes to the first 06 and 07 numbers >>> properly but when I would think 07 would be the uri sent to the perl >>> script an environment check sees that 06 is still being sent as the >>> $SIP_USER >>> >>> any ideas as to what I need to do? >>> >>> >>> >>> _______________________________________________ >>> Serusers mailing list >>> Serusers at iptel.org >>> http://lists.iptel.org/mailman/listinfo/serusers >> >> >> >> _________________________________________________________________ >> Masterpieces made affordable! Buy art prints. >> http://go.msnserver.com/IN/42736.asp MSN Shopping. > > > _______________________________________________ > Serusers mailing list > Serusers at iptel.org > http://lists.iptel.org/mailman/listinfo/serusers