Strange Issue with multisite system

[Hershel]

Setup
Main Node has LS trunks which all inbound calls come in on and are always answered by a CRA on the Main Node.  From the CRA caller can extension dial any of the other nodes.

Issue
Outside caller calls into Main Node and select an extension on Node 2(1201) from the CRA
If the extension is available everything works fine
If the extension is busy the caller hears 4-5 rings and then ends up at the carrier operator

[Tech Electronics]

Hershel,

IP or T1 networking?

Does the busy station get to see a second call in?

What is the forwarding set up to do on a busy or no answer condition? What flags are checked?

Thanks,

TE

[Hershel]

IP networking

Forwarding Path... Station Busy = Yes
***This path send the call to the Voicemail pilot

Flags... I have screen captured the flags for this extensions and saved it has an attachment... not sure if this works as I have never tried this.

[Hershel]

The busy station does not see the call.

One more thing I tried that might help.  When the station is busy if someone from the Main Node extension dials the busy station they receive "Ext X is busy" and they got busy tones.

[Tech Electronics]

Hershel,

From what you just put in your last two posts the system forwarding is obviously not working properly. Does the person not camp on to the phone after they get a busy signal?

Forwarding Path 1
Ring Principle Once                            No
Station - Busy                              Yes
Station - DND                              Yes
Station - No Answer                           Yes
Station - Immediate                           No
System - Day Mode                           Yes
System - Night Mode                           Yes
FWD Calll Type - Call Routing Table    Yes
FWD Calll Type - CO Ring-In      Yes
FWD Calll Type - CO Transfer/AA/VM   Yes
FWD Calll Type - CO Recall              No
FWD Calll Type - DISA         Yes
FWD Calll Type - IC Calls              No

Is this what your Forwarding Path looks like (Default)?
Is Voicemail local to this station or is it centralized at another Node?

Thanks,

TE

[Hershel]

Yes those are the correct setting for the system forwarding path

The voicemail is local to the station, each node has its own voicemail. 

[Tech Electronics]

Hershel,

Could you check to see if the Node IP Connection Group for each node has Camp-Ons Allowed set to Yes.

The reason the IC call didn't work as expected was because your FWD Call Type - IC was set to No so that wouldn't be a good test. Set it to yes and see what happens.

Thanks,

TE

[Hershel]

Camp-on is set to yet for all Node IP Connection Groups

[Tech Electronics]

Hershel,

Are you able to call the node 2 voicemail directly? It may be an extension conflict that can't be resolved and it doesn't know what to do with the call.

Thanks,

TE

[Hershel]

OMG

So after trying to resolve things remotely and testing with the clients technical staff I decided it would be more efficient for all parties if I just went on site.  Seems the user had their extension set to call forward busy and to top it off the number it wasn't even a valid phone number which explains the mysterious carrier operator. 

Tech Electronics... thank for all your assistance and sorry for wasting you time.  We most definitely had the onsite people verify that the call forward setting on the extension but I guess they were either confused or lazy.