Some Cisco issues

nextbgates95
Posts: 2
Member Since:
2009-07-14

Hello. I'm new to trixbox (running in a VM right now), but I've been following trixbox Without Tears, and it's been really helpful. I setup a Cisco 7941 with one extension. I don't have any major issues with the phone. However, there are a few minor annoyances. I've looked for solutions but I'm not exactly sure what to look for.

1) When Cisco phones are connected with Callmanager, there is a softkey enabled when an incoming call occurs. I believe it is called "iDivert" for Immediate divert. I'm not sure if there is a way to define a button like this using the softkey.xml file or not. Currently, when a call comes in, there are two buttons, "Answer" and "DND". Is there anyway to forward a call to voicemail (in this case, *2121) without picking up the extension?

2) MWI. I know there are lots of issues with Cisco MWI. I've found a solution or two for asterisk, but I haven't found any for trixbox. I'm running 8.3.1 firmware.

3) In the SEPmac.conf file, there are tags like :

x--serviceuri-cfwdall
x-cisco-serviceuri-pickup
x-cisco-serviceuri-opickup
x-cisco-serviceuri-gpickup
x-cisco-serviceuri-meetme
x-cisco-serviceuri-abbrdial

Is this a callmanager specific thing? Does anyone know what these URLs do? I would imagine they could be re-coded for trixbox/asterisk feature codes.



mulderlr
Posts: 15
Member Since:
2007-09-19
iDivert on Cisco 794X/796X with trixbox possible?

Bump... anyone?



Astrosmurfer
Posts: 643
Member Since:
2009-12-28
There aren't any softkey

There aren't any softkey options with Asterisk/trixbox so, no iDivert. It's one of the many "advantages" of Cisco's SIP firmware.

The MWI should work without issue for newer versions of trixbox. What version of trixbox are you using?



mulderlr
Posts: 15
Member Since:
2007-09-19
MWI

MWI works fine with trix 2.6.x.x for me as well as 2.8.x.x on Cisco 7960's running Cisco SIP firmware 8.8.0. A customer investigating a switch from CCM to trixbox is anxious about losing iDivert softkey though. Can Aastra phones be programmed in conjunction with trixbox to do an interactive call diversion? Meaning that once a phone starts ringing a key can be pressed to send a call to VM or somewhere else for that matter? This is akin to a cell phone going to voicemail as soon as I press my 'end' key for example.



SkykingOH
Posts: 9681
Member Since:
2007-12-17
This Cisco's description of

This Cisco's description of iDivert.

Quote:
You will find that Immediate Divert, a Cisco CallManager supplementary service, is available for general use within the system. Immediate Divert does not require the user to log in to have the iDivert softkey available on the phone.

The call that is being diverted can be in the call offering, call on hold, or call active state. The call can be incoming or outgoing. The person on the call that is being diverted will receive the greeting of the voice-messaging system of the person who diverted the call.

Immediate Divert coexists with the Cisco IPMA feature, Transfer to Voice Mail. For more information on IPMA, see Cisco IP Manager Assistant With Proxy Line Support.

Pressing the reject key during the ring state of the Aastra will send the call to VM.

You could easily setup an in call speed dial to do the same thing.

Does this address your requirements?

I have extensive experience replacing Call Managers with OST boxes. I suggest you work with a partner who has similar tangible, verifiable references.

--

Scott

aka "Skyking"



Astrosmurfer
Posts: 643
Member Since:
2009-12-28
I'm curious about your

I'm curious about your customers, mulderlr and Skyking. What is their reason for wanting to switch from Cisco Call Manager to trixbox? Call Manager seems way too young to be requiring forklift upgrades/replacement.



SkykingOH
Posts: 9681
Member Since:
2007-12-17
The cost of ongoing Cisco

The cost of ongoing Cisco support is very high for some users of UCM.

The current client we are converting has 450+/- extensions, 11 edge routers with SRST and one core router for the PRI. The versions of UCM they were running is EOL/EOS and the customer was looking at a $60,000 bill for the upgrade plus 3 years of 8/5 Smartnet.

We where able to reuse all of the phones and the routers and save them a bit over 50% over the same three year period.

--

Scott

aka "Skyking"



mulderlr
Posts: 15
Member Since:
2007-09-19
same reasons here basically

Customer is tired of the complete vendor lock in of cisco ip telephony when there is so much more to that world. Probably has over $30K invested in 100 phone system running on CM 4.x and is just tired of the Nickle and dime for every feature you want to add along the way from Cisco and expensive support contracts.

Converting from a CM PBX to a trixbox ce means that they can start out with all their same 79x0 phones, and through attrition start switching to other vendors phones over time (such as aastra or polycom), meanwhile averting skyrocketing costs of maintaining PIX firewalls and cisco VPNs, CM itself, smartnet, etc., etc., etc.. They'll have about 98% as good if not better experience for half the cost. IAX protocol on trixbox will play nicer with firewalls, be easier to QoS it and just hopefully make their whole IP Telephony world better. Not in every way naturally, but enough to make it worth switching. :-)



nextbgates95
Posts: 2
Member Since:
2009-07-14
As this question is a year

As this question is a year old, I've come up with a much better solution to Cisco phone support on any Asterisk implementations.

The chan_sccp-b project essentially emulates CallManager (What is it even called anymore? CM, Unified Communications Manager :P) and uses the existing SCCP protocol. You get all the features, MWI, and iDivert included. The only thing that's shaky right now is conferencing, but they're working on that. I think there is support for conferencing in Asterisk 1.6.

Hope this solves some problems.

http://chan-sccp-b.svn.sourceforge.net/
http://chan-sccp-b.sourceforge.net/doc/



mulderlr
Posts: 15
Member Since:
2007-09-19
aastra ring state

So, I invested in some aastra's to use with trixbox - big improvement over cisco SIP functionality with asterisk/trixbox. However, with all setup-aastra-xml scripts active on a 57i (fw 2.6.09.66), trixbox 2.6.2.3 (yum and trixbox module updated), during incoming call on aastra, there is not a reject softkey. There IS, however, an "ignore" softkey, but this simply silences the phone and doesn't divert the call immediately to voicemail, but to the caller the phone seems to continue to ring until normal asterisk timeout destination to voicemail happens. What the ....? Someone has to have encountered this before.

Scott (SkykingOH), how have you handled cisco customers "addictions" to this seemingly "cisco only" nonsense?



Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.