Other person can't hear me: try port 19305
dhfobi:
Considering that we don't know all of the ports OBi is or might be using in the future, I think the idea of setting a static ip for the device and prioritizing the device by its mac address in QoS, as the highest priority,which is what QBZappy and I are doing, should prioritze any and all port usage now and into the future, rather than try to keep a vigil on port usage and update port fowarding when new ports are detected.
If this is an incorrect assumption please let me know, anyone, thanks
RonR:
Quote from: dhfobi on March 14, 2012, 06:16:40 pm
Considering that we don't know all of the ports OBi is or might be using in the future, I think the idea of setting a static ip for the device and prioritizing the device by its mac address in QoS, as the highest priority,which is what QBZappy and I are doing, should prioritze any and all port usage now and into the future, rather than try to keep a vigil on port usage and update port fowarding when new ports are detected.
If this is an incorrect assumption please let me know, anyone, thanks
I don't believe that port forwarding and QoS are in any way related. IOW, QoS doesn't open/forward any ports.
dhfobi:
Quote from: RonR on March 14, 2012, 07:09:07 pm
Quote from: dhfobi on March 14, 2012, 06:16:40 pm
Considering that we don't know all of the ports OBi is or might be using in the future, I think the idea of setting a static ip for the device and prioritizing the device by its mac address in QoS, as the highest priority,which is what QBZappy and I are doing, should prioritze any and all port usage now and into the future, rather than try to keep a vigil on port usage and update port fowarding when new ports are detected.
If this is an incorrect assumption please let me know, anyone, thanks
I don't believe that port forwarding and QoS are in any way related. IOW, QoS doesn't open/forward any ports.
OK, if that's the case I'll add the listed ports to port forwarding to my OBi100, may not be necessary but it can't hurt.
Thanks
QBZappy:
dhfobi,
OBi is sending out packets on port 19305. Port forwarding that port to the OBi might be irrelevant, as suggested by the OP, no port forwarding is involved in his solution. However if you read further, Google support site mentions something about Google servers sending packets back to the client to same port. Perhaps making port forwarding relevant after all.
Quote:
"All traffic back to the client from our conference servers will originate from the same port that the client is sending to, and be directed back to the port that the client is sending from."
Looking for info on port 19305 we find references to Google hangout. At first it might seem unrelated to Google voice or GTalk, however it makes references to many of the ports the OP had mentioned.
See: http://support.google.com/a/bin/answer.py?hl=en&answer=1279090
Summary:
The connection methods are attempted in this preferenced order:
1) A UDP connection from the participant to Google on ports 19305 through 19309
2) A TCP connection from the participant to Google on ports 19305 through 19309
3) A TCP connection from the participant to Google on port 80
4) A TCP connection from the participant to Google on port 443 (SSL)
The ideal connection for a user to make to a hangout is through UDP. To allow this connection attempt to succeed you will need to allow connections into your network from UDP ports 19305 through 19309.
All traffic back to the client from our conference servers will originate from the same port that the client is sending to, and be directed back to the port that the client is sending from.
At a minimum, your corporate network must allow access to the Internet on TCP ports 80 and 443 in order for hangouts to work.
Another site analyzed the TCP connections of Google hangout. An interesting observation in his analysis is there are references that Google hangouts uses GTalk with a destination port 19305.
http://www.coolacid.net/20110701219/Latest/google-hangout-details
Since OBi support mentioned an upcoming firmware fix, port forwarding might not be the cause. I think OBihai just discovered a detail in the GTalk protocol.
Robert.Thompson:
This is embarrassing but... :-[
Yesterday, I had the same problem after remotely setting up an OBi 110 from Montreal in Florida: I could call, and hear, Florida but Florida could not hear me. I thought it was a VoIP.ms setting so I chatted back and forth with their support. Couldn't get it to work.
After about an hour of trouble-shooting, I noticed that the microphone on my headset was turned off.
So dlee, is your microphone turned off?
Rob.
Navigation
[0] Message Index
[#] Next page
[*] Previous page