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 server. All you have to do is set option 66 in your DHCP server to the address of your sipX server and the phone will do the rest once you configure it in sipX and the phone has downloaded it's configuration files.
The only merit I can see for LLDP-MED in this case is if you have users that move their phones to different locations with different VLAN configurations constantly. Adding a VLAN setting to a group of phones is all of about 5 mouseclicks. The Polycom configuration engine within sipX is pretty comprehensive so just about any standard Polycom setting is available to configure within sipX. Polycom has sipx-users-requ...@list.sipfoundry.org wrote: > Subject: > Re: [sipx-users] Question re: handsets > From: > Robert B <d...@spudland.com> > Date: > Sun, 22 Nov 2009 08:03:45 -0600 > To: > Tony Graziano <tgrazi...@myitdepartment.net>, > sipx-users@list.sipfoundry.org > > To: > Tony Graziano <tgrazi...@myitdepartment.net>, > sipx-users@list.sipfoundry.org > > > 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 makes it easy. We provision the phone in the PBX and > plug it in. All done! > > I always like to put my phones on isolated VLANs. On HP ProCurve > networking kit, you just enabled LLDP, tell the switch which ports my > phones are on, and then plug in the phone. The Aastras and Linksys > phones *just work*. They get their voice VLAN and the pass-through > network ports remain untagged. It's really, really time-saving. It's > equally as simple with CDP on Cisco switches, but you know Cisco -- > they love to do things their own way. > > -- Robert > > > Tony Graziano wrote: >> While it's nice to have all these capabilities, I don't see how it >> matters. Don't take this the wrong way. LLP-MED offers: >> >> * Network topology-A network management system (NMS) can >> accurately represent a map of the network topology. >> * Inventory-A management system can query a switch to learn about >> all the devices connected to that switch. >> * Emergency services-Location of a phone can be determined by the >> switch port to which it is connected. >> * VLAN configuration-The switch can tell the phone which VLAN to >> use for voice. >> * Power negotiation-The phone and the switch can negotiate the >> power that the phone can consume. >> >> sipx has 911 calling based on location (by branch in upcoming 4.2). >> Polycom and other phones) can be programmed for a 911 gateway in the >> event of a proxy failure, which IMO is even better, because the >> dependencies are less. >> When I deploy a phone on a vlan, we set the vlan on the phone. POE >> negotiates the power. I just use a good POE switch (procurve) that >> has a more than generous power budget and does basic L3 routing. >> >> I'm more concerned about the feature set, useability, manageability >> of the phone config via sipxconfig, and of course, vendor (phone >> manufacturer) support. >> >> I don't think NMS or Inventory capabilities matter much. sipx has >> discovery tools to find the phones and devices and there is work >> ongoing in 4.2 to expand this and auto provision phones without a >> user account. My network monitoring tools can find and map my >> devices, whether they be phones or not (Nagios, etc.). > > > > ------------------------------------------------------------------------ > > Subject: > [sipx-users] ss7 gateway+ENUM+Sipx > From: > "Sen Heng" <he...@tcd.ie> > Date: > Mon, 23 Nov 2009 00:01:20 +0800 > To: > <sipx-users@list.sipfoundry.org> > > To: > <sipx-users@list.sipfoundry.org> > > > > > 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) > > Provider ask me to use SIP trunk connect Freeswitch and Sipxecs. > > > > My question is Sipxecs already build ENUM dialing already, so should > I ask for direct point to their ENUM server rather than SIP trunk to > Freeswitch ? > > http://sipx-wiki.calivia.com/index.php/How_to_configure_ENUM_dialing > > > > Thanks in Advance, > > Sen > > > > > > ENUM Server: http://www.voipuser.org/forum_topic_13946.html > > ------------------------------------------------------------------------ > > _______________________________________________ > sipx-users mailing list sipx-users@list.sipfoundry.org > 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/ _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org 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/
