Dual NIC Source address issue routing calls to PBX

1. Brekeke Product Name and version:
2.3.8.2
2. Java version
Not Sure where to find this
3. OS type and the version:
2003 server service pack 2
4. UA (phone), gateway or other hardware/software involved:
Brekeke and Mitel
5. Select your network pattern from http://www.brekeke-sip.com/bbs/network/ ... terns.html :
See Problem
6. Your problem:

The brekeke is installed on a server that has 2 Nics installed... The first NIC is where the Clients are residing and is physically seperate network. The second NIC is where the Mitel PBX resides. I have a dial plan to route certain calls to the MITEL and this is working if I register a client from the Mitel network.
However if I try to place a call from a client registered on the other network where all my brekeke clients are the calls fail. I assume that this is because the Mitel does not support NAT...
Hope that makes some sense? Any help would be greatly appreciated.

Are they local IP addresses?
or are they public IP addresses?

Can you see registered client records in the [Registered Clients] page?

Can you make a call from client located in Mitel's network to another client located in another network?

Yes they are local IP addresses

Yes I can see registered clients

Not sure about calls from Mitel to another client this is the reverse of what I am trying to do and is not tested yet

Let me know both NIC IP addresses.

And write your all DialPlan rules here.

192.168.103.50 - Lan with Mitel Phone Switch

192.168.55.2 - Seperate LAN with Sip Clients

Rules
Match
$request=^INVITE
To=sip:(4.+)@
Deploy
To=sip:(4.+)@ To=sip:%1@192.168.102.50

What is the Mitel PBX's IP address?
Is the PBX registered in the SIP Server?
Do you have any other DialPlan rules?


>> However if I try to place a call from a client registered on the
>> other network where all my brekeke clients are the calls fail.

Is it busy tone?
Is it no audio?
Do you get any SIP response code?

The mitel is 192.168.102.50

the PBX is not registered in the SIP Server (not sure why it would be)

No other dial plans...

If call from any client registered to the brekeke on the mitel side of the network everything works fine..

if I call from the other side where the brekeke clients are the routing rule does work I can see it routing the call to the Mitel - however it gets stuck on provisioning and I receive no errors on ether end....

The key here is that from the brekeke side the only difference between the call that works and the call that does not is the source address

Below is taken from the active session window of the brekeke on a failed call.... you can see the source is 192.168.55.2... this is the only difference between a working call

1876 sip:100*203*1@192.168.55.2:5060
(192.168.55.1:5060) sip:4387@192.168.102.50
(192.168.102.50) 2010-03-01 10:52:23.703 Closing

Hi zoldy,

Since SIP Server's interface IP addresses are 192.168.103.50 and 192.168.55.2, it can not reach 192.168.102.50 ...
Because 192.168.102.x is a different subnet..

You need to assign a 192.168.103.x IP address to the Mitel.

Thanks for your input but that is not correct. Clients registered to the brekeke on the 103 interface can make calls to the mitel. As indicated my very first posts it is only clients registered on the 55 interface that can not call the Mitel.

So.. you have 3 local subnets.. 192.168.55.x, 192.168.102.x and 192.168.103.x...

From your posts, it seems 192.168.103.x can reach 192.168.102.50 but
192.168.55.x can not reach 192.168.102.50.

Is it possible to use 192.168.103.x as the Mitel's IP address?

I dont think you are understanding the setup yet. probably my fault for not explaining it right...

I have 2 phsically seperate networks
network one
101 102 and 103 subnets

Network two
55 subnet (nothing else)

The brekeke server has 2 nic cards one connected to each physical network

The bekeke can comunicate to ALL subnets

The problem I am trying to address is clients registered to the brekeke on the 55 network can not place calls successfully to the mitel

The only difference between the successfull call and the unsuccessfull call is the sourse address of course is 55

but it is not that it can not communicate with the mitel.

zoldy,
Okay.

Add 192.168.102.x address (e.g 192.168.102.51) as an interface IP address in the SIP Server's Windows Server.
And, restart the server.


You will see 192.168.102.51, 192.168.103.50 and 192.168.55.2 in the SIP Server's Status page as the Interface addresses.

Try this and make test calls.

No change .. same issue

What's IP address can you see at [interface] field in the [Server Status] page?

Did you set [RTP relay] = "on" in [Configuration] -> [RTP] page?

RTP relay is set to Auto

I see all three IP addresses on the status page

ok..
Set "RTP relay = on" and restart the server..

How about this?

No change... I have wireshark traces from both interfaces but I dont think I can attach them... to me it looks like it tries using a source address of 55.2 then repleces 55.2 with 103.50 but the user info is stripped and this is the problem... then the Mitel reports extension not found error..

Any way to show you the wireshark logs?

I recommend that you contact brekeke's technical support or reseller's support team to analyze a packet trace file..


by the way.. I wonder...
Can you make a call between clients located in different networks?

For example, can you make a call from a client located in 192.168.55.x to another client located in 192.168.102.x?