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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
IPO R10 No Audio VoIP One-X 7
- Thread starter maxse
- Start date
-
1
- #2
- Thread starter
- #3
I do have a 0.0.0.0 0.0.0.0 GATEWAYIP route. I have seen others use 255.255.255.255 I assume they accomplish the same thing not to get off topic.
What's odd is that I setup evening before PRI cutover and I was able to dial *17 and hit vm prompts now it connects and I get dead air. It DOES work if I have the app call another line and bridge but of course not through VoIP.
What's odd is that I setup evening before PRI cutover and I was able to dial *17 and hit vm prompts now it connects and I get dead air. It DOES work if I have the app call another line and bridge but of course not through VoIP.
-
1
- #4
- Thread starter
- #5
- Thread starter
- #6
-
1
- #7
-
1
- Thread starter
- #9
holdmusic34
Vendor
Star for posting resolution. Avalon picks up a gong on the way though.
Hail the tripod!
Hail the tripod!
- Thread starter
- #12
-
1
- #13
- Thread starter
- #14
Telecomboy
Programmer
Just change the ports. Don't use the ports mentioned in the manual as these are easily hacked and you will be hacked. I had a client that didn't want to change from the ports mentioned in the manual and they were hacked less than 2 days later to the tune of $5k. I had made it such a big deal that the client knew it was not my fault and was their own/IT techs fault for using the default ports.
- Thread starter
- #16
-
1
- #17
Telecomboy
Programmer
Yes the 50802-50812... That is how they accessed my client's system.
- Thread starter
- #18
I am not forwarding the 50802-50812 BUT I have any learned that you will be hacked of course. For clients that we can get an agent (LMI/TeamViewer)that's what we do - otherwise if we have to we forward those ports but ONLY white-listing our IP so they won't get hacked.
Would you say it's safe to forward the ports for One-X mobile as long as manager ports are closed? The only way I presume they can rack up toll fraud in this case would be if they brute forced the user extension password for One-X login...
Would you say it's safe to forward the ports for One-X mobile as long as manager ports are closed? The only way I presume they can rack up toll fraud in this case would be if they brute forced the user extension password for One-X login...
-
1
- #19
Do you have one way audio? Check mobile stats for RX / TX.
Set FQDN in IPO domain for your LAN interface who's public IP you're using.
Make sure you're forwarding your assigned ports ie. 48xxx:50xxx, I like to make ports a mininum, so 54000:54264
forward your SIP to IP, forward other ports to oneX.
In onex, add your FQDN.
set your firewall correctly.
Should be fine.
Did I miss anything?
______________________
|........................................|
|.....i.eat.bunny.children......|
|______________________|
(\__/) ||
(•Y•). ||
/ < )<||
Set FQDN in IPO domain for your LAN interface who's public IP you're using.
Make sure you're forwarding your assigned ports ie. 48xxx:50xxx, I like to make ports a mininum, so 54000:54264
forward your SIP to IP, forward other ports to oneX.
In onex, add your FQDN.
set your firewall correctly.
Should be fine.
Did I miss anything?
______________________
|........................................|
|.....i.eat.bunny.children......|
|______________________|
(\__/) ||
(•Y•). ||
/ < )<||
- Status
