Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 876
  • Last Modified:

FreePBX/Trixbox Cannot keep a active trunk with 3com VCX

I am in the process of replacing a Trixbox with a updated FreePBX system which trixbox is based on FreePBX interface so the setup is almost the same.  The configurations from the one has been manually transferred to the other system. We are running into a issue where the FreePBX <=> VCX keeps losing its connection.
This worked fine in the past when it was on the Trixbox we ran it no problems at all.
On the FreePBX we keep seeing the below errors.

FreePBX is at 192.168.0.34
VCX is at 192.168.100.190

We are positive without a double there is NO network disruption or anything between the VCX and FreePBX.

Does anyone have any ideas on the cause?

Here is the trunk config
allow=ulaw
canreinvite=no
context=from-pstn
disallow=all
host=192.168.100.190
insecure=very
nat=yes
port=5060
qualify=yes
type=peer


allow=ulaw
canreinvite=no
context=from-pstn
disallow=all
host=192.168.100.190
insecure=very
nat=yes
port=5060
type=user



[2011-09-15 15:30:30] NOTICE[3163]: chan_sip.c:24251 handle_request_register: Registration from '<sip:192.168.0.34>' failed for '192.168.100.190:5060' - No matching peer found
[2011-09-15 15:30:39] NOTICE[3163]: chan_sip.c:20169 handle_response_peerpoke: Peer 'VCX' is now Reachable. (83ms / 2000ms)
[2011-09-15 15:32:27] NOTICE[3163]: chan_sip.c:24251 handle_request_register: Registration from '<sip:192.168.0.34>' failed for '192.168.100.190:5060' - No matching peer found
[2011-09-15 15:34:27] NOTICE[3163]: chan_sip.c:24251 handle_request_register: Registration from '<sip:192.168.0.34>' failed for '192.168.100.190:5060' - No matching peer found
[2011-09-15 15:36:27] NOTICE[3163]: chan_sip.c:24251 handle_request_register: Registration from '<sip:192.168.0.34>' failed for '192.168.100.190:5060' - No matching peer found
[2011-09-15 15:38:27] NOTICE[3163]: chan_sip.c:24251 handle_request_register: Registration from '<sip:192.168.0.34>' failed for '192.168.100.190:5060' - No matching peer found

Open in new window

0
tsukraw
Asked:
tsukraw
  • 6
  • 2
2 Solutions
 
tsukrawAuthor Commented:
One thing i should add is VCX does not do any kind of authentication for PBX to PBX connections.  You just add the source IP as a trusted IP address and it will accept any incoming SIP connections.
0
 
Ron MalmsteadInformation Services ManagerCommented:
I noticed you changed the type from user to peer..or visa versa.  Have you tried using type=friend?

Also, I see  nat=yes    are you sure that is correct?   How are the two networks connected?  vpn? public ip's? direct link?
0
 
tsukrawAuthor Commented:
vpn tunnel.  Should that be nat=no?
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
tsukrawAuthor Commented:
I think you miss understood my posting
The top part was the outgoing trunk settings bottom was incoming.
.:OUTGOING:.
allow=ulaw
canreinvite=no
context=from-pstn
disallow=all
host=192.168.100.190
insecure=very
nat=yes
port=5060
qualify=yes
type=peer

.:INCOMING:.
allow=ulaw
canreinvite=no
context=from-pstn
disallow=all
host=192.168.100.190
insecure=very
nat=yes
port=5060
type=user
0
 
tsukrawAuthor Commented:
Ok i know i am going to sound like a idiot here but figured out what the cause was....
FreePBX has a new feature that trixbox didnt have... "Intrusion Detection"  It would auto ban the VCX if it thought it was trying to intrude in...That is why it was working some times and other times not since it was a timed ban...
I discovered this when i was doing a PING from the FreePBX to the VCX.  I could do a ping just fine then it would randomly stop even though i could ping other devices just fine on the 192.168.100.x network.

When i initially did the testing of the network it must have been in its working period cause the ping worked.

0
 
Ron MalmsteadInformation Services ManagerCommented:
Got it.


To answer your question, If it's a vpn tunnel you don't need NAT, unless NAT is applied to the tunnel.  In most cases it isn't.
0
 
tsukrawAuthor Commented:
Figured out the issue.
0
 
tsukrawAuthor Commented:
Please Close
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 6
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now