this post was submitted on 24 Oct 2023
1 points (100.0% liked)

VoIP

1 readers
1 users here now

Rules

founded 1 year ago
MODERATORS
 

Hi guys,

Need your help on yeastar pabx. I have created one vlan for pabx and it is vlan 3. It is connected directly to HPE 5140 switch.

Right now the issue is to make it as voice vlan and data vlan. If i put vlan 3, the ip phone gets the DHCP but if i change it to voice vlan 3, it will stop working. Lets say i want to put it as voice data vlan 3 and data vlan 1.

Just need your guys advice on few things

  1. Does the pabx connected to HPE switch need to be trunk or access ? (mine is currently access if i put as trunk the pabx will not get the vlan 3 segmentation

  2. Does the ip phone need to be setup manually ? I believe it should be able to point to the pabx

Thank you.

you are viewing a single comment's thread
view the rest of the comments
[–] stlslayerac@alien.top 1 points 1 year ago (5 children)

First off it's PBX not pabx.

There is a lot of missing info. Is your router plugged into this switch? Is the router have vlan 3 configured? Are the phones sharing data ports with PCs or do the phones have their own switch? Are PCs being plugged into the PC port on your VoiP phones?

[–] clownboyz7@alien.top 1 points 1 year ago (4 children)

The setup is isp > load balancer > juniper firewall > hpe switch

The pbx is connected to hpe switch. The phones is sharing data port with pc. Meaning data vlan and voice vlan should be together.

I want vlan 1 as data vlan and vlan 3 as my voice vlan.

[–] stlslayerac@alien.top 1 points 1 year ago (1 children)

Ok so this is helps.

Create Vlan 3 on router and set it to DHCP server so it hands out IPs. Set the range to exclude the IP address you are going to give the PBX system PBX system will need itself configured to use Vlan tag 3. If Vlan 3 is going to go through the same interface as your data interface the firewall needs that configured so data is native lan. If the HPE switch is having data and voice go through the same interface you need to set that port as a trunk and allow Vlan 1 for native data and 3 for voice. Trunk ports allow multiple vlans through them while access ports dont. So really if every port on the switch that will share voice and data all need to be trunked for Vlan 1 and 3. Next phones will need to manually have vlan 3 set on them to get a DHCP address and communicate on Vlan 3.

[–] clownboyz7@alien.top 1 points 1 year ago

The dhcp is from juniper firewall. So no need to declare voice vlan ? Just trunk vlan 1 and 3 and manually set vlan 3 on each phone ? This is what you trying to say correct ?

load more comments (2 replies)
load more comments (2 replies)