Cannot Call Ext.

[pakman]

I have a phone that's programmed of a survivable site that can make calls internally and externally but I and others cannot call his line. The number is in the telephone directory and when I call it I get invalid but when others call it the number up top changes like it's being call forwarded. When I look what features are on the phone nothing shows up and to be safe I had him cancel any call forward by using **87...

Anything else I could check? Otherwise I will just delete the ext and re add it.

Thanks

[ralph]

1)  Are the phones calling it on the same controller?
2) I'm assuming you checked the features via the command line and it shows no active features.
3) Is the COS the same as other phones that you can call?
4) If you remove all call rerouting does it still do the same thing?

Ralph

[pakman]

Hi Ralph,

Yes, I checked for active features and there was none. The COS is the same and I'm not sure on phones calling it from the same controller as I will test that today. For number 4 the only call routing on this phone is to go to voicemail and I removed that and I still get invalid. I'm not sure if there's a way to remove all the default call routing is that's what your asking?

Thanks,

[ralph]

if you're getting "invalid" then I would think that call rerouting doesn't come into play.
Try this:
On the registered controller enter "dgt trace <extension>"
Then do the same on a remote controller.
It's possible that there is an invalid ARS set up on the remote controller.
You can prove this by calling it from a phone registered from the same controller and then one from  a remote.

Ralph

[pakman]

On the remote PBX the results are

DGT trace Started:
4605 : remote DN (388)
DGT trace completed

On the registerd controller
DGT trace Started:
4605 : broadcast group (73)
DGT trace completed

I would think if it was an ARS issue I wouldn't be able to call other numbers at the remote branch which I can.

[pakman]

Think I found out why as on the remote site I went to users and devices and looked up 4605 and received the following.

The device for service '4605' is missing.

Sync Device Level Resiliency with the secondary host 'Unknown Host', and resolve errors related to this service.

If the service does not exist on the secondary host 'Unknown Host', click here to remove all references to this service:

Other options to try fixing the problem are as follows:

    Run the GDM CHECK USERANDSERVICE and GDM REPAIR USERANDSERVICE maintenance commands on this service's primary host 'Unknown Host'.
    Program a new device with Number '4605'
    Check the SDS Distribution Errors form on this service's primary host 'Unknown Host' for errors related to this service and resolve any you find.