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

Embedded VM giving Busy. Prompts are upgraded.

Status
Not open for further replies.

Gibsonic

MIS
Joined
May 9, 2001
Messages
458
Location
US
I have a brand new 406V2. It is running 3.1(65). I have done a dozen embedded VM's in 406's in the past but this is the first time i've had an issue.

I upgraded the 406 before ever working with the CF card. As in the past i used a CF card reader to my PC an copied over the prompts per the avaya documentation.

Reboot. *17. Busy.

I then put the card back in the pc and the LVMAIL folder was gone.

I repeated the copy via the CF card reader and returned card to 406.

Reboot. *17. Busy.

I have monitor enabled to watch Embedded VM activity. It is able to read the card. The CF light on the front of the 406 is on. Upon reboot it reads in all the files from the card. Still busy.

Ok, so now i'm thinking maybe something is screwy with the way it transfered via the card reader so I transfer all the files again using TFTP method.

Reboot. *17. Busy.

I wait a while, I reboot a few more times. Still busy.

I try to put the CF card back in the card reader and now the card is unreadable to windows.

here is the latest monitor log from a call attempt to *17 resulting in busy.

Any ideas?



198216mS CMTARGET: LOOKUP CALL ROUTE:1 type=100 called_party=*17 sub= calling=204 in=0 complete=0
198216mS CMTARGET: ADD TARGET:1 number=*17 type=100 depth=1 nobar=1 setorig=1
198216mS CMTARGET: SYS SC:1 *17 3 sc=type=VoicemailCollect code=*17, num=?U
198217mS PRN: LVMailFlashMan::AvailableChannels: Used = 0
198217mS CMTARGET: SC VMC:1 target=00000000
198217mS CMTARGET: OVERLAP LOOKUP CALL ROUTE:1 returned 1
198217mS CD: CALL: 0.1001.0 BState=Idle Cut=1 Music=0.0 Aend="Extn204(204)" (1.11) Bend="" [] (0.0) CalledNum=?Extn204 () CallingNum=204 () Internal=1 Time=752 AState=Dialling
198218mS CMExtnTx: v=204, p1=2
CMSetupAck
Line: type=DigitalExtn 3 Call: lid=0 id=1001 in=0
Called[?Extn204] Type=Default (100)
BChan: slot=1 chan=11
Product Unknown
Display [?Extn204]
Timed: 26/06/07 10:27
198218mS CMTARGET: SELECT:1 1 0 TGHG=00000000 TGUSER=00000000 INCL=00000000 EXCL=00000000
198218mS CMTARGET: SELECT:1 NO TARGETS, TRY VOICEMAIL
198219mS PRN: CALL: 0.1001.0 Deleted leaving 0 CMCall objects
198219mS CALL:2007/06/2610:27,00:00:00,000,204,O,?Extn204,*17,Extn204,,,1,,""
198219mS CD: CALL: 0.1001.0 BState=Idle Cut=0 Music=0.1 Aend="Extn204(204)" (1.11) Bend="" [] (0.0) CalledNum=?Extn204 () CallingNum=204 () Internal=1 Time=754 AState=Idle
198220mS CMExtnTx: v=204, p1=2
CMInbandTone
Line: type=DigitalExtn 3 Call: lid=0 id=1001 in=0
Product Unknown
UUI type=User2User [TB1\r\n] [0x54 0x42 0x31 0x0d 0x0a ]
Cause=17, User busy
Timed: 26/06/07 10:27
198220mS CD: CALL: 0.1001.0 Deleted
 
To be honest with all the issues reading from your PC and what not I would say the Compact Flash card may have an issue.

Like you say if you have done it all before your obviously confident in the way its done.
 
ok for kicks and grins before i send this card back to Avaya I put the card back in my card reader and got windows to format the card.

i then put the card back in the IPO, blank, and then did the tftp send of the files again.

the good news is that i can now take the card out of the IPO and read the files fine in my card reader.

the bad news is that i still get busy when dialing into VM

i also tried setting up an auto attendant and using the shortcode prompts created with that to get some sort of response from the card.

i know these CF cards have "something" magical about them that makes them unique for embedded vm as opposed to a standard off the shelf CF card.

Is the license file or key file that makes this unique deleteable?

The thing is that the monitor logs look to be perfectly normal. no errors, it reads the files. it convered the files on first reload to the new file names like it was suppose to...just won't f'ing work.

 
Just a long shot. Under the system tab what is your VM type set to?
 
hah...yeah i knew someone would ask that. it's been integral all along.

thanks though.

im going to try to use a slightly older copy of the source files from 3.1.56. The files are probably identical to 3.1.65 but this may cure the issue if ive got bad/incomplete source files.

here's tryin!
 
Did you really re-formatted the card? If you did then the card cannot be used for embedded VM anymore.
These cards are formatted with a special FileSystem from VXWorks and there is a magic code on it so IP Office can identify if it is a valid embedded VM Card. Now you changed the filesystem and erased the magic code, bad luck!
 
it was already DOA before i tried that...it never worked even before formating it.

good to know though.
 
Unfortunately now you will be unable to claim warranty on the card. Worse Avaya don't reformat the cards claiming (to me) that it's cheaper for the dealer/customer to buy a replacement.
 
i am no worried about getting the card replaced. I just want one that works.
 
If you have formatted it it is definitely screwed beyond anything you can do now.

You need a new card.

Now it is screwed there is no way you will be able to find out why it wasnt working, you need to start again with a new card.

ACA - IP Office Implement
ACS - IP Office Implement
ACE - IP Office Implement
 
yeah, i was pretty sure it was a bad thing to do but seeing how the card was not functioning at all prior to that point and I was trying to get this thing working as quickly as possible, i gave it a try anyway. I didn't know if it had a secure partition with the special "key" in it or how it worked.

anyway, it obviously didn't worked. I can now remove that option from the list of possible fixes in the future ;)
 
You could still use the card on a 406V2 or IP500 without the need for an embedded VM to hold the music on hold wavefile and the binfiles necessary for the IPPhones to work.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top