The number you have dialled is not in service. GS Wave Android Client

FreePBX
1

Hi guys - I’m unable to make any calls either to external numbers or FreePBX itself using the Android Grandstream Wave client. The client registers with FreePBX fine.

When calling any number I receive ‘the number you have dialled is not in service’

If I use the same extension on a desktop client (MicroSIP) I can place calls without issue.

/var/log/asterisk/full shows this at the time of placing the call.

[2019-03-22 16:35:39] WARNING[23328][C-00000045] Ext. s: “Rejecting unknown SIP connection from 192.168.5.181”

Weirdly the IP address logged is the IP of the PBX server and not the mobile phone.

I’m using voipfone UK as my trunk. These are the settings provided by the SIP provider for FreePBX which I have.

host=sip.voipfone.net
username=someusername
secret=somesecret
qualify=yes
nat=yes
insecure=very
type=peer
fromuser=someuser
dtmfmode=rfc2833
disallow=all
allow=alaw
context=from-pstn
authuser=someuser

I also have ‘Allow SIP Guests’

It seems to be an issue with the GS Wave client - does anyone know what might be causing this?

Many thanks

2

Are you registering to the PBX internally or Publicly?

Also, can you post a full call log?

https://wiki.freepbx.org/display/SUP/Providing+Great+Debug#ProvidingGreatDebug-AsteriskLogs-PartII

3

Thanks for the reply Pitzkey - The softphone is registering internally.

I’ve just tried the same extension on my mobile using the Linphone client and I can place calls successfully. Unfortunately Linphone is prone to crashes and is generally less stable than the GS Wave client.

Here’s the full asterisk log when using the GS Wwave client.

[2019-03-24 13:13:33] NOTICE[1245] chan_sip.c: Peer ‘1001’ is now Lagged. (3693ms / 2000ms)
[2019-03-24 13:13:43] NOTICE[1245] chan_sip.c: Peer ‘1001’ is now Reachable. (396ms / 2000ms)
[2019-03-24 13:14:45] NOTICE[1245] chan_sip.c: Peer ‘1001’ is now Lagged. (2098ms / 2000ms)
[2019-03-24 13:14:59] NOTICE[1245] chan_sip.c: Peer ‘1001’ is now UNREACHABLE! Last qualify: 2098
[2019-03-24 13:15:34] NOTICE[1245] chan_sip.c: Peer ‘1001’ is now Reachable. (129ms / 2000ms)
[2019-03-24 13:17:39] NOTICE[1245] chan_sip.c: Peer ‘1001’ is now Lagged. (2976ms / 2000ms)
[2019-03-24 13:17:49] NOTICE[1245] chan_sip.c: Peer ‘1001’ is now Reachable. (40ms / 2000ms)
[2019-03-24 13:21:56] NOTICE[1245] chan_sip.c: Peer ‘1001’ is now Lagged. (2975ms / 2000ms)
[2019-03-24 13:22:08] NOTICE[1245] chan_sip.c: Peer ‘1001’ is now Reachable. (1972ms / 2000ms)
[2019-03-24 13:25:39] NOTICE[1245] chan_sip.c: Peer ‘1001’ is now UNREACHABLE! Last qualify: 3
[2019-03-24 13:26:29] NOTICE[1245] chan_sip.c: Peer ‘1001’ is now Reachable. (576ms / 2000ms)
[2019-03-24 13:26:35] WARNING[26535][C-00000076] Ext. s: “Rejecting unknown SIP connection from 192.168.5.181”

Not sure why the latency is reporting as ridiculously high - pinging from the Android phone to the PBX over a minute results in around 20ms average latency. Pinging from the PBX to the Android phone shows spikes of 2000ms. Odd.

Pinging iOS devices shows much lower latency 10-20ms range.

Many thanks

4

Sorry about the delayed response.

Is your PBX on the 192.168.5.x network?

No this is not a full call log, please follow instructions from the link.

5

The problem is now resolved. Turns out there was a bug in the Unofficial LineageOS 16 build I was running which caused an issue with the way SIP packets were written. I’ve performed a clean install of LineageOS 16 Official and I can now place and receive calls.

1 Like
6

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.