[asterisk-users] MFC/R2 problems
yusuf
yusuf at ecntelecoms.com
Mon Jan 15 07:36:39 MST 2007
Hi,
thanks for the help. It turns out the this device I had, an Orion GSM gateway, does not talk MFC/R2,
but some variant of R2, according to Steve U.
thanks anyways :)
Facundo Ameal wrote:
> These are the different meanings for the diferrent error codes:
> T1 TIMEOUT = 32769
> T2 TIMEOUT = 32770
> T3 TIMEOUT = 32771
> UNEXPECTED MF SIGNAL = 32772
> UNEXPECTED CAS = 32773
> INVALID STATE = 32774
> SET_CAS FAILURE = 32775
> SEIZE ACK TIMEOUT = 32776
> DEVICE IO ERROR = 32777
> T1B TIMEOUT = 32778
>
> I hope it helps.
>
> Greets
>
> On 1/8/07, yusuf <yusuf at ecntelecoms.com> 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.
More information about the asterisk-users
mailing list