mISDN drops calls after change Elastix 1.0->1.3

Discussion in 'General' started by kontogou, Nov 2, 2008.

  1. kontogou

    Joined:
    Nov 2, 2008
    Messages:
    4
    Likes Received:
    0
    Hi all,
    I 've made a clean installation of Elastix 1.3 keeping the configuration from 1.0.
    It seems that mISDN 1.1.7 (asterisk 1.4.22-rc5) blocks BRI port when incoming call occurs while outgoing call is on progress.

    I have this issue 2-3 times per day, all incoming calls on the specific port are rejected permanently and I have to do : "restart" or "misdn restart port 1" in asterisk console to unblock port.

    The same configuration worked absolutely fine for 5 months without restart in Elastix 1.0 (with mISDN 1.1.6 and asterisk 1.4.18).

    Other users have also reported this issue : http://bugs.digium.com/view.php?id=13488&nbn=15

    This is from misdn.log:

    Code:
    Mon Oct 27 00:00:06 2008: P[ 0] -- mISDN Channel Driver Registered --
    Mon Oct 27 10:34:35 2008: P[ 2] GOT IGNORE SETUP
    Mon Oct 27 10:34:35 2008: P[ 2] CC_RELEASE_COMPLETE|CONFIRM [TE]
    Mon Oct 27 10:36:45 2008: P[ 2] GOT IGNORE SETUP
    Mon Oct 27 10:36:45 2008: P[ 2] CC_RELEASE_COMPLETE|CONFIRM [TE]
    Mon Oct 27 10:45:19 2008: P[ 2] **** Received CAUSE:44, so not cleaning up channel 1
    Mon Oct 27 10:45:19 2008: P[ 2] **** This channel is now no longer available,
    please try to restart it with 'misdn send restart <port> <channel>'
    Mon Oct 27 10:45:19 2008: P[ 2] Sending Restarts on this port.
    Mon Oct 27 10:45:19 2008: P[ 2] Restarting and cleaning channel 1
    Mon Oct 27 10:45:19 2008: P[ 2] Restarting channel 1
    Mon Oct 27 11:02:43 2008: P[ 2] Requested Channel Already in Use releasing this call with cause 34!!!!
    Mon Oct 27 11:02:43 2008: P[ 2] couldn't handle event
    Mon Oct 27 11:02:43 2008: P[ 2] CC_RELEASE_COMPLETE|CONFIRM [TE]
    Mon Oct 27 11:04:12 2008: P[ 2] Requested Channel Already in Use releasing this call with cause 34!!!!
    Mon Oct 27 11:04:12 2008: P[ 2] couldn't handle event
     
  2. kontogou

    Joined:
    Nov 2, 2008
    Messages:
    4
    Likes Received:
    0
    Changed back to mISDN 1.1.6 (elastix 1.0) from 1.1.7 (elastix 1.3) and problem is eliminated.

    mISDN now restarts the port and does not throw "Requested Channel Already in Use releasing this call with cause 34!!!!" message. Incoming calls are not blocked.

    Code:
    Thu Nov 20 20:55:52 2008: P[ 2] CC_RELEASE_COMPLETE|CONFIRM [TE]
    Fri Nov 21 12:17:49 2008: P[ 2] **** Received CAUSE:44, so not cleaning up channel 1
    Fri Nov 21 12:17:49 2008: P[ 2] **** This channel is now no longer available,
    please try to restart it with 'misdn send restart <port> <channel>'
    Fri Nov 21 12:17:49 2008: P[ 2] Sending Restarts on this port.
    Fri Nov 21 12:17:49 2008: P[ 2] Restarting and cleaning channel 1
    Fri Nov 21 12:17:49 2008: P[ 2] Restarting channel 1
    Fri Nov 21 12:19:58 2008: P[ 2] Any Channel Requested, but we have no more!!
    Fri Nov 21 12:19:58 2008: P[ 2] couldn't handle event
    Fri Nov 21 12:19:58 2008: P[ 2] CC_RELEASE_COMPLETE|CONFIRM [TE]
     
  3. eyasterisk

    Joined:
    Apr 3, 2007
    Messages:
    6
    Likes Received:
    0
    Which version of zaptel you are using..Are you using asterisk and zaptel version buit in with Elastix 1.0.1 or recompiled to newer version? Am also facing same issue now with Elastix 0.7.3
     
  4. kontogou

    Joined:
    Nov 2, 2008
    Messages:
    4
    Likes Received:
    0
    Did you update elastix to newer version of asterisk ? That may be the reason you encounter blocked ports.
    I'm using the default asterisk and misdn versions of Elastix 1.0.1.
    The problem is probably related to chan_misdn version which is included in asterisk versions > 1.4.17

    Please install elastix 1.0.1 or older and do not do any yum update or any update via the web interface so that you have asterisk 1.4.17 or older installed. You should not encounter blocked ports with this version.

    Please post here any succesful installation.
     
  5. Usuarioforum

    Joined:
    Nov 15, 2007
    Messages:
    93
    Likes Received:
    0
    The same here:

    1.4.22-rc5
    mISDN-1.1.7.2-1

    Is solved in near versions?
     
  6. kontogou

    Joined:
    Nov 2, 2008
    Messages:
    4
    Likes Received:
    0
    The bug is closed and a patch has been released.
    But I think it is not included in version 1.4.22.:)
     

Share This Page