Fernando Lujan wrote:
Steve Underwood wrote:
The problem is almost solved. The card was configured as a T1 interface, the selled came and jumped it.
Now I have the following problem. When I call from my legacy pbx, appear a event:
*CLI> May 26 12:04:09 WARNING[5215]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/31 <- 0001 [1/ 1/Idle /Idle ] May 26 12:04:09 WARNING[5215]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/31 Detected May 26 12:04:09 WARNING[5215]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/31 Making a new call with CRN 32769 May 26 12:04:09 WARNING[5215]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/31 1101 -> [2/ 2/Idle /Idle ] May 26 12:04:09 WARNING[5215]: chan_unicall.c:2644 handle_uc_event: Unicall/31 event Detected May 26 12:04:54 WARNING[5215]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/31 <- 1001 [2/ 2/Seize ack /Seize ack ]
But this event, doesn't enter in the context which I configure in the unicall.conf file. Do I need to change something else?
Thanks again. 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
