Sorry, I don’t know, it could be any number of things. The flow type, channel order, something with the peer config or routing, if this just started and nothing else changed (which of course it never does) I would go with the reload/replace. There’s a second DSP you look to have in the flex pool for voice, which it could also use on inbound. If you run a call out you can see where it goes with the same show command. ... View more

DSP 0 is broken, there's a number of bugs out for that being stuck in "FW_DNLD_FINISHED"   You would assume that it could try other resources but as "intelligent" as these things are, they're not that intelligent.  At the bottom of the show dsp-g all should be something like this:   DSP groups on slot 1:  This command is not applicable to slot 1   1490 DSP resource allocation failure   If it failed to allocate, but, it's possible (speculating) that with the DSP being broken but it thinks it can pull credits from there that it is trying but it fails and you get an out of resources condition. I'd suggest to fix that first unless you know that you don't have an issue with it.   Congestion is equiv to a SIP 503 if it's being generated locally or relayed from a far end host. I can't say if that's the cause code that's generated if you have an actual issue with bandwidth or call limiting or something. But your DSP seems to be broken for sure.  ... View more

It is based on tracked phones and manual phones. So if someone has added manual phones that would do it , or exclude some IP range that’s registering to your UCM that you don’t want to deal with. It loads all registered devices via SNMP and goes from there plus manual devices. ... View more

We prepare our own in house doc. The PIN Sync helps a lot, same with the PCA. The wallet card tree and or unity tools generator for that (does this still exist?) helps with navigating the conversation.  ... View more

Nope, we run various ATA and analog VG3x0 series with cat6a horizontal and don’t have any trouble. The ATA sometimes have their own problems with DTMF reception but it is not cable related. Given you say 6A I asssume the cabling was certified when installed and it’s not just a case of the 4p2c cable not seating in the jack right? ... View more

Yes that in my experience is the same as the associated devices under the DN. I’m not sure what you’re asking about the dependency records. What do you want to know? You probably have to come in from another angle depending on what you want to know if it’s related to another function ( partition , vm profile , etc ) ... View more

Assuming it is in the same partition, check that the busy triggers and max call settings on that line appearance are sufficient to let it ring. ... View more

The Self Care Portal is still available for a user to make line setting changes - I’m not sure that you can’t do this with only a CSF device.    Regarding the reorder tone, this is working as it should if there is no active station at the target DN. You can deploy these with a CFUR destination to a recording to let the caller know the person they are trying to reach is unavailable, generically.    Call Back or Camp On is not something that I’ve used personally, however even non Jabber users can display phone presence if tethered to an account, providing the equivalence to a BLF when on the users roster. This does not carry on to anonymous devices, but Jabber is user oriented. The availability state shown in the UCM doesn’t carry over to Jabber unfortunately as far as I can tell, as you can’t subscribe to presence for a line with the client. Not ideal but a possibility.  ... View more

Note the behavior for MRA in maintenance in that since the phone or jabber is effective registered through the E, it won’t figure out maintenance immediately and you’ll have a period where calls will fail to progress.   Youll also see alarms about the cluster that take a bit to clear while things reconverge but this is normal.    I ran ran into an issue with 8.10.4 using per domain DNS for MRA, where on one cluster upgrading to X8.11 broke this, which I could reproduce- didn’t affect another. Needed to reconfigure this feature for it to work properly . ... View more