Teleworker and 3300 upgrade 1

[blackberry1980]

I have an enquiry and am uncertain regarding a hardware upgrade from a lx controller to a Mxe controller. I need to upgrade from an lx to mxe but this system is on a rather large network with enterprise and ops manager. Is it possible to do a backup from the lx controller and restore it to the mxe controller, keeping the same system ip addresses and just do a straight swap of the controllers without having any major problems ?


Another question.........I have an sx2000 using a 3300(dpnss link) as a gateway connected to a teleworker server. If i ring from a teleworker set to the sx2000 phones audio is bothways and works fine. But if i ring from the sx2000 to the teleworker phone, the teleworker cannot hear the sx2000 phone but the sx2000 phone can hear the teleworker(one way audio). All relevant ports are opened and teleworker server is in server mode in the DMZ. The 3300 gateway subnet is defined withing the teleworker.

Any idea's ?

 

[Mitelmatt]

Hi

Ok so Question 1:

yes changing from an LX to an Mxe is simple. Move the licences on the AMC to the new Hardware id of the MXe. Take a back up. Input the new licence options into the Mxe, restore database when asked.(the restore process sorts out the difference in controller) You may have to change the IP address from the default as this is set in Vxworks. But apart from that all should be good. Just do a few checks like DBMS save and make sure all the data looks good. But done this loads and never had any major problems.

Question 2:

Sounds like you haven't got the Nating on the firewall correct. Basically all traffic has to route to the EXTERNAL INTERFACE address and not the internal one. So on your firewall you need a NAT on the inside interface as well as the outside interface. So in your case when the traffic goes from the SX200/3300 it's not routing correctly.
Either that or check your deafault gateway.

Hope that all helps

 

[blackberry1980]

Thanks Mitelmatt

I was hoping the lx to mxe would be that simple, but just needed some verification which you have provided!

I have checked the rules on my firewall but not the nat table, i will have a look at this. Thanks for pointing in the right direction

 

[Mitelmatt]

no problem.

What type of firewall is it?

 

[blackberry1980]

Its a Nokia checkpoint firewall, on release NGX R65. I dont have much knowledge on those but am trying to learn it.

 

[Mitelmatt]

ok cool. I'd make sure you have your inside NAT done

Let me know how you get on

 

[blackberry1980]

Hi mitelmatt

Ive not had a chance to look at the inside nat due to firewall engineer not being around for a while. But have discovered something interesting. If i put an ip phone on the 3300 gateway, this communicates fine with the teleworker set on the other end with no audio loss. It is only when a dnic or ons(from the sx2000) set calls to the teleworker(via 3300 gateway) that i have the problem, but if this was an e2t issue, howcome i can call a normal ip set on the other end and get through with audio bothways ? If it was a network problem or routing or nat issue, howcome the call works fine with a phone from the 3300 gateway ? Ive also had mitel support look into the teleworker and they say its all set up correctly. This is turning out to be very weird!

 

[IrwinMFletcher]

The system (E2T) uses a different port range than the sets, so the firewall is probably configured to allow the set port through.

 

[blackberry1980]

But this 3300 has a common rtc and e2t. Where can a find a port range used by the e2t?

 

[Mitelmatt]

Ok so the reason why you can call IP to IP ok is that the E2T doesn't get involved. The E2T only gets involved when there is a TDM (analogue or digital) device involved.

So what Irwin is staying is correct. It sounds like the Firewall rules have been set up properly:

UDP 20,000 to 23,000 (SRTP)
Server ? Internet
Server ? LAN
Voice Communications. Allow incoming SRTP on UDP ports 20000 – 23000 from all streaming devices on the LAN and the Internet. Mis-configuration here is a common cause of one-way audio problems.

UDP 1024 to 65,535 (RTP)
Server ? LAN
Server ? Internet
Voice Communications. Allow outgoing SRTP on UDP ports greater than, or equal to, 1024 from the server to all streaming devices on the LAN and the Internet. Mis-configuration here is a common cause of one-audio

 

[blackberry1980]

Would the above still hold true if i had another sx2000 using another 3300 as a gateway but using the same teleworker server and that system works fine. Would those rules cover all my 3300's in the network ?

 

[Mitelmatt]

as long as the rules allow these ports from both 3300 ranges.

Definately sounds like a rule / gateway issue

 

[blackberry1980]

mitelmatt

sorry to deviate from one scenario to the other but ive just done the lx to mxe upgrade and when i do the restore, i get dsp failures. Now, i think this is due to the mxe being on version 9 and using dsp2 modules whereas my lx controller had version 7.1 and it didnt have dsp 2 modules. Have you ever done one of these ? If i format the hard disk and re-install software the dsp alarm goes away but as soon as i restore the database, the dsp alarm comes into play!

 

[blackberry1980]

ok sorry! that was just me being daft! I didnt notice that there were 32 compression licenses but no dsp module to support it. i done the restore immediatly after pulling licenses from the amc, thinking that the restore was causing the dsp problem. So i re-installed the software and licensed it and rebooted without the restore and the dsp alarm came up. I do make life hard for myself!

 

[Mitelmatt]

ah yes but you'll only make these mistakes the once....hopefully!!!! ;)

 

[IrwinMFletcher]

You don't need the dsp2 modules for the MXe, the 'old' 21161 dsp modules will work fine. The dsp2 are only required for T38 and increased G729 densities.

The E2T/RTC voice udp port range is 50000-50512.

 

[blackberry1980]

Guys, I have checked all the nat settings and they are all set according to the teleworker guidelines. All firewall rules are fine. I have even tried allowing all udp ports. This is terribly strange. Could this have anything to do with me using an NSU for dpnss between my sx2000 and 3300 ?
Im running out of idea's here!!!!!!!!!!!!!!!! Perhaps class of service settings/system option settings ? <----------------- I know.....clutching at straws ?????

 

[Mitelmatt]

you sure you've got a NAT so that phones on the LAN Talk to the EXTERNAL Address of the Teleworker not the Internal? That's normally the gottcha?

Also, in the Loacl Networks in the teleworker server, have you all the sub nets in there? Another cause of one way audio

 

[blackberry1980]

Yeah man, ive got nat settings correct. If this was wrong howcome an ip phone sitting off the 3300 gateway can do two way trans fine. The subnet is also defined in local networks form of the teleworker. Ill try to get the nat table and put it up here!

 

[Mitelmatt]

have you got any compression licences on the 3300?

You need these to convert the digital to IP signaling?