Did I screw up my system big time?

[johnnypuffs]

Hey all,

Thanks to everyone involved in this project. Amazing! I just stumbled across this a few weeks ago and have probably logged 100 hours reading, setting up, etc. Know enough about Linux to be dangerous, but the Asterisk/FreePBX/Incredible is all new to me...

So I had my box setup working perfectly with the new install of PBX in a Flash 1.7.5.5 Purple Edition with Asterisk 1.8.0 with Incredible PBX. Everything was working great. Multiple inbound/outbound Gvoice DIDs, multiple IVRs, etc.

Last night I came across this thread about TCP transport for Endpoints:

http://pbxinaflash.com/community/threads/tcp-transport-for-endpoints.8606/?t=8606

When out and about I use Bria on my iPhone and iPad so wanted to enable this. I went ahead and followed the instructions to a T but it did not work. What happened is my whole system seemed to be down. Extensions would not register, etc.

I am not sure, but I think the cause of the issue was me entering the TCP settings in "Asterisk SIP Settings" as outlined in the post. When I entered this it through an error that an external IP must be set to continue. I hit the auto-configure button, all the information was correct, so I added my two TCP lines and submitted and applied the config changes. After this is when the issues started happening.

I noticed then that my sip_general_additional.conf had grown from a few parameters to 46 lines. Many of which seem to conflict with other settings. The file says to not modify manually (so I did not). I can't go into "Asterisk SIP Settings" to modify as if I remove my external IP to have it setup as it was before it won't allow the change.

I removed the lines referenced in the post above from "sip_custom_post.conf " and I finally ran update-sources and reloaded (however many times it asked), then ran update-programs & update-fixes. From there everything now APPEARS to be working normally. (Still no TCP transport of course)

However, my Asterisk SIP Settings remain in the state they were after changing them in the GUI.

Is this going to cause me issues somewhere down the line?
How can I restore these settings to what they were?

I have attached my "sip_general_additional.conf" so you can see my settings..


Thanks in advance for any advice for this newb!

John

 

[wardmundy]

Lesson #1: If everything is working perfectly, leave it alone!

I'd start over but...

Check /etc/sysconfig/iptables. Do you see lines like the following:

# Allow TCP SIP connections
-A INPUT -p tcp -m tcp --dport 5060 -j ACCEPT

If not, add them and then: service iptables restart

 

[johnnypuffs]

Thanks Ward,

Yes, iptables and my hardware router are both set to allow TCP on Port 5060.

I'll try and get TCP working again, but am more concerned about the status of the system right now. I can of course, start over, but would rather not as I have a rather in depth IVR, multi tenant system I don't want to reconfigure.

I guess my main questions are:

1. Running update-source, update-programs and update-scripts should not cause the system harm, correct? I mean is that not what they are there for?

2. The biggest concern is that those settings in the attached file (from submitting "Asterisk SIP settings") are going to be an issue. I have another local machine configured as well as a hosted box at rentpbx.com and neither have anything configured in those settings for external IP, etc.

It almost appears as though the FreePBX/Incredible system ignores those settings. Is that correct?

If not should I just manually update the sip_general_additional.conf back to it's original state? Or is there no harm in having it the way it is?

As I said everything besides TCP SIP is working just as it was before..

As far as TCP SIP, the IP tables and hardware firewall are set correctly. sip_general_custom.conf has the additional lines for TCP:

;placeholder for future expansion PIAF Dev Team
rtptimeout=120
videosupport=yes
allow=h263
tcpenable=yes
tcpbindaddr=0.0.0.0

I took out the extension code lines from sip_custom_post.conf:

 [710](+)
transport=tcp

One thing I did not mention which may be relevant.. I have installed travelinman.. so I have the 701.inc, 702.inc, etc. files

It almost looks to me like that is where the transport=tcp code should go?

Thanks again for the help!

John

Lesson #1: If everything is working perfectly, leave it alone!

I'd start over but...

Check /etc/sysconfig/iptables. Do you see lines like the following:





If not, add them and then: service iptables restart

 

[wardmundy]

Using the tcp transport mechanism puts you on the bleeding edge. You really need a second system to test things out, or you may be rebuilding frequently. I haven't used tcp yet, and you've convinced me to wait a bit longer.

 

[johnnypuffs]

Thanks Ward.. If I get it running, I'll post up about the steps involved..