Moises Silva wrote:
my mistake.
the line in the unicall.conf should be something like
loglevel=4



Hi Moises,

I search for a error message and found this thread in the list:

http://lists.digium.com/pipermail/asterisk-users/2006-April/148978.html

I'm having the same error here.

Do you have a patch which I can apply?

He is the events which I have when I receive a call:

May 29 13:06:09 WARNING[12503]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/31 <- 0001 [1/ 1/Idle /Idle ] May 29 13:06:09 WARNING[12503]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/31 Detected May 29 13:06:09 WARNING[12503]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/31 Making a new call with CRN 32769 May 29 13:06:09 WARNING[12503]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/31 1101 -> [2/ 2/Idle /Idle ] May 29 13:06:09 WARNING[12503]: chan_unicall.c:2644 handle_uc_event: Unicall/31 event Detected

As I said, the call do not enter in the context I specified in the unicall.conf.

Here is the events I receive when I try to make a call trough the asterisk:

  1.
         -- Setting call duration limit to 600 seconds.
  2.
     May 29 12:37:42 WARNING[12319]: chan_unicall.c:627 unicall_report:
     MFC/R2 UniCall/1 Call control(1)
  3.
     May 29 12:37:42 WARNING[12319]: chan_unicall.c:627 unicall_report:
     MFC/R2 UniCall/1 Make call
  4.
     May 29 12:37:42 WARNING[12319]: chan_unicall.c:627 unicall_report:
     MFC/R2 UniCall/1 Making a new call with CRN 32769
  5.
     May 29 12:37:42 WARNING[12319]: chan_unicall.c:627 unicall_report:
MFC/R2 UniCall/1 0001 -> [1/ 1/Idle /Idle ]
  6.
         -- Called g1/044882120
  7.
     May 29 12:37:42 WARNING[12319]: chan_unicall.c:2644
     handle_uc_event: Unicall/1 event Dialing
  8.
     May 29 12:37:42 WARNING[12319]: chan_unicall.c:627 unicall_report:
MFC/R2 UniCall/1 <- 1101 [1/ 40/Seize /Idle ]
  9.
     May 29 12:37:42 WARNING[12319]: chan_unicall.c:627 unicall_report:
MFC/R2 UniCall/1 0 on -> [2/ 40/Group I /Idle ]
 10.
     May 29 12:37:47 WARNING[12319]: chan_unicall.c:627 unicall_report:
MFC/R2 UniCall/1 R2 prot. err. [2/ 40/Group I /DNIS ] cause 32769 - T1 timed out
 11.
     May 29 12:37:47 WARNING[12319]: chan_unicall.c:627 unicall_report:
MFC/R2 UniCall/1 0 off -> [1/ 1/Idle /Idle ]
 12.
     May 29 12:37:47 WARNING[12319]: chan_unicall.c:627 unicall_report:
MFC/R2 UniCall/1 1001 -> [1/ 1/Idle /Idle ]
 13.
     May 29 12:37:48 WARNING[12319]: chan_unicall.c:2644
     handle_uc_event: Unicall/1 event Protocol failure
 14.
         -- Unicall/1 protocol error. Cause 32769
 15.
     May 29 12:37:48 WARNING[12319]: chan_unicall.c:627 unicall_report:
     MFC/R2 UniCall/1 Channel gains
 16.
     May 29 12:37:48 WARNING[12319]: chan_unicall.c:627 unicall_report:
     MFC/R2 UniCall/1 Channel switching
 17.
         -- Hungup 'UniCall/1-1'
 18.
       == Everyone is busy/congested at this time (1:0/0/1)
 19.
         -- AGI Script agi://192.168.1.59:4573/asterisk/dialup
     completed, returning 0
 20.
       == Auto fallthrough, channel 'IAX2/123456-2' status is
     'CHANUNAVAIL'


Please, not the lines 10 and 13-14.

Thanks in advance.

Fernando Lujan
_______________________________________________
--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

Reply via email to