thr3ads.net - asterisk users - [Asterisk-Users] R2 implementation problem [Jan 2006]

If this information is useful, please help other people find it:
Share via:

Manuel Marin Garcia

2006-Jan-31 12:23 UTC

[Asterisk-Users] R2 implementation problem

I have a TE110P connected to a Telmex E1 circuit with R2 signaling.

Asterisk version= 1.0.10
Zaptel= 1.0.1
Spandsp=0.0.3pre6
Unicall= 0.0.3pre8

*zaptel.conf
span=1,1,0,cas,hdb3
cas=1-15:1101
cas=17-31:1101
dchan=16
loadzone = us
defaultzone=us

*unicall.conf
immediate=no
loglevel=255
protocolclass=mfcr2
protocolvariant=mx,10,4
protocolend=cpe
group = 1
context = telmex
channel => 1-15
channel => 17-31
*
*chan_unicall is compiled without any problems and when asterisk starts 
I see all channels in idle state. The problem is that I am unable to 
make or receive calls. When there is an incoming call I see the following

Incoming Call (I receive 10 ANI digits and 4 DNIS digits) I suppose to 
receive 0875 for DNIS

Jan 31 10:08:48 WARNING[4293]: chan_unicall.c:704 unicall_report: MFC/R2 
UniCall/25      <- 0001  [1/       1/Idle          /Idle         ]
Jan 31 10:08:48 WARNING[4293]: chan_unicall.c:704 unicall_report: MFC/R2 
UniCall/25 Detected
Jan 31 10:08:48 WARNING[4293]: chan_unicall.c:704 unicall_report: MFC/R2 
UniCall/25 Making a new call with CRN 32769
Jan 31 10:08:48 WARNING[4293]: chan_unicall.c:704 unicall_report: MFC/R2 
UniCall/25 1101  ->      [2/       2/Idle          /Idle         ]
Jan 31 10:08:48 WARNING[4293]: chan_unicall.c:2865 handle_uc_event: 
Unicall/25 event Detected
Jan 31 10:08:48 WARNING[4293]: chan_unicall.c:704 unicall_report: MFC/R2 
UniCall/25      <- 0 on  [2/       2/Seize ack     /Seize ack    ]
Jan 31 10:08:48 WARNING[4293]: chan_unicall.c:704 unicall_report: MFC/R2 
UniCall/25 1 on  ->      [2/       2/Seize ack     /Seize ack    ]

There is a 9 or 10 seconds pause and the I receive the following 
message. There is a busy tone in the caller side after the message

Jan 31 10:10:34 WARNING[4311]: chan_unicall.c:704 unicall_report: MFC/R2 
UniCall/27      <- 1001  [2/       2/Group A       /DNIS request ]
Jan 31 10:10:34 WARNING[4311]: chan_unicall.c:704 unicall_report: MFC/R2 
UniCall/27 Far end disconnected(cause=Normal, unspecified cause [31]) - 
state 0x2
Jan 31 10:10:34 WARNING[4311]: chan_unicall.c:704 unicall_report: MFC/R2 
UniCall/27      <- 0 off [2/     800/Clear fwd     /DNIS request ]
Jan 31 10:10:34 WARNING[4311]: chan_unicall.c:704 unicall_report: MFC/R2 
UniCall/27 1 off ->      [2/     800/Clear fwd     /DNIS request ]
Jan 31 10:10:34 WARNING[4311]: chan_unicall.c:704 unicall_report: MFC/R2 
UniCall/27 R2 prot. err. [2/     800/Clear fwd     /DNIS request ] cause 
32774 - Invalid state
Jan 31 10:10:34 WARNING[4311]: chan_unicall.c:704 unicall_report: MFC/R2 
UniCall/27 1001  ->      [1/       1/Idle          /Idle         ]
Jan 31 10:10:34 WARNING[4311]: chan_unicall.c:2865 handle_uc_event: 
Unicall/27 event Far end disconnected
Jan 31 10:10:34 WARNING[4311]: chan_unicall.c:3198 handle_uc_event: CRN 
32769 - far disconnected cause=Normal, unspecified cause [31]
Jan 31 10:10:34 WARNING[4311]: chan_unicall.c:704 unicall_report: MFC/R2 
UniCall/27 Call control(6)
Jan 31 10:10:34 WARNING[4311]: chan_unicall.c:704 unicall_report: MFC/R2 
UniCall/27 Drop call(cause=Normal Clearing [16])
Jan 31 10:10:34 WARNING[4311]: chan_unicall.c:704 unicall_report: MFC/R2 
UniCall/27 1101  ->      [1/       1/Idle          /Idle         ]
Jan 31 10:10:34 WARNING[4311]: chan_unicall.c:2865 handle_uc_event: 
Unicall/27 event Protocol failure
   -- Unicall/27 protocol error. Cause 32774
Jan 31 10:10:34 WARNING[4311]: chan_unicall.c:704 unicall_report: MFC/R2 
UniCall/28      <- 0001  [1/       1/Idle          /Idle         ]
Jan 31 10:10:34 WARNING[4311]: chan_unicall.c:704 unicall_report: MFC/R2 
UniCall/28 Detected
Jan 31 10:10:34 WARNING[4311]: chan_unicall.c:704 unicall_report: MFC/R2 
UniCall/28 Making a new call with CRN 32769
Jan 31 10:10:34 WARNING[4311]: chan_unicall.c:704 unicall_report: MFC/R2 
UniCall/28 1101  ->      [2/       2/Idle          /Idle         ]
Jan 31 10:10:34 WARNING[4311]: chan_unicall.c:2865 handle_uc_event: 
Unicall/28 event Detected
Jan 31 10:10:34 WARNING[4311]: chan_unicall.c:704 unicall_report: MFC/R2 
UniCall/28      <- 0 on  [2/       2/Seize ack     /Seize ack    ]
Jan 31 10:10:34 WARNING[4311]: chan_unicall.c:704 unicall_report: MFC/R2 
UniCall/28 1 on  ->      [2/       2/Seize ack     /Seize ack    ]
Jan 31 10:10:35 WARNING[4311]: chan_unicall.c:704 unicall_report: MFC/R2 
UniCall/28      <- 0 off [2/       2/Group A       /DNIS request ]
Jan 31 10:10:35 WARNING[4311]: chan_unicall.c:704 unicall_report: MFC/R2 
UniCall/28 1 off ->      [2/       2/Group A       /DNIS request ]
Jan 31 10:10:35 WARNING[4311]: chan_unicall.c:704 unicall_report: MFC/R2 
UniCall/28      <- 8 on  [2/       2/Group A       /DNIS request ]
Jan 31 10:10:35 WARNING[4311]: chan_unicall.c:704 unicall_report: MFC/R2 
UniCall/28 1 on  ->      [2/       2/Group A       /DNIS request ]

*NOTE*:
I Already tried changing values for DNIS and ANIS and same problem
I tried with other versions of spandsp and unicall and same problem
The same occurs in Asterisk version 1.2.3

Does someone has experience configuring R2 in TE110P boards?


Any ideas or suggestions will be appreciated


Thanks

Alberto Sagredo

2006-Jan-31 13:49 UTC

head link

[Asterisk-Users] R2 implementation problem

I hope this link will help you.

http://zarzamora.com.mx/asterisk/17

Regards


Manuel Marin Garcia escribi?:> I have a TE110P connected to a Telmex E1 circuit with R2 signaling.
>
> Asterisk version= 1.0.10
> Zaptel= 1.0.1
> Spandsp=0.0.3pre6
> Unicall= 0.0.3pre8
>
> *zaptel.conf
> span=1,1,0,cas,hdb3
> cas=1-15:1101
> cas=17-31:1101
> dchan=16
> loadzone = us
> defaultzone=us
>
> *unicall.conf
> immediate=no
> loglevel=255
> protocolclass=mfcr2
> protocolvariant=mx,10,4
> protocolend=cpe
> group = 1
> context = telmex
> channel => 1-15
> channel => 17-31
> *
> *chan_unicall is compiled without any problems and when asterisk 
> starts I see all channels in idle state. The problem is that I am 
> unable to make or receive calls. When there is an incoming call I see 
> the following
>
> Incoming Call (I receive 10 ANI digits and 4 DNIS digits) I suppose to 
> receive 0875 for DNIS
>
> Jan 31 10:08:48 WARNING[4293]: chan_unicall.c:704 unicall_report: 
> MFC/R2 UniCall/25      <- 0001  [1/       1/Idle          /Idle        
]
> Jan 31 10:08:48 WARNING[4293]: chan_unicall.c:704 unicall_report: 
> MFC/R2 UniCall/25 Detected
> Jan 31 10:08:48 WARNING[4293]: chan_unicall.c:704 unicall_report: 
> MFC/R2 UniCall/25 Making a new call with CRN 32769
> Jan 31 10:08:48 WARNING[4293]: chan_unicall.c:704 unicall_report: 
> MFC/R2 UniCall/25 1101  ->      [2/       2/Idle          /Idle        
]
> Jan 31 10:08:48 WARNING[4293]: chan_unicall.c:2865 handle_uc_event: 
> Unicall/25 event Detected
> Jan 31 10:08:48 WARNING[4293]: chan_unicall.c:704 unicall_report: 
> MFC/R2 UniCall/25      <- 0 on  [2/       2/Seize ack     /Seize ack   
]
> Jan 31 10:08:48 WARNING[4293]: chan_unicall.c:704 unicall_report: 
> MFC/R2 UniCall/25 1 on  ->      [2/       2/Seize ack     /Seize ack   
]
>
> There is a 9 or 10 seconds pause and the I receive the following 
> message. There is a busy tone in the caller side after the message
>
> Jan 31 10:10:34 WARNING[4311]: chan_unicall.c:704 unicall_report: 
> MFC/R2 UniCall/27      <- 1001  [2/       2/Group A       /DNIS request
]
> Jan 31 10:10:34 WARNING[4311]: chan_unicall.c:704 unicall_report: 
> MFC/R2 UniCall/27 Far end disconnected(cause=Normal, unspecified cause 
> [31]) - state 0x2
> Jan 31 10:10:34 WARNING[4311]: chan_unicall.c:704 unicall_report: 
> MFC/R2 UniCall/27      <- 0 off [2/     800/Clear fwd     /DNIS request
]
> Jan 31 10:10:34 WARNING[4311]: chan_unicall.c:704 unicall_report: 
> MFC/R2 UniCall/27 1 off ->      [2/     800/Clear fwd     /DNIS request
]
> Jan 31 10:10:34 WARNING[4311]: chan_unicall.c:704 unicall_report: 
> MFC/R2 UniCall/27 R2 prot. err. [2/     800/Clear fwd     /DNIS 
> request ] cause 32774 - Invalid state
> Jan 31 10:10:34 WARNING[4311]: chan_unicall.c:704 unicall_report: 
> MFC/R2 UniCall/27 1001  ->      [1/       1/Idle          /Idle        
]
> Jan 31 10:10:34 WARNING[4311]: chan_unicall.c:2865 handle_uc_event: 
> Unicall/27 event Far end disconnected
> Jan 31 10:10:34 WARNING[4311]: chan_unicall.c:3198 handle_uc_event: 
> CRN 32769 - far disconnected cause=Normal, unspecified cause [31]
> Jan 31 10:10:34 WARNING[4311]: chan_unicall.c:704 unicall_report: 
> MFC/R2 UniCall/27 Call control(6)
> Jan 31 10:10:34 WARNING[4311]: chan_unicall.c:704 unicall_report: 
> MFC/R2 UniCall/27 Drop call(cause=Normal Clearing [16])
> Jan 31 10:10:34 WARNING[4311]: chan_unicall.c:704 unicall_report: 
> MFC/R2 UniCall/27 1101  ->      [1/       1/Idle          /Idle        
]
> Jan 31 10:10:34 WARNING[4311]: chan_unicall.c:2865 handle_uc_event: 
> Unicall/27 event Protocol failure
>   -- Unicall/27 protocol error. Cause 32774
> Jan 31 10:10:34 WARNING[4311]: chan_unicall.c:704 unicall_report: 
> MFC/R2 UniCall/28      <- 0001  [1/       1/Idle          /Idle        
]
> Jan 31 10:10:34 WARNING[4311]: chan_unicall.c:704 unicall_report: 
> MFC/R2 UniCall/28 Detected
> Jan 31 10:10:34 WARNING[4311]: chan_unicall.c:704 unicall_report: 
> MFC/R2 UniCall/28 Making a new call with CRN 32769
> Jan 31 10:10:34 WARNING[4311]: chan_unicall.c:704 unicall_report: 
> MFC/R2 UniCall/28 1101  ->      [2/       2/Idle          /Idle        
]
> Jan 31 10:10:34 WARNING[4311]: chan_unicall.c:2865 handle_uc_event: 
> Unicall/28 event Detected
> Jan 31 10:10:34 WARNING[4311]: chan_unicall.c:704 unicall_report: 
> MFC/R2 UniCall/28      <- 0 on  [2/       2/Seize ack     /Seize ack   
]
> Jan 31 10:10:34 WARNING[4311]: chan_unicall.c:704 unicall_report: 
> MFC/R2 UniCall/28 1 on  ->      [2/       2/Seize ack     /Seize ack   
]
> Jan 31 10:10:35 WARNING[4311]: chan_unicall.c:704 unicall_report: 
> MFC/R2 UniCall/28      <- 0 off [2/       2/Group A       /DNIS request
]
> Jan 31 10:10:35 WARNING[4311]: chan_unicall.c:704 unicall_report: 
> MFC/R2 UniCall/28 1 off ->      [2/       2/Group A       /DNIS request
]
> Jan 31 10:10:35 WARNING[4311]: chan_unicall.c:704 unicall_report: 
> MFC/R2 UniCall/28      <- 8 on  [2/       2/Group A       /DNIS request
]
> Jan 31 10:10:35 WARNING[4311]: chan_unicall.c:704 unicall_report: 
> MFC/R2 UniCall/28 1 on  ->      [2/       2/Group A       /DNIS request
]
>
> *NOTE*:
> I Already tried changing values for DNIS and ANIS and same problem
> I tried with other versions of spandsp and unicall and same problem
> The same occurs in Asterisk version 1.2.3
>
> Does someone has experience configuring R2 in TE110P boards?
>
>
> Any ideas or suggestions will be appreciated
>
>
> Thanks
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> --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
>

asterisk users - Jan 2006 - R2 implementation problem

[Asterisk-Users] R2 implementation problem

[Asterisk-Users] R2 implementation problem