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...
I'm almost done with my testing of the 2050 software, but I'm running into a painful problem. Whenever I launch the app, the GN2020 headset lights up, and all buttons work on the app. The initial launch "tone" comes over the headset, but I can't hear any audio from the phone over the headset. I...
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...
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...
I'd rather use the user's existing DN for both versions of 2050, since her extension is linked to it. The rev 1 2050 is currently using that DN - how can I get the rev 4 version to use it as well?
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. How can I get the new 2050 to use the existing DN? Thanks!
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.