From: Bhavin Patel (BPatel@ibasis.net)
Date: Thu Aug 19 2004 - 18:44:37 GMT-3
Hello Grant,
CD seems to be correct. "voice hunt user-busy" will cause the call to be
routed to the next dial-peer if you dont have "huntstop" configured on your
first dial-peer. If you have "huntstop" configured on the dial-peer, call
wont be routed to next dial-peer.
Any one else, please correct me if I am wrong.
Bhavin
-----Original Message-----
From: Grant Stevenson [mailto:grant.h.stevenson@virgin.net]
Sent: Thursday, August 19, 2004 4:53 PM
To: ccielab@groupstudy.com
Cc: steve.skinner@uk.pwc.com
Subject: voice hunt user-busy
I posted this a couple of days ago hoping for some help in the
configuration. I am not looking for anyone to breach the NDA act I was just
trying to find out wether my assumption of the command was correct. Could
anyone please advise
<SNIP>
Hi Folks,
I have a contradiction from the doc cd and a book I have read (Cisco Field
Manual: Router Configuration by David Hucaby and Steve McQuerry)
Scenario:
Phone on R1 dial peer calls R2 and the phone is busy on R2, this is
signalled
to R1, thus if this command [voice hunt user-busy] is configured on R1 then
it
will look at the next voice peer to dial say R3, so long as the same
destination pattern is used.
I have read on the CD that this command must be entered to initiate the
voice
hunt, the book contradicts this by saying that this command stops the
routing
form voice hunting.
At the present time I do not have any voice equipment in my lab, and would
welcome any discourse in this configuration.
This archive was generated by hypermail 2.1.4 : Fri Sep 03 2004 - 07:02:46 GMT-3