I agree, having things like "paging" show up in the CDR's makes it hard for customers to get meaningful data.
In addition to "summary" reports like total monthly outbound calls, etc I would love for "CDR" permissions to be available for users without having to grant superadmin access. This would be so management can run CDR reports on employees. -M >>> Josh Patten <[email protected]> 01/23/10 1:26 PM >>> Now that you ask, I'll elaborate a bit more. 1. There is often a need for department heads to compare their longdistance bill with individual callers within a department. Our longdistance provider uses PIN numbers on the telco side, so eachdepartment has a specific PIN number and get a long distance bill basedon that PIN. It would be nice for department heads to be able to loginto the web portal and retrieve their departments CDR's (group based?)for the billing period. 2. The current CDR, when used with park, MOH, directed call pickup,etc. etc. is an absolute mess. It's almost impossible to get any usefulinformation out of it. One of the reasons for this is we use polycomphones and an outbound SIP trunk to dial 4 digit to our Meridian Option61c via DMS100 PRI so all of those numbers appear as external outboundand inbound calls in the CDR. Perhaps a minumum number length thresholdwhen pulling CDR records for a report, or even better, perhaps a nestedcall path within the detailed report, such as: Step From To Start Total Duration Duration Action Status 1 5551234567 4321 15-Jan-2010 9:01:15 AM 1 minute, 43 seconds Call Pickup by 4123 Completed 2 5551234567 4123 23 seconds Placed On Hold Success 3 5551234567 ~~mh~ 20 seconds Retrieved From Hold Success 4 5551234567 4123 15 seconds Transfered to 84321 Success 5 5551234567 84321 45 seconds Call ended by remote party Success 1 4123 5553211236 15-Jan-2010 10:32:14 AM 5 minutes, 22 seconds Completed 2 4123 5553211236 5 minutes, 22 seconds Call ended by 4123 Success 1 5556344358 4987 15-Jan-2010 11:01:42 AM 1 minute, 10 seconds No answer, sent to voicemail Completed 2 5556344359 ~~vm~4987 1 minute, 10 seconds Call ended by remote party Success And, in addition, a simpler report for the department heads, preferablysortable by inbound and outbound calls: From To Start Total Duration Last Action Status 5551234567 4321 15-Jan-2010 9:01:15 AM 1 minute, 43 seconds Call ended by remote party Success 4123 5553211236 15-Jan-2010 10:32:14 AM 5 minutes, 22 seconds Call ended by 4123 Success 5556344359 4987 15-Jan-2010 11:01:42 AM 1 minute, 10 seconds Call ended by remote party Success Right now, as I said, it's a bit of a jumbled mess and not really in ausable state. I'm sure this could be done or at least improved upon. Raymond Dans wrote:Josh, Noticed your request forbetter CDRs/Reports. Can you be a bit more specific. A considerableamount of new information has been added to the CDR records in 4.2 aswell as new/changes to reports. Is there something in particular abouta report that you'd like see? Voice/Fax/Mobile: 613-763-3941/613-763-7742 [ Please consider the environment before printing this email ] mailto:[email protected]] On Behalf Of JoshPatten Sent: Friday, January 22, 2010 5:09 PM To: Lawrence, Scott AVAYA (BL60:9D30) Cc: sipXecs users Subject: Re: [sipx-users] Simplify, Simplify, Simplify Be ready for a mailing list flood :-P Here are a few things, and I'm sure some if not most are already inmotion and some of them may not fall within your guideline, call me outon them if they're out of the scope of your request: * Advanced audiocodes gateway configurations, such asmanipulation tables. * Better CDR's. Right now I'm having to get our on-staffprogrammer to write me out a parser to sift through all the CDR recordsto generate a comprehensive report. * Voice notification of new voicemails, not just email. Somepeople don't have data or SMS on their phones. * Auto Attendant Dial by name directory is currently just bad,namely due to the 10 second delay issue. * make backup and restore a little more comprehensive, such asmaking sure all SSL certs are in order. * Wildcard SSL certificates. * Bring back the remote call forwarding restriction, sometimesthere is a need to keep certain users from forwarding calls off-site. * Hunt group pickup code shortcut. A speed dial has to be usedfor hunt group pickup because users can't remember the entire *78XXXXpickup code. * Call pickup/hunt group pickup permissions. It is somewhatunnerving that anyone can set up a presence monitor on any extensionthey want to and intercept their calls. * Allow different alarms to be sent to different email addresses * (sipXconfig) Allow more than 20 phones/users to be displayedat one time. * For end users: allow a different phonebook in the web portalthan on the phone so the entire directory can be searched in the webportal but only a small departmental subset will be seen on the phone. * Better dial plans. The current ones are a bit watered down. * Transferring calls to park requires three button presses onPolycom handsets (transfer, blind, park button). Could this possibly bewhittled down? * If a Jabra or Plantronics headset with EHS adapters is usedon a phone with BLF then every time a BLF button shows a monitoredextension to be ringing, the headset also rings. Polycom and Jabra havebasically ignored me on this. I am almost 100% positive this has to dowith the "alerting" state with enhanced BLF. * I've had to write EFK's for Intercom, Group Page, Transfer ToVoicemail, and Blind Transfer on Polycom phones. Perhaps these could beincluded by default and turned on/off at the group phone level? * Allow for a pickup time shorter than 1 second for *78XXXXcall pickup. Users are used to the call immediately being picked up onolder systems. I have trained users to wait for the short "beep" soundbut sometimes they forget :-( * Voicemail quotas so the packrats will get rid of voicemailsfrom 5 years ago or archive them to their computer * 64 bit CentOS installation ISO. * Polycom config overrides upload. It's frustrating after afirmware update having annoyed users because their ringtone,background, etc. got reset. * Troubleshooting has got to become a bit easier. A scrollingCLI would definitely help. OK, that seems to be more than just a few. I'm sure there are more thatI'm not thinking about right now. I'm really glad to hear Avaya iscommitted to the project. Josh PattenAssistant Network AdministratorBrazos County IT Dept.(979) 361-4676 On 1/22/2010 3:23 PM, Scott Lawrence wrote: http://www.sipfoundry.org/ </[email protected]>
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
