Hi there, I'm considering migration of my voicemail system from Cisco Unity to sipXecs. It has to be able to work with Cisco Callmanager 4. Fortunately, CCM 4 seems to provide a few simple hooks for that, as outlined in [ http://www.voip-info.org/wiki/view/Asterisk+Cisco+CallManager+Voicemail+Integration ]. In a nutshell, when it wants to send a call to voicemail, CCM will dial a designated extension (pilot number) and pass the original destination as RDNIS (which translates to Diversion or History-Info in SIP.) In turn, when the voicemail system is to communicate MWI to CCM, it can just dial one of two designated extensions on CCM (MWI on or MWI off) and pass the line number as the caller ID.
The fist part (CCM->voicemail) seems to me as easy as setting up a "middlebox" (e.g., Asterisk) that will receive calls to the pilot number, extract RDNIS and call the respective extension on SipXecs with the voicemail prefix. E.g., if CCM receives a call to 5678 and wants to send it to VM, it'll dial 101 on the box and pass 5678 as RDNIS, and the box will call 85678 on SipXecs. Should CCM pass no RDNIS to it, the middlebox can just call 101 (or whatever the vm extension is set to) on SipXecs. As for the second part of the problem, which is VM->CCM MWI, my only solution involving no modification to SipXecs source is this: Write a trivial HTTP proxy that will sit between the voicemail server and the status server, peek at MWI messages sent to /cgi/StatusEvent.cgi, and call CCM respectively (e.g., using the same Asterisk instance). Do you think there can be a way to do the same thing with less hackery and more sipXecs power? Thanks! Yar _______________________________________________ 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/
