VoIP

1 readers

1 users here now

Rules

Be civil. Disagreements of varying intensities will happen, but particularly vitriolic attacks will be pruned from the discussion.
Do not promote or advertise for any business, service or product unless responding to a specific request for recommendations. This includes recommending a user change providers when they have not indicated they are interested in doing so.
Do not send private messages to users, or invite users to send you a private message, for the purpose of promoting or advertising a business, service or product.
Do not invite, encourage, or seek help with engaging in unethical or fraudulent activity relating to VoIP, such as call spoofing, robocalling and autodialers, or fraudulent STIR/SHAKEN attestation.

founded 11 months ago

MODERATORS

communick@netheads.online

Yeastar (alien.top)

submitted 11 months ago by clownboyz7@alien.top to c/voip@netheads.online

12 comments fedilink hide all child comments

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

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
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 11 months 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 11 months 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 ?