GOautodial Open Source Omni-channel Contact Center Suite

Hi Mark,

Yes, you just need to use your firewall or the built-in firewall of the Goautodial Server which is IPTables to forward the port you
want to port 5060.
Please see this link to give you an idea (http://serverfault.com/questions/140622/how-can-i-port-forward-with-iptables)

Hope that helps

Cheers
q^_^p

Thank you for your reply.

Could someone post the iptables file as it appears "out of the box" for GoAutoDial 3.0 CE? I was trying to follow a tutorial on iptables, and I issued the command "service iptables save", and it seems to have overwritten the iptables file with something completely different.

Aaaagh!

Thanks.

Here is the default content of /etc/sysconfig/iptables:

# Firewall configuration written by system-config-securitylevel
# Manual customization of this file is not recommended.
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:RH-Firewall-1-INPUT - [0:0]
-A INPUT -j RH-Firewall-1-INPUT
-A FORWARD -j RH-Firewall-1-INPUT
-A RH-Firewall-1-INPUT -i lo -j ACCEPT
# Uncomment line below if you have 2 NICs and eth1 is public
#-A RH-Firewall-1-INPUT -i eth0 -j ACCEPT
-A RH-Firewall-1-INPUT -p icmp --icmp-type any -j ACCEPT
-A RH-Firewall-1-INPUT -p 50 -j ACCEPT
-A RH-Firewall-1-INPUT -p 51 -j ACCEPT
-A RH-Firewall-1-INPUT -p udp --dport 5353 -d 224.0.0.251 -j ACCEPT
-A RH-Firewall-1-INPUT -p udp -m udp --dport 631 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A RH-Firewall-1-INPUT -m udp -p udp --dport 5060 -j ACCEPT
-A RH-Firewall-1-INPUT -m udp -p udp --dport 4569 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 21 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
#-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 222 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 443 -j ACCEPT
#-A RH-Firewall-1-INPUT -m tcp -p tcp --dport 3306 -j ACCEPT
#-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 10000 -j ACCEPT
-A RH-Firewall-1-INPUT -m udp -p udp --dport 10000:65535 -j ACCEPT
-A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited
COMMIT

Great! Thanks much for posting that. I was able to copy and paste it back into my iptables file, and I'm back in business.

Still haven't quite figured out how to received incoming calls on a port other than 5060, but I'm going to attempt to configure iptables to port-forward port 5061 to 5060, and hope that then will allow me to do what I want.

You can configure Asterisk to accept SIP on a different port. Edit /etc/asterisk/sip.conf and change the following entry:

bindport=5060                   ; UDP Port to bind to (SIP standard port is 5060)

to any port you need. And don't forget to also edit /etc/sysconfig/iptables to open the port.

Wow! Fantastic. I was struggling to figure out that iptables port forwarding, but this is SO much easier. I've made the settings changes to sip.conf and to iptables. Will let you know how it turns out.

OK, so I edited the bindport setting in /etc/asterisk/sip.conf and changed it to 5061. I then changed the settings in my Zoiper softphone to have the account be: 192.168.1.2:5061. I know the Zoiper phone registers with the GoAutoDial server (3.0 CE), because I was able to use Zoiper to call ext. 8168 and record and play back an answering machine message. Everything worked fine with that.

So, I can conclude from this much, that the changes I also made to iptables worked properly (to open up port 5061), because I would never have been able to use Zoiper to call and interact with the system otherwise.

However, when I then go to log-on to the system as an Agent, the system does not call Zoiper as it's supposed to do. The log-in screen appears, I put in the username and password, and choose a campaign (same campaign I have been working on, which worked just fine when I had port 5060), click on the Login button, I get a few seconds delay during which the message "loading" appears on the screen, and then I see the goagent display. But, I never get a call to my Zoiper softphone!

I must be missing something here... Is it possible that I need to change iptables to allow for an OUTPUT on port 5061? But, that doesn't seem to make sense, because how would I have been able to have 2-way communication with the system via Zoiper if that were true?

I think I've figured out that the fact that the system is not calling my softphone must be due to something other than the non-standard SIP port.

I changed the bindport back to 5060, changed the settings on my Zoiper to corresponds. The phone registered, I was able to call 8168 and hear and be heard. But, still no call to the softphone when I logged in as an agent.

So, what could be causing that?

Hi,

What audio codecs are currently set on your softphone? Can you also post your asterisk CLI logs while logging in.

Regards,
Ryan

Hello.

I'm using ulaw codec, according to the Zoiper status info. See below for the contents of the "messages" file in /var/log/asterisk. (Not sure if this is what you're looking for, but I notice the thing about the conference not existing!

[Jun 30 20:53:02] VERBOSE²⁶⁸⁴⁵ logger.c: [Jun 30 20:53:02] Parsing '/etc/asterisk/manager.conf': [Jun 30 20:53:02] VERBOSE[26845] logger.c: [Jun 30 20:53:02] Found
[Jun 30 20:53:02] VERBOSE[26845] logger.c: [Jun 30 20:53:02] Manager 'sendcron' logged on from 127.0.0.1
[Jun 30 20:53:02] VERBOSE²⁶⁸⁵⁰ logger.c: [Jun 30 20:53:02] Parsing '/etc/asterisk/manager.conf': [Jun 30 20:53:02] VERBOSE[26850] logger.c: [Jun 30 20:53:02] Found
[Jun 30 20:53:02] VERBOSE[26850] logger.c: [Jun 30 20:53:02] Manager 'sendcron' logged on from 127.0.0.1
[Jun 30 20:53:02] VERBOSE²⁶⁸⁵⁰ logger.c: [Jun 30 20:53:02] Manager 'sendcron' logged off from 127.0.0.1
[Jun 30 20:53:02] VERBOSE[26856] logger.c: [Jun 30 20:53:02] Parsing '/etc/asterisk/manager.conf': [Jun 30 20:53:02] VERBOSE²⁶⁸⁵⁶ logger.c: [Jun 30 20:53:02] Found
[Jun 30 20:53:02] VERBOSE²⁶⁸⁵⁶ logger.c: [Jun 30 20:53:02] Manager 'sendcron' logged on from 127.0.0.1
[Jun 30 20:53:02] VERBOSE[26856] logger.c: [Jun 30 20:53:02] Manager 'sendcron' logged off from 127.0.0.1
[Jun 30 20:53:02] VERBOSE²⁶⁸⁵⁷ logger.c: [Jun 30 20:53:02] Parsing '/etc/asterisk/manager.conf': [Jun 30 20:53:02] VERBOSE[26857] logger.c: [Jun 30 20:53:02] Found
[Jun 30 20:53:02] VERBOSE[26857] logger.c: [Jun 30 20:53:02] Manager 'sendcron' logged on from 127.0.0.1
[Jun 30 20:53:02] VERBOSE²⁶⁸⁵⁸ logger.c: [Jun 30 20:53:02] -- Executing [55558600051@default:1] MeetMeAdmin("Local/55558600051@default-d652,2", "8600051|K") in new stack
[Jun 30 20:53:02] WARNING²⁶⁸⁵⁸ app_meetme.c: Conference number '8600051' not found!
[Jun 30 20:53:02] VERBOSE²⁶⁸⁵⁸ logger.c: [Jun 30 20:53:02] -- Executing [55558600051@default:2] Hangup("Local/55558600051@default-d652,2", "") in new stack
[Jun 30 20:53:02] VERBOSE²⁶⁸⁵⁸ logger.c: [Jun 30 20:53:02] Spawn extension (default, 55558600051, 2) exited non-zero on 'Local/55558600051@default-d652,2'
[Jun 30 20:53:02] VERBOSE[26858] logger.c: [Jun 30 20:53:02] -- Executing [h@default:1] DeadAGI("Local/55558600051@default-d652,2", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16---------------") in new stack
[Jun 30 20:53:02] VERBOSE[26858] logger.c: [Jun 30 20:53:02] -- AGI Script agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16--------------- completed, returning 0
[Jun 30 20:53:02] VERBOSE[26857] logger.c: [Jun 30 20:53:02] Manager 'sendcron' logged off from 127.0.0.1
[Jun 30 20:53:03] VERBOSE²⁶⁸⁴⁵ logger.c: [Jun 30 20:53:03] Manager 'sendcron' logged off from 127.0.0.1
[Jun 30 20:53:07] VERBOSE[26865] logger.c: [Jun 30 20:53:07] Parsing '/etc/asterisk/manager.conf': [Jun 30 20:53:07] VERBOSE²⁶⁸⁶⁵ logger.c: [Jun 30 20:53:07] Found
[Jun 30 20:53:07] VERBOSE²⁶⁸⁶⁵ logger.c: [Jun 30 20:53:07] Manager 'sendcron' logged on from 127.0.0.1
[Jun 30 20:53:07] VERBOSE[26865] logger.c: [Jun 30 20:53:07] Manager 'sendcron' logged off from 127.0.0.1
[Jun 30 20:53:20] VERBOSE²⁶⁸⁸⁵ logger.c: [Jun 30 20:53:20] Parsing '/etc/asterisk/manager.conf': [Jun 30 20:53:20] VERBOSE[26885] logger.c: [Jun 30 20:53:20] Found
[Jun 30 20:53:20] VERBOSE[26885] logger.c: [Jun 30 20:53:20] Manager 'sendcron' logged on from 127.0.0.1
[Jun 30 20:53:20] VERBOSE²⁶⁸⁸⁶ logger.c: [Jun 30 20:53:20] -- Executing [8300@default:1] Hangup("Local/8300@default-cf51,2", "") in new stack
[Jun 30 20:53:20] VERBOSE²⁶⁸⁸⁶ logger.c: [Jun 30 20:53:20] Spawn extension (default, 8300, 1) exited non-zero on 'Local/8300@default-cf51,2'
[Jun 30 20:53:20] VERBOSE[26886] logger.c: [Jun 30 20:53:20] -- Executing [h@default:1] DeadAGI("Local/8300@default-cf51,2", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16---------------") in new stack
[Jun 30 20:53:20] VERBOSE[26886] logger.c: [Jun 30 20:53:20] -- AGI Script agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16--------------- completed, returning 0
[Jun 30 20:53:20] VERBOSE[26885] logger.c: [Jun 30 20:53:20] Manager 'sendcron' logged off from 127.0.0.1
[Jun 30 20:54:01] VERBOSE²⁷⁰⁷⁶ logger.c: [Jun 30 20:54:01] Parsing '/etc/asterisk/manager.conf': [Jun 30 20:54:01] VERBOSE[27076] logger.c: [Jun 30 20:54:01] Found
[Jun 30 20:54:01] VERBOSE[27076] logger.c: [Jun 30 20:54:01] Manager 'sendcron' logged on from 127.0.0.1
[Jun 30 20:54:01] VERBOSE²⁷⁰⁷⁶ logger.c: [Jun 30 20:54:01] Manager 'sendcron' logged off from 127.0.0.1
[Jun 30 20:54:01] VERBOSE[27078] logger.c: [Jun 30 20:54:01] Parsing '/etc/asterisk/manager.conf': [Jun 30 20:54:01] VERBOSE²⁷⁰⁷⁸ logger.c: [Jun 30 20:54:01] Found
[Jun 30 20:54:01] VERBOSE²⁷⁰⁷⁸ logger.c: [Jun 30 20:54:01] Manager 'sendcron' logged on from 127.0.0.1
[Jun 30 20:54:02] VERBOSE[27078] logger.c: [Jun 30 20:54:02] Manager 'sendcron' logged off from 127.0.0.1
[Jun 30 20:54:06] VERBOSE²⁷⁰⁹⁴ logger.c: [Jun 30 20:54:06] Parsing '/etc/asterisk/manager.conf': [Jun 30 20:54:06] VERBOSE[27094] logger.c: [Jun 30 20:54:06] Found
[Jun 30 20:54:06] VERBOSE[27094] logger.c: [Jun 30 20:54:06] Manager 'sendcron' logged on from 127.0.0.1
[Jun 30 20:54:06] VERBOSE²⁷⁰⁹⁴ logger.c: [Jun 30 20:54:06] == Manager 'sendcron' logged off from 127.0.0.1

Hi,

I really need help on this. I'm totally dead in the water - can't make a single call, because I can't get the system to dial my softphone (Zoiper) at the start of the agent login process.

I've verified that I can make outgoing calls - in the sense that the system will dial the number. But, of course, I can't talk to anyone, because I'm not connected to the conference!

The softphone registers, using the ulaw codec, and I can verify this by dialing 8168 and getting the voice prompt, and record something - all of this works.

But, meanwhile, I'm totally paralyzed.

Should I start a new thread under the Help area, perhaps? This is no longer about a non-standard sip port number.

I've tried different things to get more detail on what might be causing it - clearly the fact that the system cannot "find" the conference room is a problem (see above posting of the "messages" file from /var/log/asterisk/) . But what might have caused this, I haven't a clue, much less how to fix it.

By the way, I guess I should say too, that I've gone back to port 5060 - that is, I've changed the bindport setting back to 5060, and went back to the "stock" iptables as posted earlier in this thread, hoping I could retrace my steps, as it were, and get back to a working system.

This is the problem. The system is trying to call your agent. However, it looks like there are no meetme conferences configured. This usually happens if you have changed the IP address of your GOautodial server and did not update the vicidial_conferences tables. You can do this by running "update_server_ip".

[Jun 30 20:53:02] VERBOSE26858 logger.c: [Jun 30 20:53:02] -- Executing [55558600051@default:1] MeetMeAdmin("Local/55558600051@default-d652,2", "8600051|K") in new stack
[Jun 30 20:53:02] WARNING26858 app_meetme.c: Conference number '8600051' not found!