LESSONS LEARNED: In GV, the check box must be set so that calls are forward to ‘google chat’. If you can not see XMPP traffic in asterisk (CLI>jabber set debug on), then this is the first thing to check. Thank goodness for others that have walked the path before me and share their experience.
If there is no XMPP traffic when you call your GV #, You can also verify that your jabber connections are active via CLI:
athomehost*CLI> jabber show connections
Jabber Users and their status:
[mylogin1] mylogin1@gmail.com/Talk - Connected
[mylogin2] mylogin2@gmail.com/Talk - Connected
Google Voice (Jabber\XMPP) Asterisk 1.8.4 is setup on an Optware Asus RT-N16. System details (sip.conf and dial plan) can be found by clicking here. I am able to make calls out and view the traffic from the CLI. This is done by issuing the command from the * CLI:
[code]root@athomehost:~# asterisk -vr
Here is a Jabber traffic sample when a GV call is placed through Asterisk (email address \ phone # redacted):
[quote]athomehost*CLI> jabber set debug on
Jabber Debugging Enabled.
JABBER: myEmailAddr OUTGOING:
JABBER: myEmailAddr INCOMING: xmpp:15555551212@voice.google.com/srvres-MTAuMTMuMTcyLjU6OTg4Nw==<ses:redirect xmlns:ses=“http://www.google.com/session”>
JABBER: myEmailAddr INCOMING: xmpp:15555551212@voice.google.com/srvres-MTAuMTMuMTcyLjU6OTg4Nw==</ses:redirect>
JABBER: myEmailAddr OUTGOING:
JABBER: myEmailAddr OUTGOING: <candidate name=‘rtp’ address=‘98.82.141.242’ port=‘13180’ username=‘696c440175278525’ secret='XXXXXXXXXXXXXpreference=‘1.00’ protocol=‘udp’ type=‘local’ network=‘0’ generation=‘0’/>
JABBER: myEmailAddr INCOMING:
JABBER: myEmailAddr INCOMING:
JABBER: myEmailAddr INCOMING: <ses:session type=“candidates” id=“2337b31a1713b921” initiator="myEmailAddr@gmail.com/Talk1ED71C4C" xmlns:ses=“http://www.google.com/session”><ses:candidate name=“rtp” address=“74.125.45.126” port=“19295” username=“rnfJJdBA2XpWv3R8” preference=“1.0” protocol=“udp” network=“mediaproxy” generation=“0” ="" type=“relay”/><ses:candidate name=“rtp” address=“74.125.45.126” port=“19294” username=“rnfJJdBA2XpWv3R8” preference=“0.6” protocol=“tcp” network=“mediaproxy” generation=“0” ="" type=“relay”/><ses:candidate name=“rtp” address=“74.125.45.126” port=“443” username=“rnfJJdBA2XpWv3R8” preference=“0.5” protocol=“ssltcp” network=“mediaproxy” generation=“0” ="" type=“relay”/></ses:session>
JABBER: myEmailAddr OUTGOING:
JABBER: myEmailAddr OUTGOING:
JABBER: myEmailAddr INCOMING: [/quote]
Incoming presence XMPP traffic also shows up:
[code]JABBER: myIdentity INCOMING: 24<caps:c node=“http://www.android.com/gtalk/client/caps” ext=“pmuc-v1” ver=“1.1” xmlns:caps=“http://jabber.org/protocol/caps”/>awayShort week…upcoming beach weekend for Marissa’s pre-bachelorette party! !d53fb354807c177187591cd381b05f17c85999ab
JABBER: myIdentity INCOMING: 24<caps:c node=“http://www.android.com/gtalk/client/caps” ext=“pmuc-v1” ver=“1.1” xmlns:caps=“http://jabber.org/protocol/caps”/>awayShort week…upcoming beach weekend for Marissa’s pre-bachelorette party! !0d90142e4744030225ad9600309b1461f8f8ffb2
athomehost*CLI> jabber set debug on
Jabber Debugging Enabled.[/code]
Calls made to the GV# show no Jabber traffic. I would think that when my GV# is called that XMPP\Jabber traffic would be visible.
- Is this a correct assumption?
- If true, what can be done to determine root cause of not receiving Jabber traffic (unable to receive GV calls)?
- Can I conclude that the configuration between my ATA and * is complete \ correct based on the fact that I make outgoing GV calls?
Any actionable guidance is appreciated. Thank you.