Polycom Soundpoint 650 and 670

[Anonymous]

I am going to run these phones behind a Netvanta 4430 (enhanced firmware). I do not have a Netvanta 7000 series PBX at this time. We will be using the PBX or Centrex features of a Nortel/Genband CS1500 soft switch (we are a telco). When I just program the phone locally, it is very limited on what I can do with it and I can not even upgrade software. I called Polycom for support but I have to get certified first before I can use it. I am going to go ahead and do that but it will take a little while.

We do have a local ft/tftp server already running.

My question is this: does anybody have a config file pre-built I can use or any tips? Anybody ever used these W/O a 7000 series PBX?

[Anonymous · Accepted solution]

I am moving this post to the Polycom area so it will get more visibility.

These documents and links from Polycom’s site may help:

http://www.polycom.com/global/documents/whitepapers/configuration_file_management_on_soundpoint_ip_p...

http://support.polycom.com/global/documents/support/setup_maintenance/products/voice/How_to_Provisio...

http://support.polycom.com/PolycomService/support/us/support/voice/soundpoint_ip/soundpoint_ip650.ht...

http://support.polycom.com/PolycomService/support/us/support/voice/soundpoint_ip/soundpoint_ip670.ht...

If you use Polycom phones with a NetVanta 7100 it will generate all of the proper configuration files automatically when creating a new user.  Here is our guide on troubleshooting Polycom phones with the Netvanta 7100:

Thanks,
Matt

[Anonymous]

Those are helping. I am on page 4 of "How to provision a Polycom Phone" and am stuck on where to insert the MAC address. Do I overwrite something or do I go in the line below? The instructions do not have a pic or explain this at all.

[Anonymous]

Typically you will need to save the results of this file into <macaddress>.cfg (ex: 0004f210dfae.cfg).  This file references the other files the phone will need to download to build its complete configuration containing the registration info and any other parameters needed.  For example, in the NetVanta 7100 we reference the <extension-macaddress>.cfg file (ex: 2060-0004f210dfae.cfg) along with several others from within the <macaddress>.cfg file.  In our case the the <extension-macaddress>.cfg file configures the registration information and any other specific parameters needed for this particular phone.  I attached these files to serve as an example, but these are built for a particular version of firmware and specifically for a NetVanta 7100.  Is Nortel/Genband able to offer any help on a suggested configuration?

Thanks,
Matt

[Anonymous]

Nortel/Genband does not help at all with other vendors equipment. It would be nice if they did though. As far as the <macaddress>.cfg file goes, is that a file that I create or should that be a download from Polycom's website? I downloaded the 3.2.6 combined and split files, but it was not in there. I downloaded that version because Adtran told me that was the latest they supported on my phones when using them with a NV7100. Even though I do not have one at this time, I know we might get one down the road and I want to be ready.

[Anonymous]

Thank you for yours by the way, I might be able to just re-use those with my specific information.

[Anonymous]

The macaddress.cfg file is the one you need to create.

Thanks,

Matt

[Anonymous]

I got everything working pretty much. I updated firmware, bootrom and it pulls the config files off ftp server. The only issue I am having now is dialing long distance numbers. Is there a dial plan or something I need to set in the config file?

[Anonymous]

The dial plan for the phone needs to be set in one of the config files.  It needs to match the dial plan of the soft switch you are using.  Here is an example from the 2060-0004ff210dfae.cfg file in the attachment above:

<dialplan>

      <digitmap dialplan.1.digitmap="0|911|9,911|[1-8]xxx|9,[2-9]xxxxxx.T|9,[2-9]xx[2-9]xxxxxx|9,[0-1][2-9]xx[2-9]xxxxxx|9,011xxx.T|*[2-9][0123456789*].T|*1xxx|#xx.#|xx.#|**xxxx|##xxxx"/>

   </dialplan>

Thanks,
Matt

[Anonymous]

Ok thanks for that info. I found a nice link on Polycom's website regarding dial plans that need to dial 9 to get out. That seems to be where our long distance problems occur. Does it matter what config file I put this in? I was just going to do one of my common files that will affect everything across the board.

[Anonymous]

As long as it is present in a file that the phone loads, technically it should not matter.  The macaddress.cfg file tells the phone the order to load files in.  Just keep in mind if the same parameter is configured in different places the one that is downloaded by the phone last overwrites the previous settings.

Another piece of information worth sharing is that when the digits dialed on the phone match something in the phone dial plan exactly the call will be sent immediately.  If it matches part of a dial plan entry but is not exact the user will have to add a # to the end of the dial string, manually hit the Dial softkey, or wait for a timeout for a call to be sent.  If it does not match anything the call will be rejected by the phone.  Once the call gets sent from the phone to the next device it is usually an option to manipulate the dialed digits (DNIS) if they are not in a format that you want.  For example if all the users dialed a 9 before a 10 digit number but the dial plan of the SIP device the phone sent the call to did not accept calls with a 9 in front, the 9 could be stripped with a DNIS substitution in the SIP device before routing the call on. It depends on the device being used, but that feature is supported in our AOS Voice products like the NetVanta 7100 as well as many other vendors.

Thanks,

Matt

[Anonymous]

How does this look for a dial-plan? I just put as much down as I could. Figured it would not hurt to have more than what I need. Does the spacing look correct?

0|911|9,911|[1-8]xxx|9,[2-9]xxxxxx.T|9,[2-9]xx[2-9]xxxxxx|9,[0-1][2-9]xx[2-9]xxxxxx|9,011xxx.T|*[2-9][0123456789*].T|*1xxx|#xx.#|xx.#|**xxxx|##xxxx[2-9]11|0T|011xxx.T|[0-1][2-9]xxxxxxxxx|[2-9]xxxxxxxxx|[2-9]xxxT|9,[2-9]xxxxxxT|9,[2-9]xxxxxxxxxT|

9,1[2-9]xxxxxxxxx

[Anonymous]

I would suggest enforcing the dial plan on the phone to match what is acceptable to the softswitch the phones are talking to.  The original dial plan from the file that I quoted above is good for dialing 4 digit extensions, 7 digit numbers with a preceding 9, 10 digit numbers with a preceding 9, and a couple other exceptions.

Thanks,
Matt