Upgrading 2050 connecting to BCM

[Dloke]

I posted this originally in the Meridian forum - they suggested I go here...

I'm testing the rev 4 of 2050, and have installed it on a user's system. Everything connects fine to the BCM, but when I try to enter the user's DN, it says it's already assigned (which is the rev 1 2050 software already installed on the user's system). How can I get the new 2050 to use the user's existing DN? Thanks!

 

[jsaad]

de-register DN

 

[Dloke]

Actually, figured it out - since the Hardware ID is being used to determine the DN, I just copied the hardware ID from the profile of the rev 1 install to the profile of the rev 4 install, and I was able to use the user's existing DN.

Now I have a problem with the headset. The headset works fine with the system and the rev1 software, but when I try to use it with the rev 4, the headset flashed red twice, and I keep getting 'Need headset' when I try to switch to it. I know this type of headset works with rev 4 of 2050 (it's a Nortel USB Audio Adapter), but I can't get the 2050 software to recognize it. Any ideas?

 

[Dloke]

Never mind - figured it out. The 2050 software is very susceptable to low bandwidth - it looks like you need something more substantial than a 3G connection to your favorite cell provider. Also, the headset settings will reset for no apparent reason, making you go in and reselect your headset. This software is giving me a royal headache.

 

[curlycord]

I thought v4 was for Merdian PBX.

This is a Norstar forum, not BCM.

Here is the headache forum for future:

http://www.tek-tips.com/threadminder.cfm?pid=1361

=----(((((((((()----=
curlycord

http://www.curlycord.com