Call is routed to two lines, but why?

[mmarkowitz]

I'm experimenting with Incoming Call Routing, and set up a route that ID's my cell phone and routes it to my desk. I just wanted to be sure I was getting the formatting and such correct.

Sure enough, when I call in from my cell my desk phone starts to ring. Success!

But for no reason I can understand, the operator's desk rings too. Failure!

Looking in monitor, I can see it does this deliberately, but I don't understand why. The first line below is the match I expect, routing my number to extension 225. But then it goes on an ADD PRIMARY's in the extension 221.

Can anyone offer a reason for this? 221 does not appear in any ICR, and I don't have a fallback on my rule, or anything like that. There is a rule for *all* calls to line 200, Main, which may ring 221, but why would that fire in this case?

2532246910mS CMTARGET: 6.3.1 12659 Alog Trunk:6: LOOKUP ICR: DDI= CGPN=1416xxxxxx (Destination 225 ) => CDPN=225
2532246910mS CMTARGET: 6.3.1 12659 Alog Trunk:6: ADD TARGET (N): number=225 type=0 depth=1 nobar=1 setorig=1 ses=0
2532246910mS CMTARGET: 6.3.1 12659 Alog Trunk:6: SET USER: Maury orig=1
2532246910mS CMTARGET: 6.3.1 12659 Alog Trunk:6: ADD USER: Maury depth=1 disallow_cw=0 dnd=0 real_call=1 group_call=0 type(CMNTypeUnknown) incl(0x0) excpt(0x0), allow_redir(1) remote=00000000
2532246911mS CMCallEvt: 0.50022.0 -1 BaseEP: NEW CMEndpoint f54a40c0 TOTAL NOW=3 CALL_LIST=1
2532246911mS CMCallEvt: 0.50022.0 -1 Maury.-1: NEW CMExtnEndpoint f54a40c0, Name=Maury, Extn=225, Phys Extn=225
2532246912mS CMTARGET: 0.50022.0 12659 Maury.0: ADD PRIMARY
2532246912mS CMCallEvt: 0.50023.0 -1 BaseEP: NEW CMEndpoint f54ca9f8 TOTAL NOW=4 CALL_LIST=1
2532246912mS CMCallEvt: 0.50023.0 -1 Alexis.-1: NEW CMExtnEndpoint f54ca9f8, Name=Alexis, Extn=221, Phys Extn=221

[furrerm]

What is your target in the ICR? Check the mobility tab on 225, and make sure that there is no internal twinning to 221 or 200.

Make sure 221 has no coverage for 225.

Look in system status, as this will indicate forwarding, etc.

When calls come in on the normal ICR, do they route correctly?

[mmarkowitz]

What is your target in the ICR? Check the mobility tab on 225, and make sure that there is no internal twinning to 221 or 200.

Make sure 221 has no coverage for 225.

Look in system status, as this will indicate forwarding, etc.

When calls come in on the normal ICR, do they route correctly?

The target in the ICR is 225. There is no fallback target.

I don't know what the second line is referring to for sure, but I suspect the answer is "no". When someone calls the auto-attendant and dials my extension, the other phone does not ring.

I see no forwarding in Status.

The normal ICR routes to extension 200, which goes to the AA. This works fine.

We route calls by hand and AA all day, none of that causes the receptionist phone to ring. Nor does the "ADD PRIMARY" line appear anywhere else in the logs.

[mmarkowitz]

I just checked, there's definitely no twinning or forwarding or twinning on the extension in question.