Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

2033 Polycom Phone

Status
Not open for further replies.

Acoustech

Technical User
Jul 5, 2006
127
US
We purchased a new 2033 (our second Polycom phone). On OTM, when we set it as an 2033 template it thinks the phone is a 2001 and it doesn't work. We set the phone as a i2500 (which our other, working polycom is set to) and it only took audio in, but no one could hear us when we were speaking. Does anyone have any ideas on what this could be?
 
Does your system meet these requirments

The IP Audio Conference Phone 2033 is a full duplex, handsfree conference phone for the desktop, offering 360 degree room coverage.

The Nortel IP Audio Conference Phone 2033 is compatible with:


CS1000 (release 3.0 on)

BCM (release 4.0 onwards - Sep 2006)





This is a Signature and not part of the answer, it appears on every reply.

This is an Analogy so don't take it personally as some have.

Why change the engine if all you need is to change the spark plugs.


 
The 2033 is programmed as an i2001.

Patch MPLR19682 is required to be applied on a CS 1000 3.0/4.0 system. Install the patch prior to installing the 2033.

When configuring the 2033, enable handsfree by setting CLS=HFA.

You also need patch MPLR18688 on a CS 1000 3.0 system.
 
How are you guys so fast with responding? Ok, so I'm assuming the patch is applied as our last 2033 phone was installed by a Nortel Tech on our CS1000 and works fine. From the OTM it looks like HandsFree is enabled but I don't know if that's the same as CLS=HFA. Thanks for all your help!
 
If your other 2033 was installed as an "i2050", then it was NOT installed correctly. Handsfree is enabled in OTM is correct.
 
If the other one works you could try doing a
CPY 1 to the new TN if you can't get it to work any other way.

May not be the right set type, but if it works.


This is a Signature and not part of the answer, it appears on every reply.

This is an Analogy so don't take it personally as some have.

Why change the engine if all you need is to change the spark plugs.


 
Thx Ace, I suck at CLI. Would you be able to walk me through how to get there and which LD it is? (I've done it a handful of times) The Current, working 2033 has a tn of 65.15, DN 7680
 
I'm seeing conflicting info here, could you post the TNB of the working Polycom?

LD 20
REQ PRT
TYPE TNB
TN x x x x TN of the working polycom CUT and PASTE here


This is a Signature and not part of the answer, it appears on every reply.

This is an Analogy so don't take it personally as some have.

Why change the engine if all you need is to change the spark plugs.


 
I'd be thinking that it's an ip issue rather than a system issue if they already have a working set.
 
REQ: prt
TYPE: tnb
TN 017 0 00 00
DATE
PAGE
DES

DES POLYCM
TN 017 0 00 00
TYPE 500
CDEN 4D
CUST 0
WRLS NO
DN 7693 0 MARP
CPND
NAME CONF RM POLYCOM
XPLN 15
DISPLAY_FMT FIRST,LAST
AST NO
IAPG 0
HUNT
TGAR 1
LDN NO
NCOS 7
SGRP 0
SGRP 0
XLST
SCI 0
CLS CTD DTN FBD XFA WTA THFD FNA HTD ONS
LPR XRA AGRD CWD SWD MWD RMMD SMWD LPD XHD SLKD CCSD LND TVD
CFTD SFA MRD C6A CNID CLBD AUTU
ICDD CDMD LLCN EHTD MCTD
GPUD DPUD CFXA ARHD OVDD AGTD CLTD LDTD ASCD
MBXD CPFA CPTA DDGA NAMA MIND
MCRD
EXR0 SHL ABDA CFHD
USRD BNRD OCBD RTDD RBDD RBHD FAXD CNUD CNAD PGND FTTC CDMR
RCO 0
PLEV 02
CSDN
AACS NO
MLWU_LANG 0
FTR CFW 4
DATE 15 DEC 2005
 
The polycom TN 17 0 0 0 DN 7693 is a single line Analog phone, so they are not the same. The 2033 is an IP phone, do you need it to be an IP phone?


This is a Signature and not part of the answer, it appears on every reply.

This is an Analogy so don't take it personally as some have.

Why change the engine if all you need is to change the spark plugs.


 
That is very strange because the existing 2033 is actually an IP phone as far as i know... unless the tech somehow routed it out over an analog line. I would ideally like this new one to be an IP phone as well. This conference phone we have which is apparently an analog line can be moved all over the office and it works fine which suggests it's definitely an IP setup. How strange!
 
Also I tried the CPY 1 command and got this. I'm assuming it error'd out because it's listed as an Analog line (2500):

REQ: cpy 1
TYPE: 2500
SCH0099 2500?
TYPE: 500
CFTN 017 0 00 00
DES POLYCM

*** MAKE PRINTER READY ***
TN 017 0 00 01
DN 7692

NEW 500 TN 017 0 00 01 DN 7692

SCH5525

 
Are you sure you have the right TN, as the one you listed is an Analog phone and will not work as you discribed by plugging in anywhere you want. use the working phone to call the ATTN and ask her what DN you are showing.


This is a Signature and not part of the answer, it appears on every reply.

This is an Analogy so don't take it personally as some have.

Why change the engine if all you need is to change the spark plugs.


 
Ugh, apologies. It seems there are 2 phones in there, 1 in a small corner. Here it is:

TN 065 0 00 08 VIRTUAL USRD ULAD RTDD RBDD RB
TYPE I2001D FLXD FTT
CDEN 8D
CUST 0
ZONE 001
FDN 7690

TGAR 1VOUD C
LDN NO
NCOS 7
CPND_
SGRP 0G
RNPG 0
RCO
SCI 0
HUNT
SSU0
LNRS 16LHK 0
XLST
PLE
CLS CTD FBD WTA LPR MTD FNA HTA TDD CRPDACS NO
ITNA NO
DGRP
MLW
MWD LMPN RMMD SMWD AAD IMD XHD IRD NID OLD VCE DRG1ARP
CPND

POD DSX VMD CMSD SLKD CCSD SWD LNA CNDA
XPLN 15
CFTD SFD MRD DDV CNID CDCA MSID DAPA BFED RCBD
01 SCR 7737 0 MARP
ICDD CDMD LLCN MCTD CLBD AUTUD
NAME UNUSE
GPUD DPUD DNDD CFXD ARHD CLTD ASCD
XPLN 15

CPFA CPTA ABDD CFHD FICD NAID BUZZ AGRD MOAD
02 SCR 7837 0
AST
IAPG 0

AACS NO

ITNA NO

DGRP3
MLWU_LANG 0

DNDR 0

KEY 00 SCR 7694 0 MARP
17 TRN

CPND
12
13
14
15
16
17 TRN
18 AO6
19 CFW 16
20 RGA
21 PRK
22 RNP
23
24 PRS
25 CHG
26 CPN
27
28
29
30
31
DATE 21 JUN 2006
 
So try and copy that new TN you printed above to another Virtual TN and see if it takes.

REQ: CPY 1
TYPE: i2001
CFTN 65 8
TOTN <-- insert vacant VTN
DN <-- insert unused DN
 
definitely did that before. we're just going to attempt an RMA and see if it's a hardware issue.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top