atcomsystems.ca/forum Forums TDM Business Telephone Systems NEC Telephones & Systems 2000IPS Call Pickup Group Issue

Having an issue with a group call pickup and just wanted to get some fresh eyes and ideas.

Set up a group call pickup with four extensions. Group pickup works on three of the extensions, but it will not work on one extension. The other members of the group cannot pickup calls to that extension. I don't know why; same tenant, class of service, etc.

Checked the pickup group with 163 and it scrolls through all the extensions and ends properly. Tested calling other extensions and can be picked up, just can't be picked up if I call the one extension.

Anyone got an idea????

It should work. I would CCC out the current data & re-enter it.

Did you delete and rebuild any of the extensions?

If so, blow away the pickup group and rebuild it.

Deleting a member of a hunt group or a pickup group sometimes makes a hole in the group, and calls fall out.

The customer was redoing all of their pickup groups so I made a CSV file with all the new pickup groups in the switch. I did a LEN listup of the switch, then modified the listup for command 160 and set all extensions from the LEN listup (including virtuals) to CCC and ran it in MACH script. I ran the CSV that I had built with all the pickup groups and verified the groups with 163. This is the only pickup group that is giving me grief.

Instead of using 163 , do it manually , using 160
eg for a pickup group with exts 300,301,302,303
it should look like this

160>300:301
160>301:302
160>302:303
160>303:300

163 sometime looks ok when it is not.
Also pickup groups are sometimes affected by other exts that point at the group when they should not , for the above example if you also found
160>306:302 , it may cause a problem with the group.

I would run a sniff of all exts in cm 160 and check for other exts pointed at the group.
To run a sniff , in the script use 160 in first col , ext in 2nd and then do a get 2nd data