Samsung Galaxy Not Registering With 3CX

[thegodplato]

Hi, I have got the software on my Galaxy S but can't seem to get it registered. Model is GT-I9000 on 2.2 Firmware. I have the latest 3CX update ( 1.2.9 ) downloaded too. Tel number for VOIP is through Sipgate. I have followed their instructions but nothing works. Any advice? Getting desperate!!

 

[AlanM]

You understand that the settings that I was referring to are in the 3CX PBX itself, right?

Yes, in the 3CX console. When that box is selected it also asks for the domain name. I do not have a domain setup. This is a home system on a peer-to-peer network. Currently, the default domain name, 3cx.local, is in the field. Since I am not on a domain, should I specify the workgroup name?

 

[Vali_3CX]

Hi
Network workgroup/domain has nothing to do here, forget them.
The SIP Domain is an alias set by the PBX administrator for - mainly - a stronger authentication. You may set any name you want, no relationship with network workgroup/domain.

Now, supposing your PBX is set as having SIP domain alan.m and is running on machine having as internal IP 10.0.0.1, you will have to configure your 3CXPhone account as follows:

Use Internal Server: checked
Internal Server: alan.m
Advanced/Proxy: 10.0.0.1

If 10.0.0.1 machine has network name x1232.company.local, then you may configure your account as

Use Internal Server: checked
Internal Server: alan.m
Advanced/Proxy: x1232.company.local

 

[leejor]

Hi
Network workgroup/domain has nothing to do here, forget them.
The SIP Domain is an alias set by the PBX administrator for - mainly - a stronger authentication. You may set any name you want, no relationship with network workgroup/domain.

Yes, but does 3CX not require the Domain be datafilled (if you are sending calls to it rather than the IP) or it will reject the call?

I use a dynamic DNS service. The domain name is directed to my PBX in my router configuration. My settings in 3CX for that extension does not have the checkbox selected prohibiting using the extension outside the LAN.

Here is the section of my 3CX Server log:
11:37:32.187 [CM502001]: Source info: From: <sip:[email protected]>;tag=oCZAZIVcYJXJE93nBt8pgN9as3fdRB6F<sip:9xxxxxx@mypbx.dynamicdns.com>
11:37:32.187 [CM503013]: Call(11): Incoming call rejected, caller is unknown; msg=SipReq: INVITE [email protected] tid=Pj.Btfx5gtBA-

 

[StefanW]

you can even type in there (3cx MNG - setting - adv) the IP of the host.
For internal calls this field ist just something "optical" to make the sip flow look right.
in external connection this comes a bit more into play. then this SIP Domain should reflext the external domain of the pbx.

so internaly you register against the IP and from extern via dns.
that would work.

 

[AlanM]

I have tried various configurations suggested in the immediate previous posts. I have had some success and still some issues. Here is where I am at right now. I can make calls on my local LAN. I can now make calls via WiFi from outside my local LAN. The limitation I have not been able to overcome is making calls via 3G. The phone registers via 3G but outgoing calls fail. Here is the configuration in my mobile phone:

Use Internal server: checked
Internal server: 3CX.local
External server: <MyDynamicDNSDomainName>
(Advanced) Proxy: <blank>
(Integration) Enable 3G: checked

In my 3CX console, the Allow direct SIP calls is checked and the internal server name listed above is used.

 

[leejor]

It may just be that your provider is preventing the calls from completing. What provider are you using, perhaps others can tell you if it will work, or not to bother putting in any more effort.

 

[AlanM]

My cell provider is AT&T. Off the top of my head, I do not know anyone else with a data plan that utilizes a different provider.

 

[Vali_3CX]

Hi Alan

Alan, I suggest you to try the same test - I mean, the same account configuration - using a different SIP phone, no matter is a 3CXPhone for Windows, Grandstream, Polycom, Aastra and so on. Try and see if is working. In this way, having a reference, we will understand where the issue is.

Regards
vali

 

[AlanM]

Hi Alan

Alan, I suggest you to try the same test - I mean, the same account configuration - using a different SIP phone, no matter is a 3CXPhone for Windows, Grandstream, Polycom, Aastra and so on. Try and see if is working. In this way, having a reference, we will understand where the issue is.

Regards
vali

Vali,

I am now able to configure the phone to successfully register via 3G. I tried a test call and the call completed successfully. The only caveat was that the sound was fair at best, sub-par most of the conversation. Sound quality drastically improves with a WiFi connection with the only complaint received was the called person heard an echo during their conversation.

With that said, it may be an alternative solution when no cell coverage is available and you can hook into a WiFi network. However, over 3G is still very iffy.

Thanks to all for their suggestions and help.

 

[Vali_3CX]

phone successfully register via 3G. I tried a test call and the call completed successfully. The only caveat was that the sound was fair at best, sub-par most of the conversation.

Hi Alan
Alan, when using a 3G connection, please open account's Audio Codecs page, and there move the GSM codec on top (drag it). GSM requires less bandwidth than G.711 and, assuming a 3G internet connection being poorer than a WIFI one, an audio improvement could be expected.
Please tell me the results.
Regards
vali

 

[AlanM]

when using a 3G connection, please open account's Audio Codecs page, and there move the GSM codec on top (drag it). GSM requires less bandwidth than G.711 and, assuming a 3G internet connection being poorer than a WIFI one, an audio improvement could be expected.

Vali,

I tried your suggestion changing the audio codecs when using 3G. The audio quality was notably worse using the GSM codec than the G.711 codec; with that said, both were spotty with the GSM quality at about 50% of the conversation lost and the G.711 at about 25% of the conversation lost.

As expected, with WiFi, the end user reported both codecs were satisfactory with the G.711 producing a clearer conversation.

FYI, I am using AT&T 3G in the south central portion of Pennsylvania, in the city of Altoona, outside of any buildings. Hope this helps.

 

[Vali_3CX]

Hi
Thanks for feedback.

Then let a G.711 most preferred and then you may try another tuning:
open account's Audio Options and there try to increase the Play Buffer value. Try roughly a high value - but expect some extra-delay in incoming audio - to see if there is an improvement.

Regards
vali

 

[AlanM]

try another tuning: open account's Audio Options and there try to increase the Play Buffer value. Try roughly a high value - but expect some extra-delay in incoming audio - to see if there is an improvement.

Vali,

I tried increasing the play buffer value as you suggested to a value of 640 (the next increment up from -1). On WiFi the called party could hear satisfactorily, reporting it sounded like I was in a tin box. When switching to 3G, the called party could hear me talking, starting out garbled but improved as the conversation progressed. However, I did not receive any audio from the called party.
It appears WiFi is adequate, but not what I would call good; 3G is still unusable, at least on AT&T's network.

 

[aesteve]

Hi,

Samsung Galaxy Ace GT-S5830
Android 2.2.1
3CX VoIP Phone for Android 1.2.11


- WiFi works fine.
- 3G Don´t registry.

I follow all instructions I found in forums, but don´t works.
Extension allowed outside the Lan.
Local sip Domain : PBX local IP - Allow calls to external sip URIs

On 3CX VoIP for android.
- 3G activated
- Proxy disabled
- Internal server enabled
- Internal server = PBX local IP
- External Server = Public IP or Fqdn

I don´t know if my provider Movistar allows calls over IP, but its not the problem because the extension should be registred regardless.

Any idea ?

 

[AlanM]

Here is what works for me on the Samsung Galaxy S with AT&T:

On 3CX VoIP for android.
- 3G activated
That is what I have
- Proxy disabled
Set proxy to external IP or external FQDN (without the http://) if using a dynamic DNS provider
- Internal server enabled
That is what I have
- Internal server = PBX local IP
Set to 3CX default, i.e., 3cx.local. This is what I think was a key ingredient I missed. I was using the internal IP address of my 3CX server.
- External Server = Public IP or Fqdn
Set to external IP or external FQDN (without the http://) if using a dynamic DNS provider

If you read through this thread, then you already know my experience with audio quality over 3G. Hope this helps.

 

[aesteve]

Fine, it works now.

Inmy case 3G in the city work fine. Out of the city is other question.

Thank you very very very much.