Dialog IP4422 VLAN setup BP250

[jamie77]

We are struggling to get some 4422's setup with VLANS and looking to the real Ericsson experts (engineers in the real world!!!) to help me out.

I have done the *5C Admin setup and figured out that the d43x02-config file needs altering but tech support have never done VLANs and are struggling as much as we are.

We have today got hold of the latest IP Phone firmware and are going to try it on Monday (not convinced that the firmware we were given 1st was correct!)

This seems to be the area of the config file that needs changing. I want the Phone to be on VLAN 3 and the PC plugged into it to be VLAN 1.


d42x02-config.txt:
[L2QOS]
PhonePort=6,1 ;prio (0-7) ,VID(1-4095)
PCPort=0,2 ;prio (0-7) ,VID(1-4095)
LANPort=0,0 ;MAC based VLAN/802.1Q based VLAN , untagged/tagged PC originating traffic

Am I right in thinking I change PhonePort to 6,3 and PCPort to 0,1??

Can anyone shed any light on what the LANPort=0,0 actually does???

Also is there any other settings that require changing in this file???

I know this is an MD111/MX-One ofrum but I don't know of a BP250 forum. I assume some of you guys also do BP's or maybe know of another forum for the BP.

I have alot of faith in the guys on Tek-Tips (use the Avaya IP Office forum everyday) and hope you guys are like the IPO guys.

Thanks in advance.

Jamie Green

ACA:Implement - IP Office
ACS:Implement - IP Office

http://www.alliedcom.co.uk

Fooball is not a matter of life and death-It is far more important!!!!

 

[jamie77]

The firmware I have now to try monday is Application R6A and Boot R3G.

We were given App-R3B and Boot R3D but after looking in the config file, it didn't even reference to these files!!!!!

Jamie Green

ACA:Implement - IP Office
ACS:Implement - IP Office

http://www.alliedcom.co.uk

Fooball is not a matter of life and death-It is far more important!!!!

 

[whosrdaddy]

Hi jamie77,

your assumptions are correct:

[L2QOS]
PhonePort=6,3 ;prio (0-7) ,VID(1-4095)
PCPort=0,1 ;prio (0-7) ,VID(1-4095)
LANPort=1,0 ;MAC based VLAN/802.1Q based VLAN , untagged/tagged PC originating traffic

the voice VLAN traffic must be tagged and your switch must be programmed accordingly to differentiate between PC and voice packets.

R6A firmware is the latest and is correct.

Cheers,
Daddy

-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!

 

[jamie77]

Thanks for that.

The system was at R13 with a CPU-D4. We were told these phones would only work on R15 and CPU-D5, do you know if this is correct? I have found a document thats seems to say otherwise: Here
I noticed that you put LANPort to 0,1. What does this do and what does each setting mean???

Jamie Green

ACA:Implement - IP Office
ACS:Implement - IP Office

http://www.alliedcom.co.uk

Fooball is not a matter of life and death-It is far more important!!!!

 

[whosrdaddy]

it is LANPort=1,0

this means that the voice traffic is tagged with the VID so your network equipment can give the voice traffic priority...

-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!

 

[jamie77]

LANPort=A,B

Ia it A to turn on VLAN for the Phone LAN port and B for the PC LAN Port or do I just put 0,1 and it will be fine??

Also if the Cisco switches we are connecting to default traffice to VLAN 1 if no tag is there do we need to set the PC Port to anything or will it pass it through untagged.

Jamie Green

ACA:Implement - IP Office
ACS:Implement - IP Office

http://www.alliedcom.co.uk

Fooball is not a matter of life and death-It is far more important!!!!

 

[jamie77]

sorry mistype (again) 1,0

Jamie Green

ACA:Implement - IP Office
ACS:Implement - IP Office

http://www.alliedcom.co.uk

Fooball is not a matter of life and death-It is far more important!!!!

 

[jamie77]

We cannot get these to work with or without the VLANs.

We have the IPU setup. IP phones with correct IP setup. Tried on 2 different systems. 2 different IPU's. Are the dialog 4422 just crap???? Don;t have any other IP Phones nocking about to try.

Phone logs on to system but we just get a message "Congested!" when we try to dial. Phone gets config file from HTTP server (BMS) ok but phone refuse to work!!!!!! Cannot ring these phones from others either.

This has been escalated to Sweden but I would really appreciate any advise you guys can give.

Jamie Green

ACA:Implement - IP Office
ACS:Implement - IP Office

http://www.alliedcom.co.uk

Fooball is not a matter of life and death-It is far more important!!!!

 

[whosrdaddy]

did you make an ethereal trace?

-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!

 

[jamie77]

yep. It shows the phone Registering with the gatekeeper when making a call (packet both ways) but nothing else.

Jamie Green

ACA:Implement - IP Office
ACS:Implement - IP Office

http://www.alliedcom.co.uk

Fooball is not a matter of life and death-It is far more important!!!!

 

[etompau]

Licence on IPU board?
Command 2171 and 2172 correctly programmed?
Correct system setting (BP-R15) in config file?
Other IP phones working with the same IPU board?

 

[ADB100]

The best option is to use DHCP Option 43 to supply the IP Phones with the Voice VLAN tag to use. This option is also used to supply the IP Phones with the Software Server so everything is automatic - i.e. you can simply plug the phone in to your PoE switch and walk away...

If you have access to the Ericsson Documentation it is detailed in there. The logic is quite simple though -
1. Phone powers up via PoE (or external PSU)
2. Phone sends DHCP discovery & request on Native (untagged) VLAN
3. DHCP Server supplies phone with an IP address from the Native/Access VLAN scope with standard options plus Option 43 which tells the IP Phone where the software server is and what VLAN(s) to use
4. IP Phone downloads the configuration file from the software server and upgrades to new firmware if required (then reboots and starts again)
5. Once firmware is correct the IP Phone releases the DHCP IP Address and starts 'talking' using the supplied VLAN tag, sending DHCP discovery & request
6. DHCP Server supplies new IP address & options from Voice VLAN scope
7. IP Phone registers with Gatekeeper using either Gatekeeper Discovery (multicast) or directly using Unicast (options in Config file).

HTH

Andy

 

[jamie77]

@etompau: Licenses ok. progammed correctly. Files ok. tied R6 and R5 Phone Firmware. No other phones working. These are the first. There are IP trunks to another BP on the existing IPU. We have taken the new IPU out and brought it back to the office.

@ADB100: There is no DHCP supplied in the Voice VLAN do that is not an option.

Jamie Green

ACA:Implement - IP Office
ACS:Implement - IP Office

http://www.alliedcom.co.uk

Fooball is not a matter of life and death-It is far more important!!!!

 

[ADB100]

@ADB100: There is no DHCP supplied in the Voice VLAN do that is not an option.
Jamie Green

Well done.........

 

[whosrdaddy]

We cannot get these to work with or without the VLANs.

We have the IPU setup. IP phones with correct IP setup. Tried on 2 different systems. 2 different IPU's. Are the dialog 4422 just crap???? Don;t have any other IP Phones nocking about to try.

Phone logs on to system but we just get a message "Congested!" when we try to dial. Phone gets config file from HTTP server (BMS) ok but phone refuse to work!!!!!! Cannot ring these phones from others either.

This has been escalated to Sweden but I would really appreciate any advise you guys can give.

you can always try netmeeting as an alternative for the phone (and they are not crap).

-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!

 

[jamie77]

Got these working-sort of!!!

Started IPU from scratch and now they do log on. We still have issues with the network as the IP phones will not get the D4 config when laptop is into the core network switch downstairs and these are on the Cisco's upstairs (linked by fibre). Works fine plugged into the back of the phone.

The system is not detecting the phone type but just seeing them as Generic H323 Phones. This means no button can be programmed and it doesn't say EXTENSION XXX just the number (and time/date). I believe this is how the display should be on R15. The phones do work.

Also, when an IP phone ring to the TDM but we get dial tone echoed!!! It is almost like the phone is generating dial tone and the system is also providing dial tone about 1/2 sec later!!!!!

I wonder if the IPU firmware has anything to do with all this. It is at R4B (I think). I downloaded P6EH from a link given to us by Ericsson. Might give this a go.

I know they are not crap, but getting very frustrated with these phones.

Jamie Green

ACA:Implement - IP Office
ACS:Implement - IP Office

http://www.alliedcom.co.uk

Fooball is not a matter of life and death-It is far more important!!!!

 

[jamie77]

@ABD100. Sorry didn't read your post fully!!! They don;t have DHCP on the n/w at all!!! I didn't realise DHCP could be given on the untagged VLAN and then is gives the VLAN needed for the device anyway. Never done VLANS, we have just asked for Layer 3 Diff Serv on the Avaya stuff.

Jamie Green

ACA:Implement - IP Office
ACS:Implement - IP Office

http://www.alliedcom.co.uk

Fooball is not a matter of life and death-It is far more important!!!!

 

[jamie77]

This was all downto firmware on the IPU's, even though Ericsson checked the BMS backup as said all was ok.

UPgraded to P6EH and all is now good.

Not tried the VLAN's again yet, but thanks for all your help.

Jamie Green

ACA:Implement - IP Office
ACS:Implement - IP Office

http://www.alliedcom.co.uk

Fooball is not a matter of life and death-It is far more important!!!!