Solved

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

Posted on 2011-09-15
8
820 Views
Last Modified: 2012-05-12
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
Comment
Question by:tsukraw
  • 6
  • 2
8 Comments
 

Author Comment

by:tsukraw
ID: 36546082
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
 
LVL 25

Expert Comment

by:Ron M
ID: 36546383
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
 

Author Comment

by:tsukraw
ID: 36546398
vpn tunnel.  Should that be nat=no?
0
 

Author Comment

by:tsukraw
ID: 36547095
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
DevOps Toolchain Recommendations

Read this Gartner Research Note and discover how your IT organization can automate and optimize DevOps processes using a toolchain architecture.

 

Assisted Solution

by:tsukraw
tsukraw earned 0 total points
ID: 36547194
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
 
LVL 25

Accepted Solution

by:
Ron M earned 500 total points
ID: 36549280
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
 

Author Closing Comment

by:tsukraw
ID: 36941237
Figured out the issue.
0
 

Author Comment

by:tsukraw
ID: 36918308
Please Close
0

Featured Post

3 Use Cases for Connected Systems

Our Dev teams are like yours. They’re continually cranking out code for new features/bugs fixes, testing, deploying, testing some more, responding to production monitoring events and more. It’s complex. So, we thought you’d like to see what’s working for us.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

In my office we had 10 Cisco 7940G IP phones that were useless as they were showing PROTOCOL APPLICATION INVALID when started. I searched through Google and worked for a week continuously on those phones, and finally got them working. This is a di…
Although VoiceOver IP has been around for a while, internet connections have only recently become fast enough to provide good call quality. Now, VoIP has become a real option for businesses looking at ways to improve their business model. In this ar…
Along with being a a promotional video for my three-day Annielytics Dashboard Seminor, this Micro Tutorial is an intro to Google Analytics API data.
As a trusted technology advisor to your customers you are likely getting the daily question of, ‘should I put this in the cloud?’ As customer demands for cloud services increases, companies will see a shift from traditional buying patterns to new…

864 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

24 Experts available now in Live!

Get 1:1 Help Now