cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
most_ahdy
Contributor
Contributor

Polycom 650 Bottom Map misfunction

Jump to solution

Dears,

       I have Polycom 650 with firmware version 3.2.7 and BootRom 4.3.1.0440

I mapped the bottom line extension "the first two" and the remaining to speed dial "using GUI"

But the bottoms does not mapped correctly in the phone, as it does not mapped completely, sometimes it map only 4 bottoms and after rebooting in maps 5 bottoms, and it happen randomly after each reboots.

kindly find the output of show version for NV7100:

NV7100#show version

ADTRAN, Inc. OS version R10.3.1.E

  Mainline Version: ENM.12.023

  Checksum: BCD6CB6A

  Built on: Tue Sep 25 16:22:58 2012

  Upgrade key: ec41708db482a5d1a3a6ce163ce0ec36

Hardware version 10A

Boot ROM version A2.06.B1

  Checksum: E213

  Built on: Thu Jun 17 10:50:21 2010

Copyright (c) 1999-2012, ADTRAN, Inc.

Platform: NetVanta 7100, part number 1200796E1

Serial number LBADTN1032AK294

Flash: 33554432 bytes  DRAM: 134217728 bytes

NV7100 uptime is 1 weeks, 6 days, 7 hours, 31 minutes, 40 seconds

slot 0, DSP 1

  DSP software version: G2.R10.3.0.6a

  DSP hardware version: Freescale MSC7119

  Total channels: 30

System returned to ROM by External Hard Reset

Current system image file is "NV7100A-R10-3-1-E.biz"

Primary boot system image file is "NV7100A-R10-3-1-E.biz"

Backup boot system image file is "CFLASH:/NV7100A-A4-10-00-E.biz"

Primary system configuration file is "NONVOL:/startup-config"

NV7100#


ThanKs,

Mostafa Aly

Labels (1)
0 Kudos
1 Solution

Accepted Solutions
Anonymous
Not applicable

Re: Polycom 650 Bottom Map misfunction

Jump to solution

Looks like the issue was the speed dials being duplicate numbers in the system directory, which the Polycom phone cannot allow.. If you look at this thread, customer had similar issue:  https://supportforums.adtran.com/message/5764#5764

I looked at your before modification file and I see alot of duplicate issues with the custom entries and directory entries. The work around was to prepend the internal speed dial numbers with a 9 that will be stripped by the 7100.

Hope that helps. Have a great day!

-Mark

View solution in original post

0 Kudos
7 Replies
Anonymous
Not applicable

Re: Polycom 650 Bottom Map misfunction

Jump to solution

Mostafa,

Is this happening to all the 650 phones you have or just one 650 phone?

From the cli in enable mode do the following and post results here:

show file cflash Polycom/4001-0004f23769dd.cfg

Where 4001 is the extension and put your MAC address where the one I have is.

-Mark

Re: Polycom 650 Bottom Map misfunction

Jump to solution

I have just one 650 phone.

Kindly find the output of "show file cflash Polycom/4001-0004f23769dd.cfg"

NV7100#show file cflash Polycom/103-0004f23a0377.cfg

Using 2968 bytes

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<!-- AOS GUI Generated Configuration File -->

<!-- Generated from AOS GUI on 01/20/2013 10:58:55 GMT+0200 -->

<phone1>

   <reg reg.1.displayName="Secretary Floor 1" reg.1.address="103" reg.1.label="103" reg.1.type="private" reg.1.auth.userId="103" reg.1.auth.password="1234" reg.1.server.1.address="10.10.20.1" reg.1.server.1.transport="DNSnaptr" reg.1.lineKeys="3" reg.1.callsPerLineKey="2" reg.2.displayName="Line.1" reg.2.address="Line.1-aDtN-103" reg.2.label="Line.1" reg.2.type="shared" reg.2.auth.userId="Line.1-aDtN-103" reg.2.auth.password="1234" reg.2.server.1.address="10.10.20.1" reg.2.server.1.transport="DNSnaptr" reg.2.lineKeys="1" reg.2.callsPerLineKey="2" reg.3.displayName="Line.2" reg.3.address="Line.2-aDtN-103" reg.3.label="Line.2" reg.3.type="shared" reg.3.auth.userId="Line.2-aDtN-103" reg.3.auth.password="1234" reg.3.server.1.address="10.10.20.1" reg.3.server.1.transport="DNSnaptr" reg.3.lineKeys="1" reg.3.callsPerLineKey="2" reg.4.displayName="Line.3" reg.4.address="Line.3-aDtN-103" reg.4.label="Line.3" reg.4.type="shared" reg.4.auth.userId="Line.3-aDtN-103" reg.4.auth.password="1234" reg.4.server.1.address="10.10.20.1" reg.4.server.1.transport="DNSnaptr" reg.4.lineKeys="1" reg.4.callsPerLineKey="2" reg.5.displayName="Line.6" reg.5.address="Line.6-aDtN-103" reg.5.label="Line.6" reg.5.type="shared" reg.5.auth.userId="Line.6-aDtN-103" reg.5.auth.password="1234" reg.5.server.1.address="10.10.20.1" reg.5.server.1.transport="DNSnaptr" reg.5.lineKeys="1" reg.5.callsPerLineKey="2"/>

   <call>

      <serverMissedCall call.serverMissedCall.1.enabled="0" call.serverMissedCall.2.enabled="1" call.serverMissedCall.3.enabled="1" call.serverMissedCall.4.enabled="1" call.serverMissedCall.5.enabled="1"/>

   </call>

   <dialplan>

      <digitmap dialplan.1.digitmap="[1,2,5]xx|9,1xx.T|**xxxx|xx.#|#xx.#|*1xx|0|911|9,911|9,[2-9]xxxxxx.T|9,03xxxxxxx|40|9,[2-9]xxxxxxx|9,0[4-6]xxxxxxxx|9,0[8-9]xxxxxxxx|9,057xxxxxx.T|9,015xxxxxx|9,013xxxxxxx|9,01[0,1,2]xxxxxxxx" dialplan.2.digitmap="911|[2-9]xxxxxx.T|[2-9]xx[2-9]xxxxxx|[0-1][2-9]xx[2-9]xxxxxx|011xxx.T|xx.#|0.T|[2,9]xxxxxx.T|[2,9]xxxxxxx|03xxxxxxx|1xx.T|0[4-6]xxxxxxxx|0[8-9]xxxxxxxx|057xxxxxx.T|015xxxxxx|013xxxxxxx|01[0,1,2]xxxxxxxx" dialplan.3.digitmap="911|[2-9]xxxxxx.T|[2-9]xx[2-9]xxxxxx|[0-1][2-9]xx[2-9]xxxxxx|011xxx.T|xx.#|0.T|[2,9]xxxxxx.T|[2,9]xxxxxxx|03xxxxxxx|1xx.T|0[4-6]xxxxxxxx|0[8-9]xxxxxxxx|057xxxxxx.T|015xxxxxx|013xxxxxxx|01[0,1,2]xxxxxxxx" dialplan.4.digitmap="911|[2-9]xxxxxx.T|[2-9]xx[2-9]xxxxxx|[0-1][2-9]xx[2-9]xxxxxx|011xxx.T|xx.#|0.T|[2,9]xxxxxx.T|[2,9]xxxxxxx|03xxxxxxx|1xx.T|0[4-6]xxxxxxxx|0[8-9]xxxxxxxx|057xxxxxx.T|015xxxxxx|013xxxxxxx|01[0,1,2]xxxxxxxx" dialplan.5.digitmap="911|[2-9]xxxxxx.T|[2-9]xx[2-9]xxxxxx|[0-1][2-9]xx[2-9]xxxxxx|011xxx.T|xx.#|0.T|[2,9]xxxxxx.T|[2,9]xxxxxxx|03xxxxxxx|1xx.T|0[4-6]xxxxxxxx|0[8-9]xxxxxxxx|057xxxxxx.T|015xxxxxx|013xxxxxxx|01[0,1,2]xxxxxxxx"/>

   </dialplan>

</phone1>NV7100#

Anonymous
Not applicable

Re: Polycom 650 Bottom Map misfunction

Jump to solution

Not sure if you have tried this but default the phone and delete config file and see it keeps doing it.

Go to the user account that has the 650 assigned to him.

Change the phone type to virtual so that you don't have to delete user.

Save changes.

Then go to the 0004f23a0377 phone config file and delete it.

Then go back to user accounts and open the user again.

Change phone type to sip and click apply.

Go back to user and click edit config button.

enter MAC and set phone type and reconfigure buttons. save changes.

Choose no if it asks you to resync the phone.

Go back to user and make sure phone type is set to SIP and proper MAC address of phone.  save changes

Then go to the physical 650 phone, do a 468* at the same time and hold. then enter 456 to default the phone.

Let me know what happens.

-Mark

Re: Polycom 650 Bottom Map misfunction

Jump to solution

Hi Mark,

   I tried your above suggestion but with no success, but I modified the 0004f23a0377-directory.xml file to not include the <!--Directory--> entries and include only <!--Custom--> entries as attached.

and the problem solved totally.

Please note that the this IP650 phone has expansion module.

Do you think this is a bug.

Thanks,

Mostafa Aly

Anonymous
Not applicable

Re: Polycom 650 Bottom Map misfunction

Jump to solution

Looks like the issue was the speed dials being duplicate numbers in the system directory, which the Polycom phone cannot allow.. If you look at this thread, customer had similar issue:  https://supportforums.adtran.com/message/5764#5764

I looked at your before modification file and I see alot of duplicate issues with the custom entries and directory entries. The work around was to prepend the internal speed dial numbers with a 9 that will be stripped by the 7100.

Hope that helps. Have a great day!

-Mark

0 Kudos

Re: Polycom 650 Bottom Map misfunction

Jump to solution

Hi Mark,

   I replicated this issue in a IP 601 phone , and after adding the 9 before speed dial extension , this problem solved totally, in both 601 and 650 with one expansion module.

so it is a duplicating number in system directory issue.

Thank you Mark for your information.

Mostafa aly

Anonymous
Not applicable

Re: Polycom 650 Bottom Map misfunction

Jump to solution

Glad we got it resolved and thanks for marking the post as answered! Have a great week!

-Mark