Sangoma Phone Desktop... losing some hairs

Commercial Modules Sangoma Talk / Software Phone
1

Hello,

Losing my mind on this quirk…

Internal network:
Sangoma Talk - works 100%
Sangoma Phone Desktop - works 100%

External:
Sangoma Talk App - works 100%

Sangoma Phone Desktop - connects, favorites display, make calls receive calls… BUT… no audio both ways when on an external network.

cannot find where i’m going wrong…
Firewall port 6443 tcp opened.
ports 10000 - 20000 UDP opened.

not sure what i missed,

Thanks,
Peter

2

You’ll need to provide some packet capture of an example phone call without any audio before anyone will be able to help.

https://sangomakb.atlassian.net/wiki/spaces/SS/pages/31162494/Providing+Great+Debug

3

Thanks for your assistance.

i setup a 2nd machine to do the debug capture and the primary machine is connected to a nexternal / hotspot network

interesting when i tried a call on from the “internal” network – no errors were noticed, as mentioned – everything is working.

when i flipped to the external network, an error was observed:

in regards to “Error sending STUN request: network is unreachable”, then right below it is attempting to play the “unavail.wav” message

i have specified stun.l.google.com:19302 in teh SIP settings, not sure why this is occuring…
i can ping it from my system - it returns the ip6 address…

thanks,
Peter

4

I resolved the stun issue, but still no audio…

5

as a testing, I installed 3CX and Zopier desktop clients. They both worked with the default app settings, can hear audio both ways, but with the Sangoma Desktop still no audio either way

any suggestions

Tjhanks,
Peter

6

at a total loss still, cannot find the culprit, event though the Desktop works internal and the Phone app works internal and externally…

did a debug trace of acall from desktop (external network) and the mobile app (external network), the only thing I see are the ip addresses – desktop is using an internal ip address, where as the mobile app appears to have a public ip

DESKTOP APP:
Sent RTP packet to 192.168.128.226:50456 (type 00, seq 025621, ts 000160, len 000160)
– <PJSIP/98220-000000ae> Playing ‘/var/spool/asterisk/voicemail/default/246/unavail.slin’ (language ‘en’)
Sent RTP packet to 192.168.128.226:50456 (type 00, seq 025698, ts 012480, len 000160)
Sent RTP packet to 192.168.128.226:50456 (type 00, seq 025699, ts 012640, len 000160)
Sent RTP packet to 192.168.128.226:50456 (type 00, seq 025700, ts 012800, len 000160)
Sent RTP packet to 192.168.128.226:50456 (type 00, seq 025701, ts 012960, len 000160)
Sent RTP packet to 192.168.128.226:50456 (type 00, seq 025702, ts 013120, len 000160)
Sent RTP packet to 192.168.128.226:50456 (type 00, seq 025703, ts 013280, len 000160)
Sent RTP packet to 192.168.128.226:50456 (type 00, seq 025704, ts 013440, len 000160)
Sent RTP packet to 192.168.128.226:50456 (type 00, seq 025705, ts 013600, len 000160)
etc…

MOBILE APP:

[2024-06-21 12:35:53] DEBUG[12091][C-000000d4]: res_rtp_asterisk.c:8368 ast_rtp_read: (0x7f128414b260) RTP NAT: Got audio from other end. Now sending to address 72.139.198.123:13381
Got RTP packet from 72.139.198.123:13381 (type 00, seq 041873, ts 1460241003, len 000160)
Sent RTP packet to 72.139.198.123:13381 (type 00, seq 022872, ts 005280, len 000160)
Sent RTP packet to 72.139.198.123:13381 (type 00, seq 022873, ts 005440, len 000160)
etc

I’m using the mobile hotspot on my work phone which is connected to the laptop simulating the “Extenal network” - the 192.168.128 ip, suspecting the hotspot assigned that ??

not sure if thats the normal pattern for the desktop app…

the 72.139 is a call from my mobile phone – bell network

thanks,
Peter

7

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