Call from MicroSIP to Mizudroid is not working

Asterisk Asterisk SIP
1

I have installed asterisk on my virtual machine (Ubuntu 22.04.5 LTS) and configured for two callers. one is MicroSIP which is installed on my base machine (Lenovo ThinkPad, Windows 10 Pro), and the second one is Mizudroid which is installed on my android mobile (Samsung Galaxy A23 5G). All the devices are on the same network.

Call from Mizudroid to MicroSIP is working and I can see the relevant logs in asterisk, but the call from MicroSIP to Mizudroid is not working (getting Request Timedout error all the time). And I am not seeing any log entry while calling from MicroSIP to Mizudroid.

Here are the version details:
Asterisk: 18.10.0
Mizudroid: 4.0.44
MicroSIP: 3.21.5

Please note that my Windows Defender Firewall is set as OFF now, and when it was ON then I tried add rules for astersik port and port range 10000 to 25000. But no luck.

I have tried to test with changing Transport Protocol too, nothing worked. So, how can I solve this case?

here are the changes which I made related to asterisk config files:
ari.conf : added user entry with type = user, read_only = no, password = **** (created for two users: 7001 & 7002)
sip.conf : created settings like below

[general]
context=public
allowoverlap=no
udpbindaddr=0.0.0.0
tcpenable=no
tcpbindaddr=0.0.0.0
transport=udp
qualify=yes
nat=yes
externip=**.***.***.***  // given proper ip
externaddr=**.***.***.***  // given proper ip
localnet=192.168.178.0/255.255.255.0

[7001] // MicroSIP user
type=friend
host=dynamic
username=7001
secret=7001
context=sample
disallow=all
allow=ulaw,alaw

[7002] // Mizudroid user
type=friend
host=dynamic
username=7002
secret=7002
context=sample
disallow=all
allow=ulaw,alaw

extensions.conf : created settings like below

[sample]
exten => 7001,1,Answer()
exten => 7001,2,Dial(SIP/7001,60)
exten => 7001,3,Playback(vm-nobodyavail)
exten => 7001,4,VoiceMail(7001@main)
exten => 7001,5,Hangup()

exten => 7002,1,Answer()
exten => 7002,2,Dial(SIP/7002,60)
exten => 7002,3,Playback(vm-nobodyavail)
exten => 7002,4,VoiceMail(7002@main)
exten => 7002,5,Hangup()
2

You are using an obsolete and unsupported channel driver.

Does the mobile operator permit the use of SIP?

What steps have you taken to stop Android putting app to sleep?

3

On Thursday 02 January 2025 at 11:08:32, Rajesh via Asterisk Community wrote:

All the devices are on the same network.

I assume this means all devices (including the Android phone) have addresses
in the 192.168.178.0/24 subnet. Please confirm (you can tell us the addresses,
there’s nothing secret about addresses starting with 192.168).

Call from Mizudroid to MicroSIP is working and I can see the relevant logs
in asterisk, but the call from MicroSIP to Mizudroid is not working
(getting Request Timedout error all the time). And I am not seeing any log
entry while calling from MicroSIP to Mizudroid.

I suggest you use something like tshark or sngrep to do a packet capture on
the Asterisk server and see whether there is any network response from the
Samsung IP address when Asterisk tries to place a call to it.

Also, what is the output of “sip show peers”?

Finally, I find this somewhat odd:

exten => 7001,3,Playback(vm-nobodyavail)
exten => 7001,4,VoiceMail(7001@main)

Why do a Playback() before going to voicemail instead of just using the
voicemail greeting?

Antony.

–
I love deadlines. I love the whooshing noise they make as they go by.

  • Douglas Noel Adams

                                                Please reply to the list;
                                                  please *don't* CC me.
4

My android phone doesn’t have a sim, and its connected to the same network through WiFi.

Here are the IP address details:
MicroSIP user (Windows, Laptop) : 192.168.178.102
Mizudroid user (Android Phone) : 192.168.178.74
Asterisk server (Ubuntu22, Virtual machine) : 192.168.178.103

I tried with Playback() too, and the issue still happening.

Another point is, I tried to install another MicroSIP on my another laptop (Windows 10, same network), and tried to make call from one MicroSIP to another MicroSIP but the call is not getting connected. I will summerise the same using user names like below:

MicroSIP user (base machine, Windows laptop) >> 7001
Mizudroid user (Samsung phone, android) >> 7002
MicroSIP user (Windows laptop) >> 7003

call from 7002 to 7001 and 7003 are working fine.
call from 7001 to 7002 and 7003 are not working (Timeout error).
call from 7003 to 7001 and 7002 are not working (Timeout error).

output of “sip show peers”: // now only two users are connected as I have switched off my second laptop (7003)
Name/username Host Dyn Forcerport Comedia ACL Port Status Description
7001/7001 192.168.178.102 D Yes Yes 5060 OK (1 ms) testing purpose
7002/7002 192.168.178.74 D Yes Yes 20524 OK (6 ms) testing purpose

I am using Wireshark to analyze the packets, and I am only seeing one entry related to the VoIP calls as INVITE (attaching the captured image).

sip_call
sip_call979×419 91 KB

5

Please use plain text, not pictures of screens, and please include the whole SIP dialogue, not just a truncated initial INVITE.

Please answer the question about disabling Android power management.

6

If the qualify is working, you should be seeing some response to the INVITE, even if an error one.

The port number in the request (implied 5060) doesn’t match that from the registration (20524).

7

Sorry, I am completely new here.

I didn’t even checked the Android power management side, and I can only see in my phone that Mizudroid is running all the time.

about the registration port with Mizudroid (7002, 192.168.178.74), how can I troubleshoot the same? its by default showing the result like that.

Another test case which I have tried is, installed Linphone on my Windows laptop (base machine, named as 7004), and connected to Asterisk server (192.168.178.103). Then the call from 7004 to 7002 and 7002 to 7004 are working fine. And this time the registration port with Mizudroid (7002, 192.168.178.74) is showing as 11118.

Name/username Host Dyn Forcerport Comedia ACL Port Status Description
7002/7002 192.168.178.74 D Yes Yes 11118 OK (107 ms) testing purpose
7004/7004 192.168.178.102 D Yes Yes 5060 OK (28 ms) testing purpose