[asterisk-users] Problems with MFCR2 and Meridian

Moises Silva moises.silva at gmail.com
Fri Mar 16 16:36:54 MST 2007


Arturo, the error does not says much really, just that either the
other end timed out expecting a response from you, or your end timed
out expecting a response from the other end :)

However, from my experience, it may be an error in your DNIS/ANI
configuration and/or an mfcr2 library error ( less likely but still
possible ). Anyway, you can lear how to debug this problems with this
little document I wrote:

http://www.moythreads.com/unicall/mfcr2-asterisk-unicall-0.2-english.pdf

Good Look and happy debugging! :)

- Moisés Silva

On 3/16/07, Arturo Ochoa <aochoa at e-electrosystems.com> wrote:
> Hi List,
> I'm trying to connect Asterisk with a Nortel Meridian using an E1 with
> MRFR2 signaling.
> I've connected both cards, and compiled all the required software...
>
> The problem is every call (outgoing or incoming) got dropped,
> complaining about some "T1 timed out"
>
> Only for testing purposes I'm using an application called testcall
> included on the lib-unicall package, and this are the logs:
>
> Chan 1, class 'mfcr2', variant 'mx,0,4', end 335544324, caller 1, from
> '7000' to '6640'
> Loading protocol mfcr2
> Thread for channel 0
> MFC/R2 Chan   1: Call control(8)
> MFC/R2 Chan   1: Unblock
> MFC/R2 Chan   1: 1001  ->      [1/40000000/Idle          /Idle         ]
> MFC/R2 Chan   1: far_unblocking_expired
> MFC/R2 Chan   1: local_unblocking_expired
> Chan   1: -- Far end unblocked! :-)
> Chan   1: -- Far end unblocked! :-)
> Chan   1: -- Local end unblocked! :-)
> Chan   1: -- Local end unblocked! :-)
> Chan   1: Initiating call
> MFC/R2 Chan   1: Call control(1)
> MFC/R2 Chan   1: Make call
> MFC/R2 Chan   1: Making a new call with CRN 32769
> MFC/R2 Chan   1: 0001  ->      [1/       1/Idle          /Idle         ]
> Chan   1: -- Dialing on channel 0
> Chan   1: -- Dialing on channel 0
> MFC/R2 Chan   1:      <- 1101  [1/      40/Seize         /Idle         ]
> MFC/R2 Chan   1: 6 on  ->      [2/      40/Group I       /Idle         ]
> Main thread
> MFC/R2 Chan   1: R2 prot. err. [2/      40/Group I       /DNIS         ]
> cause 32769 - T1 timed out
> MFC/R2 Chan   1: 6 off ->      [1/       1/Idle          /Idle         ]
> MFC/R2 Chan   1: 1001  ->      [1/       1/Idle          /Idle         ]
> Chan   1: -- Protocol failure on channel 0, cause (32769) T1 timed out
> Chan   1: -- Protocol failure on channel 0, cause (32769) T1 timed out
> MFC/R2 Chan   1:      <- 1001  [1/       1/Idle          /Idle         ]
> MFC/R2 Chan   1: 1001  ->      [1/       1/Idle          /Idle         ]
>
> Have anyone know something about this??
>
>
> --
> Ing. Arturo Ochoa N
> Network Administrator
> Electrosystems,
>
> _______________________________________________
> --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
>


-- 
"Su nombre es GNU/Linux, no solamente Linux, mas info en http://www.gnu.org"


More information about the asterisk-users mailing list