[asterisk-users] Indonesian MFC/R2

Steve Underwood steveu at coppice.org
Sun Aug 20 08:52:46 MST 2006


Hi,

There are problems with Indonesian MFC/R2. My software implements one 
version of Indonesian R2 signaling, but there are others. Some are very 
different from normal MFC/R2 signaling, and would require a considerable 
rewrite of he existing software. You need to find out a little more 
about the version of R2 you have.

You can find out a lot more about what is going on by adding 
"loglevel=255" at the beginning of unicall.conf. Then the logs will show 
the fine detail of a call's progress.

Regards,
Steve


Danang Suharno wrote:

> Hi,
>
> I have problem connecting Sangoma A101 with asterisk-1.2.10 supporting 
> MFC/R2 signalling. The incoming calls is received but this messages 
> written in /var/log/asterisk/mesages.localhost.localdomain. (My 
> asterisk-1.2.10 came from latest version of ScopServ 
> http://www.scopserv.com)
>
>
> Aug 19 16:25:39 WARNING[22583] chan_unicall.c: Unicall/13 event Detected
> Aug 19 16:25:45 WARNING[22583] chan_unicall.c: Unicall/13 event Far 
> end disconnected
> Aug 19 16:25:45 WARNING[22583] chan_unicall.c: CRN 32769 - far 
> disconnected cause=Normal, unspecified cause [31]
> Aug 19 16:25:45 WARNING[22583] chan_unicall.c: Unicall/13 event Drop call
> Aug 19 16:25:45 WARNING[22583] chan_unicall.c: Unicall/13 event 
> Release call
>
> and this appears in asterisk console:
> ---------------------------------------
>
> Aug 19 16:25:45 WARNING[12538]: chan_unicall.c:2644 handle_uc_event: 
> Unicall/13 event Detected
> Aug 19 16:25:45 WARNING[12538]: chan_unicall.c:2644 handle_uc_event: 
> Unicall/13 event Protocol failure
>    -- Unicall/13 protocol error. Cause 32771
>
> zaptel.conf is
> ------------------------------------
> loadzone        =  us
> defaultzone     =  us
> span            =  1,0,0,cas,hdb3
> cas             =  1-15:1101
> cas             =  17-31:1101
> dchan         = 16
>
>
> wanpipe1.conf
> ------------------------------------
>
> [devices]
> wanpipe1 = WAN_AFT, Comment
>
> [interfaces]
> w1g1 = wanpipe1, , TDM_VOICE, Comment
>
> [wanpipe1]
> CARD_TYPE        = AFT
> S514CPU          = A
> CommPort         = PRI
> AUTO_PCISLOT     = NO
> PCIBUS           = 2
> PCISLOT          = 2
>
> FE_LINE          = 0
> FE_MEDIA         = E1
> FE_LCODE         = HDB3
> FE_FRAME         = D4
> TE_CLOCK         = NORMAL
> LBO              = 0DB
> TE_SIG_MODE     = CCS
> MTU              = 1500
> UDPPORT          = 9000
> TTL              = 255
> IGNORE_FRONT_END = NO
> TDMV_SPAN        = 1
> TDMV_DCHAN       = 18
>
> [w1g1]
> ACTIVE_CH        = ALL
> TDMV_ECHO_OFF    = NO
> TDMV_HWEC        = NO
>
> unicall.conf
> -----------------------------------------
>
> [channels]
> language             =  en
> context              =  zap-incoming
> protocolclass        =  mfcr2
> protocolvariant      =  id,6,3 -------------> telco said they sent 6 
> digits number and we never dialout so do we still need proper value 
> for DNIS?
> protocolend          =  co --------> Do I have to set to "co"?
> faxdetect            =  no
> relaxdtmf            =  no
> echocancel           =  yes
> echocancelwhenbridged =  no
> echotraining         =  no
> amaflags             =  default
> channel              => 1-15
> channel              => 17-31
>
>
> ==========================
>
> I know this is problem has been solved especially for South American 
> R2 and I've read some old posts that this type of problem has been 
> solved. This one is from Dennis:
> (I sent him emails but no reply as of today)
>
> ================================================================
> R2 protocol error
>
>    * From: Dennis Nacino <starisk11 (at) yahoo.com>
>    * Date: Tue, 4 Apr 2006 17:47:15 -0700 (PDT)
> Hi,
> Thanks a lot, guys! The problem is now fixed by updating the 
> libmfcr2-0.0.3 to pre9 and setting
> the span timing correctly.
> Dennis
>
> ================================================================
>
> The libs version used:
>
> 1. libmfcr2-0.0.3
> 2. spandsp-0.0.2-1005_pre25
> 3. libsupertone-0.0.2
> 4. libunicall-0.0.3pre??? ---> I'm sure which pre version but 
> according to Steve post:
>
> ---------------------
>
> R2 protocol error
>    * From: Steve Underwood <steveu (at) coppice.org>
>    * Date: Mon, 03 Apr 2006 20:07:46 +0800
> Hi Dennis,
>
> Update to libmfcr2-0.0.3 pre9. I made a slip in pre8. Sorry.
>
> Steve
>
> ---------------------
>
> Danang
>
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
>




More information about the asterisk-users mailing list