Missed call log button in a Key system environment

[nurban]

Here's an issue that came up, and we've since been able to find a resolution; however, if anyone has dealt with this before and has an alternative solution, we're all ears!

System: R7.0(12) Essential
Trunks: 56 Centrex trunks. 5 digit dialing within the university, dial 9 to dial external numbers once on a trunk (it would cost the customer in excess of 100k to put in a PRI)
Phones: 5410's and 20's
Environment: University

We replaced a legacy system with an IP Office. The customer has numbers assigned to each phone, so we built incoming line groups that were unique for each trunk and added incoming call routes pointing to the proper phones. On each phone we then added both call appearances and line appearances. Call appearance buttons for intercom, paging, etc... line appearances so that each user could grab their assigned centrex number when making outbound calls.

The system functions properly, and very similarly to their old system but the missed call log button doesn't work.

Through testing, we removed the line appearance buttons and the missed call log button began working without issue. To accomplish the proper line selection for outbound calls, we built short codes that accessed the proper outbound dial group, then added buttons back on their phone depicting the number with a dial action and the short code.

A few issues do exist - some of the phones share numbers (lab type setting) and if someone's on the phone using the trunk assigned to the lab, others in the lab do not know by a visual indication on the phone - only when they dial out do they get a notification that the trunk is in use. Also, on inbound calls in this scenario we had to build hunt groups to ring the multiple sets for the log to work properly.

Our question is - call log is a basic feature of many systems; and in legacy situations like this where the system needs to function as a key system, there has to be a way for the missed call log to function properly without a bunch of workarounds... what are we missing?


IPO Implement
ACSS

 

[GhostZman]

I am having a similar issue. I have a test unit setup in Partner mode. I have 3 phones in key mode all set to ring. If I call in and answer from any extension , all the phones have the call show up in the call log. If I call in and hang up after 4 rings, it doesn't show up as missed call. Also, the call log doesn't seem to seperate inbound and outbound calls, it just seems to lump them in as one big batch regardless.

 

[tlpeter]

Don't use line appearances.
Use user shortcodes to use the right Centrex, that is what you need to do.


BAZINGA!

I'm not insane, my mother had me tested!

 

[IPGuru]

IPO is not a key system
trying to make it look like one will always end in tears

program with user short-codes to select the correct lines
you could use ARS & allow one line group to fall back to another to prevent line blocking but that would affect the centrex.
otherwise when trying to dial out on a line that is already in use the user will get "Waiting for line" on the display

Computers are like Air conditioners:-
Both stop working when you open Windows

 

[nurban]

That's what I was afraid of... and exactly how we have it programmed currently. Perhaps as they migrate more features from the BCM this'd be one area they address. We have a ton of customers in small office environments where taking away their line appearances would frustrate them.


IPO Implement
ACSS

 

[tlpeter]

People should grow up and live in the "now" instead of the 1980's
Key systems are going away and i am very glad it is!

Why would you need a line appearance when you have one channel?
This is the case right?

Then program two appearances and reserve the last one.
Then program a user shortcode for using the right centrex line.
This way all the features on the IPO will work fine.
Using line appearances will stop this features from working.


BAZINGA!

I'm not insane, my mother had me tested!