On Mon, 2009-06-15 at 11:11 -0400, David Saint wrote:
> Hi,
> 
> I'm investigating http://track.sipfoundry.org/browse/XX-4849 which
> requires the addition of a per-user timer to override the current
> default call forward timer.
> 
> For example on the user configuration Call Forwarding page we could have
> the following.
>   With serial forking:
>   OLD  
>     Extension 201 will ring first
>     "Always" "Enabled" "If no response" Forward to "207" ring for "30"
> seconds
>     If none of the above answers, the call will be forwarded to your
> voice mailbox.
>   NEW
>     Extension 201 will ring first for "20" seconds
>     "Always" "Enabled" "If no response" Forward to "207" ring for "30"
> seconds
>     If none of the above answers, the call will be forwarded to your
> voice mailbox.
> 
>   With no serial forking:
>   OLD  
>     Extension 201 will ring first
>     If none of the above answers, the call will be forwarded to your
> voice mailbox.
>   NEW
>     Extension 201 will ring first for "60" seconds
>     If none of the above answers, the call will be forwarded to your
> voice mailbox
> 
> In order to control the user call forward timer I took a look at adding
> a per-user setting to one of the existing /var/sipxdata/sipdb/*xml
> files, for example the setting:
>   <cfwdtime>20</cfwdtime>
> 
> The AliasDB file (alias.xml) does not seem to be suitable for this
> purpose, it has one row per serial fork rather than one row per user.
> Other files like UserLocationDB (userlocation.xml) have one row per user
> but are specific to purposes that don't include call forwarding. I was
> wondering if it would be better to create a new UserForwardDB
> (userforward.xml) to contain the user forward

Creating a new database seems best, David - indexed by AOR.


_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to