[asterisk-users] MFC/R2 problems + Orion GSM Gateway

[yusuf]

Hi,

I have made some headway with this.  Let me explain a abit of the setup.  I have an Orion GSM 
Gateway, that was connected to a Cisco AS5300 via E1.  When I looked at the AS5300 config, it was 
talking R2 to the Orion.  So I have tried to connect the Orion direclty to Asterisk (leaving out the 
Cisco), using Unicall.
This is a problem I have with an incoming call, from Orion to Asterisk.

Jan  9 16:35:29 WARNING[7262]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2      <- 0001  [1/ 
       1/Idle          /Idle         ]
Jan  9 16:35:29 WARNING[7262]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 Detected
Jan  9 16:35:29 WARNING[7262]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 Making a new call 
with CRN 32769
Jan  9 16:35:29 WARNING[7262]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 1101  ->      [2/ 
       2/Idle          /Idle         ]
Jan  9 16:35:29 WARNING[7262]: chan_unicall.c:2644 handle_uc_event: Unicall/2 event Detected
Jan  9 16:35:31 WARNING[7262]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2      <- 1001  [2/ 
       2/Seize ack     /Seize ack    ]
Jan  9 16:35:31 WARNING[7262]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 Far end 
disconnected(cause=Normal, unspecified cause [31]) - state 0x2
Jan  9 16:35:31 WARNING[7262]: chan_unicall.c:2644 handle_uc_event: Unicall/2 event Far end disconnected
Jan  9 16:35:31 WARNING[7262]: chan_unicall.c:2930 handle_uc_event: CRN 32769 - far disconnected 
cause=Normal, unspecified cause [31]
Jan  9 16:35:31 WARNING[7262]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 Call control(6)
Jan  9 16:35:31 WARNING[7262]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 Drop 
call(cause=Normal Clearing [16])
Jan  9 16:35:31 WARNING[7262]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 Call 
disconnected(cause=Normal, unspecified cause [31]) - state 0x800
Jan  9 16:35:31 WARNING[7262]: chan_unicall.c:2644 handle_uc_event: Unicall/2 event Drop call
Jan  9 16:35:31 DEBUG[7262]: chan_unicall.c:2978 handle_uc_event: CRN 32769 - Doing a release call
Jan  9 16:35:31 WARNING[7262]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 Call control(7)
Jan  9 16:35:31 WARNING[7262]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 Release call
Jan  9 16:35:31 WARNING[7262]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 1001  ->      [1/ 
    1000/Clear fwd     /Seize ack    ]

The below output(in the mail) is of an outgoing call from Asterisk.

Can anyone please help me to see what is wrong?

yusuf wrote:
> Hi,
> 
> if that means I should post my config, here goes:
> 
> zaptel:
> span=1,1,3,cas,hdb3,crc4
> cas=1-15:1101
> cas=17-31:1101
> 
> unicall.conf:
> protocolvariant=id,10,10
> protocolend=cpe
> group=1
> channel => 1-15
> channel => 17-31
> 
> wanpipe1.conf
> FE_MEDIA        = E1
> FE_LCODE        = HDB3
> FE_FRAME        = CRC4
> FE_LINE         = 1
> TE_CLOCK        = NORMAL
> TE_REF_CLOCK    = 0
> TE_HIGHIMPEDANCE        = NO
> LBO             = 120OH
> TE_SIG_MODE     = CAS
> FE_TXTRISTATE   = NO
> MTU             = 1500
> UDPPORT         = 9000
> TTL             = 255
> IGNORE_FRONT_END = NO
> TDMV_SPAN       = 1
> TDMV_DCHAN      = 16
> 
> [w1g1]
> ACTIVE_CH       = ALL
> TDMV_ECHO_OFF   = NO
> TDMV_HWEC       = NO
> 
> 
> 
> Josué Conti wrote:
> 
>> Hi Yusuf, how are you?
>> It orders in the list its configurations, so that let us can help.
>>
>> Best Regards
>>
>> Josue
>>
>> 2007/1/8, yusuf < yusuf at ecntelecoms.com <mailto:yusuf at ecntelecoms.com>>:
>>
>>     Hi all,
>>
>>     I have Asterisk 1.2.10, zaptel 1.2.7, spandsp-0.0.3pre22 compiled,
>>     and a Sangoma A101, and when I
>>     make a call I get this:
>>
>>
>>     Jan  8 13:04:06 DEBUG[12252]: chan_unicall.c:2000 unicall_exception:
>>     Exception on 19, channel 1
>>     Jan  8 13:04:06 WARNING[12252]: chan_unicall.c:627 unicall_report:
>>     MFC/R2 UniCall/1      <- 1101
>>     [1/      40/Seize /Idle         ]
>>     Jan  8 13:04:06 WARNING[12252]: chan_unicall.c:627 unicall_report:
>>     MFC/R2 UniCall/1 0 on  ->
>>     [2/      40/Group I /Idle         ]
>>     Jan  8 13:04:11 WARNING[12252]: chan_unicall.c:627 unicall_report:
>>     MFC/R2 UniCall/1 R2 prot. err.
>>     [2/      40/Group I /DNIS         ] cause 32769 - T1 timed out
>>     Jan  8 13:04:11 WARNING[12252]: chan_unicall.c:627 unicall_report:
>>     MFC/R2 UniCall/1 0 off ->
>>     [1/       1/Idle /Idle         ]
>>     Jan  8 13:04:11 WARNING[12252]: chan_unicall.c:627 unicall_report:
>>     MFC/R2 UniCall/1 1001  ->
>>     [1/       1/Idle /Idle         ]
>>     Jan  8 13:04:11 WARNING[12252]: chan_unicall.c:2644 handle_uc_event:
>>     Unicall/1 event Protocol failure
>>          -- Unicall/1 protocol error. Cause 32769
>>     Jan  8 13:04:11 WARNING[12252]: chan_unicall.c:627 unicall_report:
>>     MFC/R2 UniCall/1 Channel echo cancel
>>     Jan  8 13:04:11 DEBUG[12252]: chan_unicall.c:955 unicall_disable_ec:
>>     disabled echo cancellation on
>>     channel 1
>>
>>     Jan  8 13:04:11 WARNING[12250]: chan_unicall.c:627 unicall_report:
>>     MFC/R2 UniCall/1      <- 1001
>>     [1/       1/Idle /Idle         ]
>>     Jan  8 13:04:11 WARNING[12250]: chan_unicall.c:627 unicall_report:
>>     MFC/R2 UniCall/1 1001  ->
>>     [1/       1/Idle /Idle         ]
>>          -- Hungup 'UniCall/1-1'
>>
>>
>>     What does "- Unicall/1 protocol error. Cause 32769" mean, and can
>>     anyone help me.
>>
>>     --
> 
> 
> 


-- 
thanks,
Yusuf

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.