Avaya changing the manufacturing of the phone - there has got to be a PSN somewhere on this, no? Speaking as a reseller myself, it has put a strain on my relationships with users. The phones walk like a Norstar T7316E, talk like a Norstar T7316E, but somewhere in there they just don't think like...
I timed my post so I would have all weekend to agonize over it and not be able to attempt to try any of your suggestions. As soon as Monday rears its ugly head i'll give it a try. Thanks for taking the time to answer, though.
~C~
www.metrolinedirect.com
I've scoured the posts but didn't find anything in relation to my inquiry, but I apologize if this has been hashed out endlessly - feel free to admonish me and point me to old posts.
The problem - IPO Release 7 and 8 (7.0.5, 7.0.27, and 7.0.31 and R8.0.18) my 9500 series phones (9504 and 9508)...
From my own experience, these phones have standard SIP support only when you have it connected to a VCX server. The phones have no way of retaining firmware settings like your typical endpoints, so, once you power the phone off it kind of forgets where it is. After some enterprising tweaking at...
One of the uber-posters crafted this FAQ:
http://www.tek-tips.com/faqs.cfm?fid=7085
Pay special attention to the "grab a cup of coffee" line as that one- above all else- will most likely save your sanity.
Yah, as GHTROUT pointed out, easiest thing to do is associate the letters with their function - if you think of the S in FXS as "station" or "set" then you know that that would essentially be an analog extension and if you think of the O in FXO as Central "O"ffice or even "Outside" knowing that...
The *XX activates speakerphone, no getting around that. Intercom plus (*) asterisk plus extension is how you page group and/or individual. Intercom plus extension (no *) is how you ring an extension and/or group. The way to disable the * is to tell the user to, you know, not dial it ;) I guess...
Well, when I said "gotcha" what I actually meant was "that was way too obscure for my addled brain to figure out so I will not be able to help you" and, therefore, no email was issued, no contact information revealed. We can all sleep well tonight knowing that absolutely ZERO rules were broken...
I know of a US based repair facility; however, I work for said company so I do not want to engage in blatant promotion / selling (against ToS). If you are interested, post your email and I can email you the details.
This happened numerous times until I discovered the pesky lil built-in Windows XP firewall. I could do all the things you listed, but never upgrade. I'm sure you already checked that, though. Sometimes, turning it on then turning it off and rebooting makes it "stick".
Gah - I must admit I was intrigued by the subject. Intrigued by not only the near impossibility of paging underwater, but by whatever possible situation which would require paging people underwater. "Boss wants every worst-case scenario covered i.e., the levees break and our warehouse floods...
We had the exact same issue here at our office. We even ran the overly verbose system monitor to see if we could see it attempting to deposit the message in some made-up mailbox. What I ended up doing was creating another user (i.e. "Test") and I copied all the problem user's button settings...
*weep*
Unfortunately, none of the advice works in my case. Not sure about the original poster. I opened TFTP log and nothing even appears. What has apparently happened, these phones were programmed for Mr. X's network using VLAN ID of 112. Let's say MR X runs has his network 10.x.x.x and I have...
I am in the same boat as the OP. I have a whole slew of 4620SW phones that seemingly bypass the ethernet programming stage and jump directly to DHCP with a VLAN setting already defined. I followed your suggestions, tlpeter, I removed the commenting from the 46XX file with PROCSTAT set to both 0...
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.