Incoming or outgoing calls do not work

jbrukardt

New Member
Joined
Mar 23, 2010
Messages
35
Reaction score
0
Ok, I just dont get this anymore. Im going to go through step by step, so someone can tell me what idiot step im missing maybe.

Made a brand new google voice account, and configured it as follows:

2jbqxb8.png


Confirmed the number, made sure it works, made sure im never logged into the account.

Downloaded PIAF-1.7.5.5.5-CentOS-5.5-32bit. Have also tried PIAF-1.7.5.5.4-CentOS-5.5-32bit with the same result. Always select PIAF purple.:

14ubda8.png


Followed this guide to a T:

http://nerdvittles.com/?p=712

Got the asterisk server up and running:

331dabb.png


2n096rs.png


Made sure port 5222 was forwarded, as well as other sip ports just in case once just 5222 didnt work

2qc2gpw.png


Registered both my xlite softphone, and my snom m3. Both connect fine.

2poxro7.png


Try to dial a number, any number (my cell phone, 1800 numbers, my relatives phones) and always get this same result

http://pastebin.com/UWycLdca

Things ive tried thus far:

Putting the pbx server in the dmz temporarily
Installing on a dedicated machine
Installing in VMware
Installing in Virtualbox
Forwarding extra ports (5000-5082 and 10000-20000)
Reinstalling about 8 times with different versions of the iso
Calling the gvoice number results in no activity in the log at all

Other things on the network:
Linksys CIT400 Skype gateway (tried unplugging this, problems still occur)
2 PCs
Snom M3

I dont get it... I thought my problems were related to the virtualization at first, but im having identical issues on the physical dedicated box.
 
Where's the Incrediblepbx download and install that's part of the article in your nerdvittles link?

cd /root
wget http://incrediblepbx.com/incrediblepbx18.x
chmod +x incrediblepbx18.x
./incrediblepbx18.x
passwd-master

I did do just what you've done plus the Incrd. Pbx part and haven't been able to get it to work but it may be my hardware...

Brian
 
What happens when you dial out? I was getting a SEG Fault and an Asterisk restart but again it may be hardware for me and something else for you...

Got a CLI trace?
 
Make sure you don't post anything you don't want public in terms of acct names or numbers.... Let's see what Ward has to say when he sees this. Looks like your system got further than mine...
 
My (working) test is identical to your down to line 81 - mine continues with the following:

2011-01-12 22:03:31] DEBUG[2738] chan_gtalk.c: redirect [email protected]/srvres-MTAuMTMuMzkuMTk6OTgxNQ==
[2011-01-12 22:03:31] VERBOSE[21778] app_dial.c: -- Gtalk/[email protected] is ringing
[2011-01-12 22:03:31] VERBOSE[21777] app_dial.c: -- Local/5555551212@gvoice-11ab;1 is ringing
[2011-01-12 22:03:37] VERBOSE[2728] asterisk.c: -- Remote UNIX connection
[2011-01-12 22:03:59] DEBUG[2738] chan_gtalk.c: The client is guest
[2011-01-12 22:03:59] VERBOSE[21778] app_dial.c: -- Gtalk/[email protected] answered Local/5555551212@gvoice-11ab;2
[2011-01-12 22:03:59] VERBOSE[21777] app_dial.c: -- Local/5555551212@gvoice-11ab;1 answered SIP/703-00000000

I can't tell what yours isn't doing, but maybe one of the folks more involved with the design/build of the Gtalk/Jabber interface can point you in the right direction based on what my trace points to.

Jeff
 
Make sure you don't post anything you don't want public in terms of acct names or numbers.... Let's see what Ward has to say when he sees this. Looks like your system got further than mine...

yeah, i edited out the digits of my number and email. theyre consistent, so they shouldnt change the diagnosis, just not my real ones.
 
What type router/firewall?? Looks to be blocking the calls. The fact that it fails on a stand-alone box and your VM kinda confirms where the problem lies.
 
Yeah, its kind of the one factor left.

Its an Actiontek MI424. FIOS MoCa Router. Its a really common router, I think someone else might have had the same problems if that was the case.

Service is fios 50/50 mbit.

As mentioned, ive tried putting it in the DMZ (which i know is horribly reliable, but should at least eliminate forwarding issues)
 
A couple of thoughts:

At the CLI, do jabber show connections and make use that you are actually showing "Connected" on your Google Voice accounts. If you typo'ed a username or password, that might cause the problem, so making sure you're connected is a very important check.

Also, if you think it might be a firewall issue, you can tell for sure by getting ready to place a call, then from a Linux prompt doing:

service iptables stop

As soon as the firewall has dropped, try placing your call, and as soon as you know whether that makes a difference, do:

service iptables start
service fail2ban restart

or maybe better yet, reboot the system if you want to make 100% sure that everything is restarted. Note that turning off your firewall can be very dangerous, so don't leave it off for any longer than is absolutely necessary to determine whether you really do have a firewall issue.
 
Authorization name should be: 702
Domain Proxy should be: 192.168.1.12; with either Domain or Proxy
 
Same issue here

If I stop IPtable and say yes anonymous inbound sip call and can receive the calls.

IPTable ON and Anonymous NO - I get no in or out calls
 
If I stop IPtable and say yes anonymous inbound sip call and can receive the calls.

IPTable ON and Anonymous NO - I get no in or out calls

That's two separate things. What happens if you leave IPtables running but say yes to anonymous inbound SIP? If that works it typically means you have a configuration error somewhere - might be as simple as not using the correct DID value in your inbound route (this will be different depending on whose instructions you are following, so make sure you're not mixing instructions or just going through the instructions hit-and-miss). It could also mean something's not quite right in one of your configuration files.

What happens if you leave anonymous inbound SIP set to no but drop the firewall? If that works then the issue is that your firewall is too restrictive. Note that the Jabber protocol uses port 5222 so you may need to make sure your firewall is allowing traffic to pass to your server on that port. From the Linux command prompt type:

iptables -nL

And hit enter and see if you see a line such as this (which must be higher in the list than any general blocking rules):

ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:5222

If not, that may be the problem. If you have Webmin, you can use that to view and edit your firewall rules (Networking | Linux Firewall).

And if you have to have both set to NO before it will work, then you'll have to address both of the above issues.
 
will be home in half an hour to test these things. Thanks for the advice thus far


edit: one would think that a preconfigured built directly designed for gvoice would have proper firewall setup though.
 
A couple of thoughts:

At the CLI, do jabber show connections and make use that you are actually showing "Connected" on your Google Voice accounts. If you typo'ed a username or password, that might cause the problem, so making sure you're connected is a very important check.

Also, if you think it might be a firewall issue, you can tell for sure by getting ready to place a call, then from a Linux prompt doing:

service iptables stop

As soon as the firewall has dropped, try placing your call, and as soon as you know whether that makes a difference, do:

service iptables start
service fail2ban restart

or maybe better yet, reboot the system if you want to make 100% sure that everything is restarted. Note that turning off your firewall can be very dangerous, so don't leave it off for any longer than is absolutely necessary to determine whether you really do have a firewall issue.


jabber show connections results in:

No such command 'jabber show connections' (type 'core show help jabber show connections' for other possible commands)

stopping iptables did nothing, same problem.
 
aha, jabber show connected (not connections) does produce a result though, and one that might be indicative of my problem.

"User: [email protected]/talk - disconnected"
 
aha, jabber show connected (not connections) does produce a result though, and one that might be indicative of my problem.

"User: [email protected]/talk - disconnected"

In your jabber.conf do you have:
[general]
debug=yes

?

If not set it to that, amportal restart and check your logs. Mine was doing that and was not connecting for some reason. I think it was due to the fact that I was logged into chat on the google email interface.
 
I made sure not to be logged into chat, but im checking that now

nope, not enabled. Enabling and restarting.
 

Members online

No members online now.

Forum statistics

Threads
26,687
Messages
174,410
Members
20,257
Latest member
Dempan
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.
Back
Top