I have standard h.323 phones and for the most part users take the numbers over wherever they choose. I'm seeing this issue where a remote VPN users phone will look as if its registered with the buttons being hosed. When you status the station it shows OOS, However, if you do a list reg the phone shows with an IP address. The original office phone has the message about pressing continue to take over the number, which works. If the other phone attempts it gets a 2011 error and on CM the above commands show the same thing. I've done a reset ip-stations and that IP address to clear it, but this phone cannot complete the registration for whatever reason. Is this a timer or something I need to let age out before having the guy try again?
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 TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Extension:2011 Error
- Thread starter wpetilli
- Start date
dialtonebone
Technical User
I would correct the 2011 error first (look at denial even 2011 in the CM books). Sounds like there is hindered communication between your PROCR and the telephone endpoint. Since this is a VPN device it further increases the chance of it being a firewall configuration problem.
- Thread starter
- #3
dialtonebone
Technical User
Your description sounds like a phone that began to register and there was obviously some 2 way communication but it never finished doing it's "station download"/getting it's buttons etc.
CM only gets what the network sends it, and the network only sends what the devices in the middle allow.
Check out other threads that discuss firewall issues such as ALG/Layer 4+/DPI etc. Many of these will see Avaya's traffic, not agree with its implementation/assume it is compromised and then it's dropped. That also means a few parts of the conversation may make it through.
Some consumer routers (alllll types) have these "features" built in and will cause the issues at a home. Recently I encountered an issue where the Spectrum Cable Company's "Wave2" router was a known offender for VoIP and VPN issues. Sure enough I got to experience this issue myself after only hearing of it from others. They have "upgraded" models and so on of the router, but none of it just lets the traffic flow through uninhibited.
There could also be something way less exciting, like a routing/configuration issue.
Are these 96x1s with VPN feature in the firmware, or some sort of "take home" VPN router kit they plug a normal programmed 96x1 phone in to?
CM only gets what the network sends it, and the network only sends what the devices in the middle allow.
Check out other threads that discuss firewall issues such as ALG/Layer 4+/DPI etc. Many of these will see Avaya's traffic, not agree with its implementation/assume it is compromised and then it's dropped. That also means a few parts of the conversation may make it through.
Some consumer routers (alllll types) have these "features" built in and will cause the issues at a home. Recently I encountered an issue where the Spectrum Cable Company's "Wave2" router was a known offender for VoIP and VPN issues. Sure enough I got to experience this issue myself after only hearing of it from others. They have "upgraded" models and so on of the router, but none of it just lets the traffic flow through uninhibited.
There could also be something way less exciting, like a routing/configuration issue.
Are these 96x1s with VPN feature in the firmware, or some sort of "take home" VPN router kit they plug a normal programmed 96x1 phone in to?
- Thread starter
- #5
- Status