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!

SIP trunk with DHCP setup 1

Status
Not open for further replies.

rsv23

Systems Engineer
Feb 13, 2019
239
PH
Hi guys,

Anyone experience of using DHCP on SIP trunk?

The ISP provided the credentials of their SIP line but they said they no longer providing static IP, this includes the SBS gateway/proxy etc.

We have set this to the IP office in lan2. the sip line registered and we can perform outgoing/incoming calls but for some reason, there are times that the calls dropped.

And also, the IP office responded very slow compared when the SIP trunk was on static. It also used the LAN2 as default LAN for outgoing network connection. This is causing issue of our call accounting via cloud. The data is not being pulled off.

The version is: Avaya IP Office V2 Essential Edition R11.0
 
Whoa. Okay, so there's prob a reason why you haven't had a response for this yet, and that's cos your setup sounds awful.

Can you explain exactly how your system is configured?

Ideally in this situation you will need -
LAN1 configured as your internal Voice VLan.
LAN2 as an internal management address. This should be static, or at least reserved on your DHCP server if that's how you really want to provide it. (NOT a public IP)
Firewall with a static nat to the LAN2 address for the appropriate .

As for your issues -
1. If you're calls are all dropping at the same time you prob have a NAT timeout issue on the Firewall. Esp if you haven't set a static nat.
2. Connection is slow. More info needed. Do you mean slow when dialling a number or slow when the line goes from out of service to in service?
3. Again seems like the firewall isn't configured for your cloud call reporter. Should need to setup a rule for the correct ports needed for the reporter, whether that's a Devlink connection or the old SMDR.
 
The problem is the service provider provided the setup as DHCP and the SBS proxy is FQDN. This is setup under LAN2, how ever all traffic seems routed here (LAN2).

The SIP line is connected directly from service provider to IPO LAN2(WAN) port. It is not connected to any firewall.

We have other customers using SIP line and they are all static and it works perfectly.
 
I just deleted my first reply. Here's the reply with diplomacy turned up to 100% - Get a firewall or SBC.


Stuck in a never ending cycle of file copying.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top