News:

On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT

Main Menu

Which ports to open on firewall to let Obi200 work with GV only?

Started by gelcom, July 20, 2015, 11:10:25 AM

Previous topic - Next topic

gelcom

Hi guys, I have an Obi200 placed behind a firewall and connected to an Asterisk server.

I use this device basically to access my GoogleVoice number.

As I don't want the device to exchange information with Obi or any other webservice/company I'm just wondering which ports should I open in my firewall to let it connect only to GoogleVoice and nothing else (including Obitalk)?

kind regards
gelcom


Mango

I don't know the port numbers, but the following settings will do what you want:

System Management >> Auto Provisioning:
Auto Firmware Update >> Method: Disabled
ITSP Provisioning >> Method: Disabled
OBiTalk Provisioning >> Method: Disabled

The following will disable OBiTALK.  If you require the features of OBiTALK, you should skip the next two steps.

Voice Services >> OBiTALK Service:
Enable: (Unchecked)

Physical Interfaces >> PHONE Port:
DigitMap: (add !**5S0| as the first sequence of the DigitMap)

CoalMinerRetired

Interesting question, one that I played around with recently.  

There is a q&a thread on the GV product forums that has some insights, url below. Aince the OBi device emulates a Google chat session the answers in the thread are relevant. I'd disregard that last response with the link to a telnet client, while the test of port 5222 using telnet seems relevant (or one way to teat the port), I would not trust some random person saying "Here, download this telnet client and see what happens..."

https://productforums.google.com/forum/m/#!msg/apps/uk_67mfZy3k/EAE5Cu-FmZgJ

P.S: I never did figure this out to my complete satisfaction, and I'll be curious if you do, if yes can you reply back with what ports were involved?


Taoman

I think this covers all ports used.

Quote80 TCP
443 TCP
19302 – 19309 TCP and UDP

Additional Ports for various clients:

        Ports                  Clients
5222, 5223, 5224     XMPP clients
5228 and 5229         Android phones
5269                       XMPP federation

https://support.google.com/a/answer/1279090?hl=en

SteveInWA

Quote from: Taoman on July 28, 2015, 07:30:17 AM
I think this covers all ports used.

Quote80 TCP
443 TCP
19302 – 19309 TCP and UDP

Additional Ports for various clients:

        Ports                  Clients
5222, 5223, 5224     XMPP clients
5228 and 5229         Android phones
5269                       XMPP federation

https://support.google.com/a/answer/1279090?hl=en

What he said.   ;)

In general, I would ignore anything posted on the GV forum that is more than a couple of years old.  The service has changed considerably since then, and some problems, solutions or issues discussed back then are now out of date, or weren't correct to begin with.

CoalMinerRetired

Do the XMPP ports cited above constitute the all inclusive list, ... is there no signalling/setup/initiation component as in 'SIP is to RTP'?


SteveInWA

XMPP is the signaling protocol, taking the place of SIP.

The media transport (the sound) is over RTP, just as it is with SIP.  That's what the 193xx range covers.  You do need to also have usual HTTP and HTTPS ports 80 and 443 open too.  This is what Taoman linked from the Google page.

https://en.wikipedia.org/wiki/Jingle_(protocol)