Thread: External Calls Ring Wrong Extension

I understand the meaning of making the line private. Prime set is already set to 4614 and always has been. F983- Ans:N Answer DNs are not assignment for any extension. We only have 2 hunt groups setup. But, I did check all available to make sure either extension was not assignment. Nothing there. Here is how this started: original user of 4614 left the company and forwarded all his calls to 4641. New person hired. Canceled call forward (F#4)....

you need to check both ext in prog..and both target lines in prog..if in doubt remove  rec digits from both target lines and start over..to be sure make private to the assigned ext In Over your head? buried deep in the snow. Call a vendor. He's trained to know

If you've been over programming with a fine tooth comb, you might want to try a power cycle of the system.

Also check your received digits in line programming for that target line. Brian Cox BC Telecom Services  

I've had this problem maybe three times, had to change public to private to the ext.It corrected the problem all three times, and I never looked back for a rhyme or reason.   Disclaimer> I could be wrong

Does 4614 ring when 4641 rings - calling in on the DID? Just wondering if extension 4641 has the target line for 4614.  

thecoming means that making the line private will erase any programming related to that line. So make it private to 4614, make prime set 4614 and see what happens. Also check F983/AA/lines/your target line that it does not answer. Also make sure that 4641 does not have an Answer DN key for 4614, and make sure the target line or those DN's are not conflicting in any hunt groups.   =----(((((((((()----= curlycord www.curlycord.com...