Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

kiax2b1 bug?

Help
2008-06-05
2013-04-25
  • It seems there is a bug in kiax2b1. Here the scenario:

    Caller-side: kiax2 (tested both windows and linux box)
    Answer-side: kiax2 (tested both windows and linux box)
    both registered with an asterisk server.

    Sometimes it happens that the kiax2 answer side is killed after a call.
    I haven't been able to tell the condition(s) to reproduce such behaviour but often I have to lauch again kiax2 program.

    Any hints?

    Thanks
    Valerio

     
    • Emo
      Emo
      2008-06-05

      Thanks, Valerio.

      Does Kiax crash after answer has been killed?
      Can you try with Kiax from one side and other softphone (using iaxclient) on the other?
      After answer killed, does the problem persist?

      Thanks for the reports.

      Emil

       
      • It does not seem that kiax crashes here a strace when it has been killed:

        Receiver-side:
        [mixvoipcore] -INFO- Incoming call. Call number 0
        [mixvoipcore] -INFO- Ringing. Call number 0
        [mixvoipcore] -INFO- Active call changed. New active number 0
        [mixvoipcore] -INFO- Call complete (established). Call number 0
        [mixvoipcore] -INFO- Registration for account 192.168.0.9 accepted.
        [mixvoipcore] -INFO- Call became inactive. Call number 0
        [mixvoipcore] -INFO- Module AccountsModuleImpl disposed.
        [mixvoipcore] -INFO- Module CDRModuleImpl disposed.
        [mixvoipcore] -INFO- Module ConfigurationModuleImpl disposed.
        [mixvoipcore] -INFO- Module ContactsModuleImpl disposed.
        [mixvoipcore] -INFO- Module SignalingModuleIAX2 disposed.
        [mixvoipcore] -INFO- Service Storage stopped successfully.
        [mixvoipcore] -INFO- Service Naming stopped successfully.
        [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 6088
        --- SIGCHLD (Child exited) @ 0 (0) ---
        read(10, "", 8192)                      = 0
        exit_group(0)                           = ?
        Process 6083 detached

        AFAIK it seems an ordinary exit, but I did not close kiax2!

        Here the log of the caller-side (which must hangup to probably force receiver exit from program)
        [mixvoipcore] -INFO- Outgoing call active. Call number 0
        [mixvoipcore] -INFO- Ringing. Call number 0
        [mixvoipcore] -INFO- Active call changed. New active number 0
        [mixvoipcore] -INFO- Call complete (established). Call number 0
        [mixvoipcore] -INFO- Call became inactive. Call number 0
        [mixvoipcore] -INFO- Registration for account 192.168.0.9 accepted.
        [mixvoipcore] -INFO- Registration for account 192.168.0.9 accepted.
        WARNING: peercallno does not match callno, peercallno => 5077, callno => 8837, dcallno => 7656[mixvoipcore] -INFO- Outgoing call active. Call number 0
        [mixvoipcore] -INFO- Ringing. Call number 0
        WARNING: peercallno does not match callno, peercallno => 5077, callno => 8837, dcallno => 7656WARNING: peercallno does not match callno, peercallno => 5077, callno => 8837, dcallno => 7656WARNING: peercallno does not match callno, peercallno => 5077, callno => 8837, dcallno => 7656WARNING: peercallno does not match callno, peercallno => 5077, callno => 8837, dcallno => 7656[mixvoipcore] -INFO- Active call changed. New active number 0
        [mixvoipcore] -INFO- Call complete (established). Call number 0
        WARNING: peercallno does not match callno, peercallno => 5077, callno => 8837, dcallno => 7656WARNING: peercallno does not match callno, peercallno => 5077, callno => 8837, dcallno => 7656WARNING: peercallno does not match callno, peercallno => 5077, callno => 8837, dcallno => 7656WARNING: peercallno does not match callno, peercallno => 5077, callno => 8837, dcallno => 7656WARNING: peercallno does not match callno, peercallno => 5077, callno => 8837, dcallno => 7656WARNING: peercallno does not match callno, peercallno => 5077, callno => 8837, dcallno => 7656WARNING: peercallno does not match callno, peercallno => 5077, callno => 8837, dcallno => 7656[mixvoipcore] -INFO- Call became inactive. Call number 0

        ...I cannot even image what WARNING can mean.

        If the receiver-side hangups the call, there is no exit from kiax2.

        Kiax2 receiver side can exit even if the caller is iaxComm (1.1.0 final tested) and iaxComm hangups the call.

        Happy to help you.
        Valerio

         
        • Emo
          Emo
          2008-06-09

          Huh.. this really looks like an ordinary exit in the first log. Very strange really! I will investigate tht, thank you!

          The second log is what iaxclient tells us, and it tells it is something wrong within the iax routines. Which version of asterisk do you use?

          Thanks again,
          Emil

           
          • here my asterisk 'show version':
            Asterisk 1.2.29 built by root @ localhost on a i686 running Linux on 2008-06-06 09:44:21 UTC

            Valerio

             
        • Emo
          Emo
          2008-06-10

          OK, fixed the app kill on incoming call in the SVN. The fix will be visible in the next build.

          THANKS

          Emil