Multiple ELU32's on separate networks and IP Extensions?

[ADB100]

My understanding is that if I want multiple ELU32's in an MD110 then they all need to be on the same subnet if they are in the same LIM? If I want to spread the modules over several LIM's then they each need to be on separate IP subnets.

If for example I have ELU32 #1 in LIM #1 (192.168.1.1/24) and ELU32 #2 in LIM #2 (10.1.1.1/24) and the IP networks are physically separate - i.e. there is no physical or logical path between the 2 networks (192.168.1.0/24 and 10.1.1.0/24). What happens if IP Phones registered to ELU32 #1 want to call IP Extensions regsitered to ELU32 #2? Do they attempt to use IP or do they go via the MD110?

Thanks

Andy

 

[fouesnant]

Hi Andy

If you don't have sepcify router in the IPBOI command for ELU32, then the MD110 will consider this as Gateway call and pass it normally thru the TDM connection

 

[ADB100]

Thanks for the reply, although I am not quite sure I understand you.

The scenario is this - An existing MD110 with ELU32 cards and IP extensions currently working. A new site is to be connected but this must remain completely separate from the existing LAN/WAN, there is no IP connectivity between the existing and new LAN/WAN. Therefore 2 new ELU32 cards will be installed in a LIM and configured with IP addresses 10.1.1.1 and 10.1.1.2 (24-bit mask). These cards will connect into a private LAN that has a router (address 10.1.1.254) that connects to a remote site where several IP phones will be. These IP phones will be on subnet 10.1.2.0/24 and will use DHCP.

What happens when an IP handset on the existing network attempts to call an IP handset on the new (10.1.2.0/24) network? Will it attempt to go IP to IP or will it terminate on the MD110 and then re-emerge (so to speak) out of one of the new ELU32 cards?

Thanks

Andy

 

[fouesnant]

Hello

It is explained in Alex, Extra Facilites, IP extenion, Decription of the Extra facility, Description
1.5 Functional overview
In order to completely integrate the IP extension in the ASB 501 04 architecture, it is necessary to have the functionality of two entities defined in the ITU-T H.323 standard:

The Gatekeeper, which basically deals with address translation, bandwidth management, admission control and call management regarding IP terminals.
The Gateway, which provides real time, two-way communication between IP terminals on the IP network and other terminals in the switched circuit network, or even IP terminals in other IP networks.
Both functionalities are performed by software units and firmware/hardware units:

The GK services are provided by the software units. There can only be one GK per LIM.
The ELU32 provides the GK interface. Every ELU32 board in a LIM may be used as GK interface.
The GW functionality is provided by the ELU32 board, the LIM switch and the associated software units.
Media (i.e., voice) transmission in calls between an IP terminal and any other type of extension or trunk is made through the ASB 501 04. Media transmission between two IP terminals belonging to the same IP network can pass directly through the IP network.

That mean, as the existing ELU32 as no route to go to other LAN, the voice and signalling goes directly thru the MD110.

Take also into consideration that there is GK protocol that knows how to reach each other.

 

[Isinor]

Hi,

You can have 2 networks each connected to a different LIM. But 2 networks to 1 LIM is not allowed. Well that’s what ALEX says...

Also from ALEX...
In a multi-LIM system it is possible to find that different LIMs are connected to different IP network segments (LANs). The network topology could change dynamically (e.g. the router between two LANs fails).

All the LIMs in ASB 501 04 have information about to which LIMs it has connectivity through the IP network (network path). Every LIM runs periodically a routine to update its information about the IP network topology. Based on this information, ASB 501 04 considers if a call between H.323 parties (extensions or trunks) is Gateway Call or Non Gateway Call.

This routine is started from every LIM by sending an inquiry to the rest of non-isolated/blocked LIMs in the system by means of inter-LIM signalling. If there is IP network path between the inquiring and the inquired LIM, a RAS NonStandardMessage with the suitable information is returned by the inquired LIM. The time before a new LIM is inquired may be modified by O&M command.

Since the routine is performed periodically (n seconds * Number of non-isolated/blocked LIMs) the GW/NGW condition may not be up to date at the moment of a call. This may be noticed in wide multi-LIM systems.

This routine can be disabled by O&M command.

IPGKC:LIM=...,TIMNET=...;

The TIMNET parameter states the time in seconds for executing the network topology discovery routine in the gatekeeper of a specific LIM.

Regards
Isinor