I think Cisco-polycom never worked under sipx properly.8.2 was the best bet
(dont remember if below issue was seen or not) RgdsNitin
Date: Sun, 20 May 2012 16:05:43 -0400
From: beck...@sunyulster.edu
To: sipx-users@list.sipfoundry.org
Subject: Re: [sipx-users] Polycom calling Cisco issue (XX-8762)
Nitin,
Didn't 8.2 still have transfer issues> That is, you could
transfer and dial the destination, however, you could not complete
the transfer until the other UA answered.
signature
Jesse Becker
Technical
Manager
Office of Information
Technology
Network+ | Linux+ Certified Professional
ellucian @
SUNY Ulster
491 Cottekill Road, Stone Ridge, NY 12484
Tel 845-687-5064 | Fax 845-687-5105
beck...@sunyulster.edu | www.sunyulster.edu
Open or check
the status of a ticket by visiting Helpdesk Online
Look up answers to
frequently asked questions by visiting the Knowledge
Base
On 05/20/2012 09:29 AM, Nitin Mirchandani wrote:
Downgrade to 8.2 version - It will work.
8.3 onwards - Security prevents calling Polycom<>Cisco
Date: Sun, 20 May 2012 06:09:24 -0400
From: mpic...@ezuce.com
To: sipx-users@list.sipfoundry.org
Subject: Re: [sipx-users] Polycom calling Cisco issue
(XX-8762)
Yea the actual problems turned out to be much deeper than
this... such as they cisco phones won't take calls from
servers they aren't registered to (this is why single server
installs worked but HA systems tended to fail).
There are still a couple other issues we're trying to
work through for a customer who would like to keep a few
thousand of these phones...
Mike
On Sun, May 20, 2012 at 12:58 AM, Becker, Jesse
<beck...@sunyulster.edu>
wrote:
Josh,
This issue is why Sen and I gave up on the interop of
the Cisco Plus profiles in 2009. Sen and i put in a lot
if effort to getting the 7906 and 79x1 series phones to
fully work with SipX. The latest patch allowed full
provisioning, however we found that each version of the
Cisco SIP firmware had different issues. The earlier
versions had issues with transferring and the message
waiting light. The later versions still had issues with
blind transfers, however, MWI worked. We thought we
were moving forward, however later discovered the issue
that cisco and polycoms were no longer able to call each
other. That's when I called it quits and stopped trying
to make it work.
On May 5, 2012 12:12 AM, "Josh
Patten" <jpat...@ezuce.com>
wrote:
For those of you who have mixed Cisco/Polycom
environments and want to call from Polycom to
Cisco, here is a temp workaround until something
better can be devised:
http://track.sipfoundry.org/browse/XX-8762
--
Josh Patten
eZuce
Solutions Architect
O.978-296-1005
X2050
M.979-574-5699
http://www.ezuce.com
_______________________________________________
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/
--
Michael Picher, Director of Technical Services
eZuce, Inc.
300 Brickstone Square
Suite 201
Andover, MA. 01810
O.978-296-1005 X2015
M.207-956-0262
@mpicher <http://twitter.com/mpicher>
www.ezuce.com
------------------------------------------------------------------------------------------------------------
There are 10 kinds of people in the world, those who
understand binary and those who don't.
_______________________________________________
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/
