Search results for query: *

MUWAHAHAHAHA! Did it! I can, once again, get the extension of inside/intercom calls passed (versus the main #), AND I can throw out my DID to external parties. Thanks, again, everyone! IP 500 V2 IPOMgr/VMPro v9.1.0.437 46/5610s, 46/5621+25s 9640Gs

I thought this (below) would do it, but internal calls are still Twinning to my mobile with my DID number instead. @#$%! IP 500 V2 IPOMgr/VMPro v9.1.0.437 46/5610s, 46/5621+25s 9640Gs

So, of course there's a quirk regarding using Twinning to my mobile. On the main ARS, I had things configured so that when someone internal dials my extension, I'd see what extension it was (Nerd alert: I added everyone's extension to their info already in my address book, so I get a name to...

Thanks folks - I finally got it working by deleting everything in the User Short Codes window, and adding back the *DCP first, and then this: FIRST: *DCP 40000000,0,1,1,0 Dial 0 SECOND: 9N; dial Ns5551212 (our telco prepends the area code) Line ID 1 (not the main ARS) IP 500 V2 IPOMgr/VMPro...

This worked! "Turning on Auto Connect on start up, turning off TCP discovery and setting the UDP broadcast address to just one of my IP Office systems" Thank you folks! IP 500 V2 IPOMgr/VMPro v9.1.0.437 46/5610s, 46/5621+25s 9640Gs

I'll reboot the PC running VMPro and report back. Thank you everyone for brainstorming this with me! IP 500 V2 IPOMgr/VMPro v9.1.0.437 46/5610s, 46/5621+25s 9640Gs

Thanks for that - still no joy. If you have time, would you share a shot of the Discovery tab? IP 500 V2 IPOMgr/VMPro v9.1.0.437 46/5610s, 46/5621+25s 9640Gs

I'll give that a whirl and report back! IP 500 V2 IPOMgr/VMPro v9.1.0.437 46/5610s, 46/5621+25s 9640Gs

Thanks Westi, WCeightoh, intrigant, and sizbut- The Discovery tab in Preference now has nothing selected, and I input the switch's IP in the discover field. When I close Manager and start back up, I'm presented with this view (image, below), and the "Okay" button is greyed-out. If use the...

@amriddle01 - Thanks! Enjoy your weekend! IP 500 V2 IPOMgr/VMPro v9.1.0.437 46/5610s, 46/5621+25s 9640Gs

Since there's no "revert" button/feature, would you mind sharing what options are ticked/selected in the first (Preferences) tab, and the third (Discovery)? IP 500 V2 IPOMgr/VMPro v9.1.0.437 46/5610s, 46/5621+25s 9640Gs

I'm looking for a way for it to skip that initial screen (below) and just ask for the password. In the Preferences --> Discovery tab, I have deselected DNS, UDP, and I have the IP range for just 192.168.42.1-192.168.42.2 so at least I don't have to wait for it to scan the whole subnet. IP...

For the life of me, I cannot get my extension to display the DID assigned to me whenever I call external parties. In the Main ARS, I have it configured so that if someone calls my mobile, I see their extension (9045551234SiE), so I know our carrier (TimeWarner) allows us to send calling party...

Yes, same subnet: Appliance = 192.168.42.1/24 Office PC = 192.168.42.2/24 IP 500 V2 IPOMgr/VMPro v9.1.0.437 46/5610s, 46/5621+25s 9640Gs

That's the frustrating part - both the PC and appliance ARE on the same LAN... @#$%! IP 500 V2 IPOMgr/VMPro v9.1.0.437 46/5610s, 46/5621+25s 9640Gs

I only have a single IP Office instance - is there any way to launch Manager.exe and have it automatically select it? In preferences, I already have "Auto connect on start up" selected, and I've experimented with the Discovery tab settings; I currently have the discovery IP range of only two...

Yurp.. gotta love FORFILES ;-) IP 500 V2 IPOMgr/VMPro v9.1.0.437 46/5610s, 46/5621+25s 9640Gs

Because I'll get a call or email about a problem, and I like to be able to go back and see what happened at the time. It's a holdover from my network engineering days... IP 500 V2 IPOMgr/VMPro v9.1.0.437 46/5610s, 46/5621+25s 9640Gs

Sooo, this (below) is too extreme? cmcallevt=1 cmextntx=1 cmextnrx=1 cmextnevt=1 cmlinetx=1 cmlinerx=1 cmcalldelta=1 cmextntxp=1 cmextnrxp=1 cmmap=1 cmtargetting=1 cmlogging=1 cmars=1 cmlrq=1 cmsortIEs=1 siptxevents=1 siprxevents=1 frevenm=1 frmgmtm=1 h323ev=1 stuninfo=1 ifacequeue=1 iftcp=1...

(note: we have a PRI) I'd like to strike a happy balance between logging too much (as a network engineer, "too much" is either never enough, or just right) and missing out on key logging information. Do any of you seasoned troubleshooters have a favorite group of settings you'd be willing to...