VOIP Tech Chat → Re: [PBX] Google Voice One Way Audio

First of all, regardless what others have said, I am no FS expert here, ATM. However, I will try my best to succinctly explain (in one or two sentences) some very basic understanding how FS works. Unlike any other B2BUA, FS differentiates between internal and external devices connected to it. I may be wrong, but my understanding of an internal device is both FS and its internal device should reside within the same subnet. From your explanation above, you have configured your ATA as an internal device while it does not reside under the same subnet where the FS is. As such, FS may have some problem to forward incoming audio streams from your ATA to the other endpoint to cause a 1-way audio.

I have never done such a configuration like the one you want. However, I believe there are several ways to resolve this issue, AFAICT. Probably, you can use the ACL approach to let FS know your ATA subnet. Or, create a new SIP proxy account for your ATA to register as an endpoint (extension). Personally, my preference is the later. I don't know if the former may cause some security issue.

P.S: Under the External section of Getting Started Guide for FS, please peruse the NOTE if you decide to create a new SIP proxy account for your ATA to register.

Thank you very much for the help. I will give that a try tomorrow.

So I did try to setup the HT701 at my home as an external device, but I could not get FS to register to the HT701. I did port forward both ports 5060 and 5080 on the NetGear router to the HT701.

Here are the messages I was seeing in the FS log.

2014-10-25 13:45:27.492161 [ERR] sofia_reg.c:2314 home Registration Failed with status Method Not Allowed [405]. failure #2
2014-10-25 13:45:28.432145 [WARNING] sofia_reg.c:504 home Failed Registration [405], setting retry to 60 seconds.
2014-10-25 13:46:29.432136 [NOTICE] sofia_reg.c:447 Registering home
2014-10-25 13:46:29.532119 [ERR] sofia_reg.c:2314 home Registration Failed with status Method Not Allowed [405]. failure #3
2014-10-25 13:46:30.432134 [WARNING] sofia_reg.c:504 home Failed Registration [405], setting retry to 90 seconds.
2014-10-25 13:47:38.652111 [NOTICE] sofia_glue.c:1811 deleted gateway home from profile external
2014-10-25 13:47:42.506177 [NOTICE] sofia_reg.c:3276 Added gateway 'home' to profile 'external'
2014-10-25 13:47:42.512815 [NOTICE] sofia_reg.c:447 Registering home
2014-10-25 13:48:14.572123 [ERR] sofia_reg.c:2314 home Registration Failed with status Request Timeout [408]. failure #1
2014-10-25 13:48:15.512145 [WARNING] sofia_reg.c:504 home Failed Registration [408], setting retry to 30 seconds.
2014-10-25 13:48:46.512159 [NOTICE] sofia_reg.c:447 Registering home
2014-10-25 13:49:18.532118 [ERR] sofia_reg.c:2314 home Registration Failed with status Request Timeout [408]. failure #2
2014-10-25 13:49:19.512120 [WARNING] sofia_reg.c:504 home Failed Registration [408], setting retry to 60 seconds.
2014-10-25 13:49:32.732121 [NOTICE] sofia_glue.c:1811 deleted gateway home from profile external
 

I am not sure if I understand what you said. I think what you will need is as follows:

1. Login to your FS VPS.

2. Go to its [FS configuration XML directory]/sip_profiles/external directory to create a new SIP profile for your ATA to register.

3. Then, login to your ATA and configure it to register to your FS using the above newly created SIP profile credentials.

When you do the above #2, your FS becomes your SIP ISP and you can register your ATA to your FS using the SIP credentials you just create. I haven't done this before.

I don't know if the following will help you or not.

At the beginning of this year, dicodread shipped me some partially broken OBi-1X0 devices. Some of these OBi-1X0 devices had problems with their FXS ports, i.e. no dial tone, no rings on an incoming call, etc., when a phone is plugged in, nevertheless they still functioned (registered) with GV. So, with some helps from a friend, we managed to configure my FS to use the partially broken OBi-1X0 devices as a GV Gateway to place an outbound call through GV. This way, the OBi-1X0 devices could still be used. To do this, we had to create a SIP profile along with an outbound dialplan for each OBi-1X0 device. The SIP profile we created doesn't require the device to register to FS. I have included here the SIP profile and default dialplan (for outbound). Perhaps, you can make use of them.

1. SIP profile for an OBi-100 (/etc/freeswitch/sip_profiles/external/OBi-100.xml). I don't know if setting the "register' value to true will work for you. You can change the gateway name and/or the value of any parameter names as you wish.

<include>
  <gateway name="OBi100">
    <param name="proxy" value="10.0.0.10:5061"/>
    <param name="username" value="1000"/>
    <param name="password" value="$${default_password}"/>
    <param name="register" value="false"/>
    <param name="retry-seconds" value="30"/>
    <param name="context" value="public"/>
  </gateway>
</include>
 

2. Dialplan for an OBi-100 (/etc/freeswitch/dialplan/default/OBi100.xml). If you change the gateway name in your SIP profile, make sure you change the gateway used in here, too. The following dialplan allows users to place an outbound call by dialing 10 or 11 digits as well as prefix the called number (10 or 11 digits) with 0100.

<include>
  <extension name="OBi100_Out">
    <condition field="destination_number" expression="^(|0100)1?(\d{10})$">
      <action application="bridge" data="sofia/gateway/OBi100/1$2" />
    </condition>
  </extension>
</include>
 

If you make it to work, I am sure readers here will appreciate your efforts to post your FS XML configuration files here. Good luck.

There is just one part I don't understand. Should FS be trying to login to the HT701 or should the HT701 be trying to login to FS?

From the looks of the error message I am seeing, it seems that FS is trying to login to the HT701.

Your FS should be the SIP server for your ATA device. Hence, you should configure your ATA device to register to your FS server.

Okay, I tried some additional things based on your recommendations and I think that I am making some progress.

Now I am getting the following messages:

You must define a domain called 'xx.xx.xx.xx' in your directory and add a user with the id="2002" attribute
and you must configure your device to use the proper domain in it's authentication credentials.
You must define a domain called 'xx.xx.xx.xx' in your directory and add a user with the id="2002" attribute
and you must configure your device to use the proper domain in it's authentication credentials.
 

Where xx.xx.xx.xx is the IP address of the VPS that FS is running on. Did you have to define a user in the /etc/freeswitch/directory tree?

In the XML which you posted

<param name="proxy" value="10.0.0.10:5061"/>
 

Is 10.0.0.10 the IP address of FS or of the Obi?

It is my OBi100 IP Address. What I am not sure is if that line is required because of the other line ("register" set to false).

BTW, I would strongly recommend that you head to FS IRC channel (#freeswitch) and/or post your questions to FS mailing list to ask experts there to help you. They definitely know a whole lot more than me and/or any FS users here, AFAICT.