Hunt Group setup: hunt Group 501 is set to ring ext 201 for 25 seconds, if no answer it falls back to hunt group 502 hunt Group 502 is set to ring ext 202 for 25 seconds, if no answer it falls back to hunt group 503 hunt Group 503 is set to ring ext 206 for 25 seconds, if no answer it falls back to ext 100 "operator" Default Global forking is set to 50 seconds When ext 203 dials 501, the following takes place Ext 201 rings for 25 seconds, then ext 202 rings for 25 seconds, ext 206 rings for 25 secs What is expected after that is "operator ext 100" connects, that does not happen, message played user not available Note if hunt group timers is set to 24 seconds it works and operator answers Analysis In the case of successful call 24 seconds hunt group, and global forking 50 seconds
1. first hunt group 501 is dialed cause the first set ext "201" to ring for 24 seconds 2. fall back to hunt group 502 cause the second set "ext 202" to ring for 24 seconds, also the global timer starts here before the invite to 202 3. fall back to hunt group 503, cause the third set "ext 206" to ring for 24 seconds 4. fall back to "ext 100" the operator and connects the call to the operator "the global forking timer at 48" so it works In the case of failed call 25 seconds hunt group, and global forking 50 seconds 1. first hunt group 501 is dialed cause the first set ext "201" to ring for 25 seconds 2. fall back to hunt group 502 cause the second set "ext 202" to ring for 25 seconds, also the global timer starts here before the invite to 202 3. fall back to hunt group 503, cause the third set "ext 206" to ring for 25 seconds 4. Global timer expires before falling back to "ext 100" the operator as the global forking timer now is at its expiration 50 seconds One problem with increasing the global forking timer is that when a user is called voice mail will not kick in until the global forking timer expires "the default is 20 seconds" Any work around? Hesham Abdelrahman Nortel, SCS Design Support * Phone 613-763-2471 ESN 393-2471 * mailto:[EMAIL PROTECTED]
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
