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!

Avaya IP Office SIP Line without Audio 1

Status
Not open for further replies.

Luis Monzon

Technical User
May 4, 2017
1
GT
Hello everybody! I hope someone can help me with this strange issue I'm experiencing with an Avaya IP Office 500V2

I have few SIP Lines with a vendor called Nextiva, my IP Office has the internal network configured to LAN Port and a Public IP Address connected to LAN2 Port (WAN). I have a license for 10 SIP Trunking Channels, and two VCM 64 modules, all of my Phones are IP (4621, 4610 and 1608). I did the configuration of the SIP lines about 4 months ago, it took me a little while to understand all the parameters and have a combination of them that allowed my system to work as expected in terms of receiving and making calls from the Nextiva SIP Lines, the setup worked fine for 4 months until one day it suddenly stopped working, the issue is that there is no audio when making or receiving calls from Nextiva SIP Lines, I have an E1 too and when making calls from this line there are no issues at all, the problem is specifically with the SIP Lines. I can trace the calls from the System Status application and I can see the SIP messages are normal, I can see that the call connects on the other end but there is simply no audio, between extensions everything is normal, also for outbound calls thru the E1.

I have tried many things:
Changing the order of codecs,
Switching to my other Internet link (reconfiguring the public IP Address accordingly)
Rebooting the IP Office
Shutting down the IP Office and on again
Upgrading the IP Office (it is now in version 9.1.700.163)
Removing one VCM
Swapping the position of the VCMs
I configured another SIP line from other vendor (SIP.US) and I had the same result (no audio)

Please advise if any of you has experienced an issue like this and if you were able to fix it.

Thanks in advance,

Luis Monzon
 
Liza Monzon said:
Public IP Address connected to LAN2 Port (WAN)
Disconnect immediately & find a COMPETENT installer.

IP Office should not be connected direct to the internet in this way, it is only a matter of time before you are hacked!


Do things on the cheap & it will cost you dear
 
Luis, did you resolve this issue? Hard to troubleshoot your configuration when you indicate that it was working 4 months ago. Does your system status indicate any errors on the SIP channels?
 
TeletronMan
The OP does not seem to have responded sins my original post

From the original post they had the IPO connected direct to a public IP address.
Because this is a VERY BAD way to configure an IP Office & exposes the eng user to hacking I would suggest that this user should not be given further assistance on this issue beyond advisig that it should be correctly secured behind a firewall or SBC.




Do things on the cheap & it will cost you dear
 
Bit of an overreaction considering he could have a firewall between the Internet and his IP Office. We have a public IP on the LAN2 port and have a firewall between them, so what?

OP, do you have a firewall? If so the problem with your audio is most likely there and I'd advise using the live logging functionality.
 
Bit of an overreaction considering he could have a firewall between the Internet and his IP Office. We have a public IP on the LAN2 port and have a firewall between them, so what?

Placing an IPO on a public IP address is a common error made by unknowledgeable users & incompetent installers resulting in 1000's of IP offices currently being visible on the Internet & targets for hackers.

if you have a firewall between the IPO & the internet then provided that only allows connection from you sip provider then you should be ok (I hope you have tested it thoroughly), however if this is the case then there is no reason why Lan2 should not have a private IP address so It always raises alarm bells when seen.

My responses have been made because I want to protect the end user from risk & without any other indication of their security I wont help them shoot themselves in the head.
had the original post been form someone claiming to be a vendor I would probably have red-flaged it as "Vendor not competent to maintain this equipment"


Luis Monzon said:
it took me a little while to understand all the parameters and have a combination of them that allowed my system to work as expected in terms of receiving and making calls from the Nextiva SIP Lines
Does not sound like a user who has a good understanding of VoIP in general or Sip In particular.

This is why My original response suggested he contact a competent installer.
the OP has had plenty of time to respond & update so I suspect they have either resolved the issue themselves - or followed my advice & had it fixed for them
, hopefully having any hacking risk resolved in the process.




Do things on the cheap & it will cost you dear
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top