TUTORIAL U Need Travelin' Man

Greeting Ward, et. al.,

First -- Thanks for all of your great work!

I've got traveling man working, but it works for inbound calls only. I can never ring the external softphone from anywhere behind the firewall. Calls into any of the extensions behind the firewall with the server work fine and I can also place calls to real world phones. However, I can not ever call the traveling man extension from any of the extensions inside the firewall.

I followed the instructions in the article, forwarded the ports as instructed, etc. When try calling extension 501, I get error code 503 shown on the internal extension I'm dialing from. If I phone into the server from a phone from the outside world and then try dialing out to extension 501, I get the voice message "Your call cannot be completed as dialed..."

I thought that once the remote extension successfully registers with the server, that the server should be able to communicate back to the remote extension...

I've posted this problem elsewhere but haven't gotten any responses, so I'm stumped. Is traveling man supposed to permit dialing out to the remote extension? If so, how should I troubleshoot this? Any help is greatly appreciated.

Thanks,
Don

This is probably a very basic (stupid) question but I've looked and haven't yet found the reason... IAX uses a single port for everything and from what I have read, is much better at traversing NAT, etc. while keeping audio intact. And it seems to have other advantages over SIP. If this isn't correct, please help me to better understand.

So then why is using a SIP softphone vs. an IAX softphone better? Or what I'm actually asking is what is the advantage of using a remote SIP softphone instead of a remote IAX softphone?

And if using an IAX softphone, shouldn't/couldn't something akin to traveling man be used to open that port for only when it is needed by the legitimate remote IAX softphones? That way iptables could also protect the IAX port.

Thanks,
Don

No Audio

Hello,

I have been experimenting with Travelin' Man, and while my remote extension connects and registers there is no audio in either direction when calls are made.

If possible, I'd also like to be able to take advantage of calling features such as wake-up calls.

The setup is PIAF Purple on an Intel Atom 330 Mini-ITX board, 2GB RAM, 160GB Hard Drive behind a Linksys WRT54GS-based router (DD-WRT), UDP ports opened as per setup instructions. 10000-20000 open as well.
24Mbps Down/1Mbps Upload connection.
On the remote end, I have a Linksys PAP2T behind a Linksys E1000 router.
Do I need a STUN Server? Please let me know what I've done wrong, or what else needs to be done.

Thanks,
Ram

PIAF Purple:
Asterisk = ONLINE | Zap/Dahdi = UNKNOWN | MySQL = ONLINE │
│ SSH = ONLINE | Apache = ONLINE | Iptables = ONLINE │
│ Fail2ban = ONLINE | Internet = ONLINE | Ip6Tables = ONLINE │
│ BlueTooth = ONLINE | Hidd = ONLINE | NTPD = ONLINE │
│ SendMail = ONLINE | Samba = ONLINE | Webmin = ONLINE │
│ Ethernet0 = ONLINE | Ethernet1 = N/A | Wlan0 = N/A │
│ │
│ PBX in a Flash Version = 1.7.5.6 Running on *HARDWARE* │
│ FreePBX Version = 2.8.1.4 │
│ Running Asterisk Version = 1.8.4.1 │
│ Asterisk Source Version = UNKNOWN │
│ Zap/Dahdi Source Version = N/A │
│ Libpri Source Version = UNKNOWN │
│ IP Address = 192.168.1.105 on eth0 │
│ Operating System = CentOS release 5.7 (Final) │
│ Kernel Version = 2.6.18-238.19.1.el5 - 32 Bit │

Thanks for the prompt reply. The script says it works on CentOS 6+, and I'm running 5.7. Do I have to upgrade the CentOS first? Should I take the plunge and upgrade the whole system to the latest PIAF/Incredible PBX?

Thanks for the prompt reply. I appreciate the information and I'll post back in a day or so when I'm able to get to the remote location to do the updates.

Just out of curiosity, is TravellinMan still available and does it work on the latest PbxIaf and incredible PBX3?

Joe

Ward is this the TravilingMan2 script ?

http://incrediblepbx.com/travelinman2.tar.gz

or a new one for IncrediblePBX 3

I am copying a conversation from Google discussion:

Me: I have a question... Let's say my primary place is defined as FQDN (myplace.dyn.com). Everything is fine until IP changes. ipcheck goes through *.iptables, but the primary FQDN doesn't have associated *.iptables file. So, as soon as IP changes, I'll be locked.

Is this analysis correct? For now I created primary .iptables similar to other files that get created as result of add-fqdn. Can't hurt even if I am wrong

Ross Lindsay
They way TM works with FQDNs is that the IPChecker script checks for IP changes, and if the IP changes, updates the applicable rules in IPTables and removes the old ones.
Me:
I am sorry, Ross - either you misunderstand my question, or I misunderstand your answer... IPChecker script checks for IP changes of what? Isn't it running through account array that lists *.iptables files?

So, my question still remains: as implemented, wouldn't ipchecker miss the change in the IP of the primary FQDN?