Cisco is Polycom's largest customers - not such a surprise.
-Original Message-
From: sipx-users-boun...@list.sipfoundry.org
[mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Robert B
Sent: Sunday, November 22, 2009 4:45 AM
To: Matt White
Cc: sipx-users@list.sipfoundry.org
Subjec
polycom is what we use as our "gold" standard.
LLDP is not a big one for us, we can just as easily autoconfigure the VLAN via
DHCP.
-M
>>> Robert B 11/22/09 7:45 AM >>>
That being said, what does the community feel is the best handset for
sipXecs implementations?
Polycom is great -- but th
I too do voice VLAN separation and I don't use LLDP-MED on my ProCurve
switches and I don't have any problems with Polycom auto-config. sipX
has phone configuration groups which allow you to set location specific
things such as VLAN tagging when the configuration is downloaded from
the FTP serv
Dale,
In a subsequent email to the group, I found that the vast, vast majority
of resources are tied up in Java. Also, due to a strange configuration
in Sun's default jvm.cfg, java tried to allocate an absurd amount of
memory if the server has 2gb or more RAM.
OpenVZ is a container-based, not
On Mon, 2009-11-23 at 00:01 +0800, Sen Heng wrote:
> Basically they has three component to provide service, SSL7
> Gateway(PSTN) + ENUM Server (PSTN/SIP number lookup) + Freeswitch (Sip
> proxy)
>
> Provider ask me to use SIP trunk connect Freeswitch and Sipxecs.
>
>
>
> My question is Sipxec
On Sat, 2009-11-21 at 06:56 -0600, Robert B wrote:
> My situation is that I am attempting to overcome the non-existence of
> "true" multi-tenant support (not meant as an insult) via running
> multiple sipXecs PBXs inside of OpenVZ containers. I was drawn to
> sipXecs over Asterisk for a variety
Hi,
I am going to connect Sipx to one of our provider to allow sip phone call to
PSTN. Our service provider use all open sourced SS7-to-SIP solution.
Basically they has three component to provide service, SSL7 Gateway(PSTN) +
ENUM Server (PSTN/SIP number lookup) + Freeswitch (Sip proxy)
P
Tony,
LLDP-MED is extremely important for a handset. If one doesn't support
it, it means you have to take exactly the steps you mentioned -- hand
configuring every device! I'll never do that again. Can you imagine
having to do that with fifty or more phones? I have, and it's a
nightmare. LLDP
LLDP support is coming in version 3.2 of the firmware... we're just
going to wait for versoin 4.2 of sipXecs to run it.
Re:MoH there are 2 or 3 ways to do it... I'm sure Worley has his
favorite though. :-)
-Original Message-
From: sipx-users-boun...@list.sipfoundry.org
[mailto:sipx-user
OK, thanks. If I see issues I'll speak up.
On Sun, Nov 22, 2009 at 8:17 AM, Scott Lawrence
wrote:
> On Sat, 2009-11-21 at 08:44 -0500, Tony Graziano wrote:
> > Updating : sipxconfig-ftp
> > [163/361]
> > error: %post(sipxconfig-ftp-4.0.4-017289.i386) scriptlet failed, exit
> > status 1
>
On Sat, 2009-11-21 at 08:44 -0500, Tony Graziano wrote:
> Updating : sipxconfig-ftp
> [163/361]
> error: %post(sipxconfig-ftp-4.0.4-017289.i386) scriptlet failed, exit
> status 1
>
>
> The package is installed. Is this cosmetic or should I be concerned?
Unless your phones start having t
I got the same.
Tony Graziano pisze:
> Updating : sipxconfig-ftp[163/361]
> error: %post(sipxconfig-ftp-4.0.4-017289.i386) scriptlet failed, exit
> status 1
>
> The package is installed. Is this cosmetic or should I be concerned?
>
> --
> ==
That being said, what does the community feel is the best handset for
sipXecs implementations?
Polycom is great -- but the only issue for me is their lack of support
for LLDP-MED. Surprised the hell out of me that Polycom would only
support Cisco's proprietary CDP.
Aastra -- nice handsets, pro
13 matches
Mail list logo
