Search results for query: *

PSS: Forgot a 5th Clue... It was ACTUALLY helpful to see the BOOTP error at the bottom of the page of the Manager... This was another clue that something was missing! It was trying to find the BOOTP file from the Analog UNIT... Could not find it since it was also not listed the the list of...

Issue Resolved... For us uneducated people here is the run down: 1) Because the IP400 Analog unit was not listed in the "Upgrade" menu in the Manager software this was one clue. 2) Because there wasn't a light "on" on the front of the IP406 Unit under "expansion" this was a 2nd clue. 3)...

Again, noone has answered why the IP400 analog 16 unit doesn't show up in the "UPGRADE" list... is it really not working even though it has a GREEN light?

Wondering if that missing BOOTP files is from the IP400 Analog 16 trunk unit? If so, guess that would explain that it isn't working. ???

Amriddle, Ok. Now, i just noticed, that one of the BOOTP files is missing... there were TWO files now there is only one. (I noticed this in the Manager, 2 files were previously there, now only one). Not sure where to go or how to get this missing file back.

IPguru... Just to clarify... are you saying i should get my Line Provider involved? I did some more searches on Cause 34 and it sounds like an error that may be caused by the Line Provider... not my IPOffice system... am i correct? Thanks

sorry, my "Manager" window... not monitor window.

at the bottom of my Monitor window i'm getting this error: "received BOOTP request for 0019db627782, 192.168.0.3:68, unable to process" What's going on here? anyone know?

K, so i did what you suggested. Still no go. This is the report of what happens when a call out is made: 150357mS CMExtnRx: v=69, p1=6 CMInformation Line: type=NoLine 0 Call: lid=0 id=-1 in=0 Called[8] Type=Default (100) Product...

I went in and made all the PRI lines out of Service... there were 8 that were in service. Not sure if that has helped yet, won't be able to test outgoing phone call until i'm in the office. The 9N shortcodes look all normal.

I noticed the PRI notes as well. There was a PRI installed on this unit years ago, but we've been using Analog for a couple years now. The PRI still shows in the Manager along with the Analog trunks. Not sure why the PRI kicked it self on, if that is the case, HOW do you turn it off so it is...

The only error i get is at the top of this monitor list: after a reboot this is what I get: 57mS ERR: TDMLink 1 reports CMmsg error at other end 59mS ERR: DTExtn Line Up 4 491mS RES: Wed 2/11/2011 18:52:22 FreeMem=3818824(1) CMMsg=2 (3) Buff=100 607 798 1100 5 Links=9320 Elements=0...

monitor of outgoing call: can't make much sense of it 2330979mS CMTARGET: LOOKUP CALL ROUTE:5 type=100 called_party=8015589178 sub= calling=128 in=0 complete=0 2330979mS CMTARGET: ADD TARGET:5 number=8015589178 type=100 depth=1 nobar=1 setorig=1 2330980mS CMTARGET: OVERLAP LOOKUP CALL...

IP406 3.2 (53)running IP400 Analog unit 5.2 (53) Can't get any incomeing calls to route and when we dial out we get a dial tone but then when we dial out it gives us a fast busy signal and phone says Disconnected. Not sure if the analog unit has gone out because it GREENS up. It also still...

Anyone know why some setting keeps getting knocked out? I can't figure out what setting it is but I have to reboot the system to get it to work every few hours. It also, keeps trying to Send Hold music.wav file to the unit, and fails... we don't currently use hold music but would like to in...

Seriously.... Ok, so I went into VoiceMail pro and it reset the settings overnight... What's going on? Why would this do this. So, I set the setting back to what it was supposed to be for daytime calls.... and now its working again. Any Clue? thanks

North America, YES, and Analog is great.... and a LOT cheaper than a crappy T1 line with PRI... Problem this moning... System Hangs up on me now. Here are stats.... can't figure it out... mS PRN: Monitor Started IP=10.20.10.70 IP 406 DS 3.1(29) Liberty 1mS PRN: LAW=U PRI=0, BRI=0...

VIGURED IT OUT! Our regular IT guy had changed the IP address on the PC running the IP Manager and VM Pro software! This seemed to fix everything! It was able to find the VM software file so that it could route the calls correctly. Thanks everyone esle for some ideas!

I can set a "FallBack" extention and it works. I can get the calls, but that doesn't help me when I want my calls to follow a route at Night from VoiceMail pro. So why does the fallback work and no my VM:Test setting from Voicemail pro?

So, its not transfering over to the Voicemail Pro client, somewhere, somehow... can't figure out what the problem is.