FOOD FOR THOUGHT New SIP client for Android

[David Foxworth]

When specifying the port to connect TO, you put it after the dns name or IP address using a colon, such as 1.2.3.4:5160

Yes, however, with their app, you can't. It gives you an error and says improper characters. The app doesn't like the :5160. So perhaps that is something they can add such that you can specify a different port number.

However, I did a tcpdump to see what port it was trying to connect with and then temporarily reset the port on my FreePBX box to match, and the phone connects and makes calls.

 

[ankyr]

I could not make the app work for me in attempting to connect to my Asterisk server. So I did a tcpdump to see what was going on. Apparently it is ignoring the port setting under Network Preferences and therefore it is attempting to contact my Asterisk server on a different port than what I have specified in the settings. Is this something I am doing wrong or is it truly ignoring that setting?

Thanks

Thanks for trying out our app.
You should use Account Settings, not Network Settings. In the domain field type 1.2.3.4 (your PBX address without port), then set "Outbound Proxy" to "Specify Address" and "Proxy Server Address" to 1.2.3.4:your_port_number. As for Network Settings, they are used to specify the listening port.

 

[ostridge]

new VoIP app, Sipnetic

Hi just been trying out. set up extension 705 on lan to ipbx. dialed a test call to [email protected] which requires to leave voice message and press the "#" key hash or pound key depending which side of the pond) and the recording gets played back. Problem the dial pad has no hash (pound) key; it's morphed into the "+" key.
As asterisk/freepbx tends to use the ## In-Call Asterisk Blind Transfer feature code and other typical press # when done voice prompts by default; I should in your position reinstate the # key; and for the + its normally bundled under the 0 (zero) key.

edit: Please note also that the dialpad needs to be available when in a call so that feature codes, such as transfers or recordings can be processed by the pbx.

Oops I don't want to sound negative, the look and feel is good, though I had to search to find my way back in to edit account. Hidden beneath the tiny dropdown arrow is the Manage Accounts menu; so that had me fooled for a while.

My limited sound quality test was fine I think that was probably alaw codec .

 

[ankyr]

Hi just been trying out. set up extension 705 on lan to ipbx. dialed a test call to [email protected] which requires to leave voice message and press the "#" key hash or pound key depending which side of the pond) and the recording gets played back. Problem the dial pad has no hash (pound) key; it's morphed into the "+" key.
As asterisk/freepbx tends to use the ## In-Call Asterisk Blind Transfer feature code and other typical press # when done voice prompts by default; I should in your position reinstate the # key; and for the + its normally bundled under the 0 (zero) key.

Thanks for your feedback. The missing # key was a serious flaw on our part. We'll be fixing it ASAP.

My limited sound quality test was fine I think that was probably alaw codec .

During the call you can press the button with lock icon to see codec and other call information.

 

[ostridge]

# key was a serious flaw on our part. We'll be fixing it ASAP

Thanks for the reply - note my edit above.

 

[ankyr]

edit: Please note also that the dialpad needs to be available when in a call so that feature codes, such as transfers or recordings can be processed by the pbx.

Thanks for the reply - note my edit above.

Thanks. We'll add dialpad to the in-call screen in the next release.

 

[ankyr]

We've updated the app. Now in-call screen has a button to show the DialPad. And it does have the # key.

 

[ostridge]

updated the app. Now in-call screen has a button to show the DialPad. And it does have the # key

Yes the app update came up on the phone and now updated thanks

 

[mattburris]

Is there any way you can add an option to integrate the call log with the native android call log?

I use SIP for incoming calls, but I still use the native android dialer to make outgoing calls. Having (an option to display) the incoming/missed numbers that called via SIP show up in the native android call log makes it very easy to return those calls via the normal dialer.

Thanks!

 

[ankyr]

Is there any way you can add an option to integrate the call log with the native android call log?

I use SIP for incoming calls, but I still use the native android dialer to make outgoing calls. Having (an option to display) the incoming/missed numbers that called via SIP show up in the native android call log makes it very easy to return those calls via the normal dialer.

Thanks!

Currently Sipnetic doesn't use the Android's native Call Log, but we consider adding this feature. It'll take some time though.
What we can do quickly is to add an option to make a normal phone call from Sipnetic's Log. I think it might be useful in your case.

 

[ankyr]

Currently Sipnetic doesn't use the Android's native Call Log, but we consider adding this feature. It'll take some time though.
What we can do quickly is to add an option to make a normal phone call from Sipnetic's Log. I think it might be useful in your case.

We have released a new version which allows calling normal phone from Sipnetic’s call history. Just long tap on the item and choose “Call via cell network”.

 

[Hometech]

Hi,
Does this client support message waiting indication. For voicemail?

 

[ankyr]

Not yet. We consider adding this feature in the next releases.

 

[ankyr]

Does this client support message waiting indication. For voicemail?

We now have the Message Waiting Indication in Sipnetic. It works well with Asterisk and other PBXs supporting RFC 3842.

 

[Hometech]

Yea! all we need now is IAX2 support

 

[wardmundy]

@ankyr: Any plans for the iPhone and iOS platform?? Looks great on Android!

 

[ankyr]

Thanks, wardmundy. We have put most of the effort into Android version, but we also consider other platforms, such as Windows and iOS. But these are rather long-term plans.

 

[phinphan]

In the latest Google play update, all sounds go through the speaker. I am using it on note 9 with Android 9. Sipnetic 1.0.14. Is there anyway to stop that? Route it back to normal phone handset?

 

[ankyr]

In the latest Google play update, all sounds go through the speaker. I am using it on note 9 with Android 9. Sipnetic 1.0.14. Is there anyway to stop that? Route it back to normal phone handset?

Thanks for reporting this. We'll need more details to resolve the issue, please contact us at [email protected]

 

[phinphan]

Whatever the problem was, it went away when I tested just now after rebooting my phone. Now the speaker icon is present and the sound is routed appropriately. It may have been related to updating yesterday or this morning from the previous version. Reboot seems to have fixed it.

by the way, it is a very handy client. Every other sip client takes forever to register and this one does it almost instantly.