OXE GD3 static route

[OXE_4400]

It is possible to add static route through netadmin in OXE CS.
How will behave GD3 board? Can we do similar on it?

[Guest]

no, maybe it works if you set up a static route with the route command in linux subsystem, but it is not designed to statically save it in configuration.

regards...

[tgn]

no, maybe it works if you set up a static route with the route command in linux subsystem, but it is not designed to statically save it in configuration.

regards...

[OXE_4400]

But it is strange. netadmin allows to enter static route, but it seems no way for GD3

[tgn]

yes !
but network design guide says callserver has to be in a seperate subnet than the other equipment...

regards...

[OXE_4400]

OK, but I don't see conflict between GD placement in separate subnet and need to manage static routes. There are 2 different things.

[tgn]

not really a conflict... but the callserver is 'designed' to work in a central server subnet (with maybe more than one router and a static ip-address) and the gd is 'designed' to work in the 'endpoint' subnet just like an ip phone (with only one default-router and the possibility to get ip-addressdata from a dhcp server).
so the restriction is only made by the 'design'.

regards...

[vad]

Just for understanding - for what you want to use static route? For signalling (GD-CS) or for RTP for TDM users from rack (GD-???).

[OXE_4400]

For RTP between TDM environment (PRA, UA) on rack and VoIP phones or SIP trunking.