shouldn't the licenses be from within PLDS, so should let you change the license entitlement to a different host address anyhow? not sure on how this all works completely yet, but my understanding is that it should allow reallocation to new host (in event of hardware failure for instance?) I...
same down under with account managers @Matt Knight... suddenly we have a presence, and there are 3 of em! they even have an office in our City/Country. there's approx 4.4 mil people in our whole country so nothing too flash. wonder if it's a global strategy to take some responsibility and drive...
hey, if the phone is being "possessed" it really has to be something TAPI/OneX controlling it, shouldn't be phone manager now if it's 9.0.2.... whether that be on a PC on the LAN that's been hacked? or via open ports? if Monitor is open, then they could gain any info they like really... clamp...
it's definitely a case of "better the devil you know... than the one you don't"
other brands are just as rubbish with their support and firmware IMHO.
Avaya is a market leader, and as such, they make a train wreck whilst pushing features to market quicker than they would otherwise have liked...
have you disabled the Xima and tested same? just a thought with the recording... we had same with VMPro/Contact store at a site running SIP trunks. changed the similar db levels on the VCM as you've mentioned (as it creates a conference call in effect with a voicemail port to do the recording...
just to add my 2 cents worth, i would say nearly ALL of the IP500v1's i know of, have had the power supplies die now. i think we have a handful of clients with V1's still working.
Tisco's do repairs on the power supplies here in NZ, but you need to drive the chassis down the road, possibly...
definitely quicker! or put a SPAN /wireshark on and see what the DHCP messaging looks like (if at all) coming from the cisco. is it trippin on the SSON side of things maybe? or is the cisco actually just bridging the ISP static and you need another SOHO router after that? in NZ we can't get a...
just static assign address info in the meantime, presuming other devices get DHCP ok, like PC's etc. find the router address manually, call server etc. "Press * to Program" :)
firewall it off perhaps, just open the ports you need open, do it linux style, lock all and open one at a time ;)
wireshark trace same time if you SPAN port with Avaya LAN will show pretty quick what last dying messages were!
why not just pop a semi decent little VPN router on the remote site behind the cable/DSL modem to run the H.323 phone anyhow, LAN to LAN then, gets round all the NAT wah wah that you've probably been reading about peeps having dramas with.
or just a VPN capable cable router/ modem? then PC/...
Jamie is right, you'll do a lot of research and find that the Avaya is incredibly good value. what you don't want to do is get a system that you may need to do a "forklift upgrade" in 12 to 18 months time cos you need something like "call recording, and library/archive searching ability" which...
it can take quite a while for the service to become available, watch the page file increase in size after restarting the service, it'l go up to 4GB I think? ours is running on the linux DVD version with VMPro on same server, so can't check the real thing at our end sorry.
there are a number of...
ha! love it Intrigant. crack out the wireshark! haha.. not many Rx there ay, alhtough not much trace to look at. Are you getting anything back at all from Panasonic? better go to that part of the network and make sure it's at least still ping-able.
how is the SIP trunk setup? any registration...
sure gave me some grey hairs! the symptom our client was complaining about was voicemail stopping all the time! and rightly so, nothing else was connecting to LAN1, no PMP, IP Phones etc, so no other symptoms... it would just show as not binding
fun times! ;)
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.