Home/ Questions/Q 9140765
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-17T09:33:32+00:00

I am facing a strange problem when using the standard Android SIP Demo in

  • 0

I am facing a strange problem when using the standard Android SIP Demo in combination with an asterisk 1.8.9.2 server: incoming / outgoing calls are working correctly, but there is one thing not working: when I launch a call from the SIP demo and I close the call again (hitting the “End current call” button), the call is terminated in the SIP demo, but the called device still keeps ringing.

I have tried to check what’s happening by logging the telegrams via Wireshark and it seems that the CANCEL telegram from the SIP demo to the asterisk server is not accepted, take a look:

300 08:30:39.483913 130.10.0.102    192.168.0.110   SIP/SDP 916 Request: INVITE sip:110@192.168.0.110:5060, with session description
301 08:30:39.488686 192.168.0.110   130.10.0.102    SIP 525 Status: 100 Trying
302 08:30:39.524884 192.168.0.110   130.10.0.102    SIP 541 Status: 180 Ringing
309 08:30:41.041071 130.10.0.102    192.168.0.110   SIP 370 Request: CANCEL sip:110@192.168.0.110:5060
310 08:30:41.051545 192.168.0.110   130.10.0.102    SIP 526 Status: 481 Call/Transaction Does Not Exist

And now the real strange thing: If I repeat the same action, and before terminating the call through the “End current call” button I wait for ca. 7 seconds, the CANCEL is accepted and the call is terminated correctly:

646 08:31:05.571464 130.10.0.102    192.168.0.110   SIP/SDP 916 Request: INVITE sip:110@192.168.0.110:5060, with session description
647 08:31:05.576150 192.168.0.110   130.10.0.102    SIP 525 Status: 100 Trying
648 08:31:05.662345 192.168.0.110   130.10.0.102    SIP 541 Status: 180 Ringing
664 08:31:08.302561 130.10.0.102    192.168.0.110   SIP 389 Request: OPTIONS sip:192.168.0.110
665 08:31:08.312097 192.168.0.110   130.10.0.102    SIP 528 Status: 404 Not Found
698 08:31:13.370346 130.10.0.102    192.168.0.110   SIP 370 Request: CANCEL sip:110@192.168.0.110:5060
699 08:31:13.373570 192.168.0.110   130.10.0.102    SIP 513 Status: 487 Request Terminated
700 08:31:13.373912 192.168.0.110   130.10.0.102    SIP 497 Status: 200 OK

I have checked the contents of both CANCEL requests, and the structure is completely the same!
Furthermore I have also tested a server with asterisk 1.6 and there I did NOT encounter this problem, the call is terminated correctly there!
So it makes me believe that it has to do something with asterisk vers. 1.8.

Did anyone encounter similar problems and has some helpful hints for me? If further data is needed for analysis, just let me know!
Thanks for your help,
BR

Armin

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I was facing exactly same problem with Asterisk 1.8.11.0 and Android 2.3/4.0.3.
    There is a simple solution for this problem under the ‘general’ section of sip.conf file
    add following attribute with value equals to no.

    [general]
.
.
pedantic=no

    I hope it will also work for you…..

    • 0