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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

1416 with bad dbm32's?

Status
Not open for further replies.
Jan 17, 2005
1,471
US
New install IP500v26.0.8
combocard
combocard
ds8
ds8

I have 2 receptionists with 1416's and a dbm32 (1 each)

One users button module works fine for a while, but it seems that when a call comes in, after teh call is answered, you hear a click, and the dbm no longer works until reboot.
Has anyone seen this before? Is there a fix? The phones all updated when plugged in, but not sure about the modules.

These things are flaky.

Is there a bin file for the dbm? (I only see one for the bm32 (gbm file))

Yes I have a power brick, on each of the phones.


 
lol, good catch. I did not see that.

Maybe Avaya doesnt know which model they are talking about.


 
So, I call support and report the same problem eveyone else in the world seems to be having.

The tech on the other end tells me I have 3 options:

1. Buy a block of hours (just for the priviledge of reporting the problem, doesn't actually use any of the time), so they will send me a private build.

2. Wait till the next general Release comes out in november.

3. Connect the modules to a 1616 phone, which does download the firmware for the DBM32.

I figured best bet was to try option 3 for now. The only problem is he forgot to mention that the 1616 takes a different module, and the plugs don't fit.

Anyone have any other ideas?
 
Option 3 would tell me that Avaya is lying big time.

They say that the DBM32 should not be connected to an ipphone because they are not compatible!!!!

Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.
 
Indeed, that's bullsh1t, the D in DBM is for Digital the plugs and unit are completely different to a BM32 module. I re-assert my point that they are just rushing cr4p out the door to make a quick buck and when anything is wrong they then fob people off like this:)

ACSS (SME)
APSS (SME)

 
I emailed a link to this thread to Massingham.

Think anything will get done about it, besides the usual sunshine on our arrsse?


 
After so many posts and a lot of AVAYA bashing:

Q3 Maintenance release will finally support the DBM32.
I have it in the lab and it's working.

But there is still no word about it from AVAYA...
 
So are your shops' salespeople continuing to sell the V2's that default and flaky DBM's or is anyone pushing V1's with 5610s still?

In between my shop and a potential Magix to 500V2 upgrade sale the card goes Read Only on the demo kit and i'm stuck in a conference room trying to recreate the demo on the fly. Doesn't give me much confidence as a small shop to risk my money/reputation on such a big question mark, but don't want to keep pushing yesterday's box and handset...Happy Friday!
 
It is really solved.
I haven't had any SD card problems with special version.
This means that they found the problem.
And if it is documented then believe it.

But I am disapointed in the DBM gate!!!

Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.
 
I say let the Europeans do the heavy lifting and work out the bugz while we reap the benefits. ;)

Use system monitor unless of course you are a Tard then it IS the fault of the pbx.
 
Is it a HW issue solved on future shipments or is the card format the fix? Will contact my disti for specifics.
 
It has nothing to do with the formatting but with the way the ipo writes to the card.

Although there was a rumour that the formTtjng was the issue but I never found a proof of it.

Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.
 
I am starting to hate those 1400 phone!!!

I am trying to upgrade a IPO with a DS30 and that DS30 is almost full.

When it is on 3/4 the DS reboots and the phones try to upgrade again.

I am now trying one phone and see what happens.



Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.
 
I am trying a 3.2.999 now
Only one phone did not work.


Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.
 
The 3.2.999 did the trick.
However this has been done with the install.


Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.
 
I now have a "not supported classmark" but i did not do a reboot yet :)


Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.
 
And a reboot fixed that too :)

Phew, this was scary after a good friday the 13th


Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.
 
It was 12:30 with multiple phone or 6:00 with one phone.


Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top