FIXED Re: [Asterisk-Dev] zapata.conf priindication option
On December 6, 2004 07:46 am, Andrew Kohlsmith wrote: > I'm still trying to discover how to get IAX2 to see the BUSY now (Dial via > IAX2 and remote has a busy you still get CHANUNAVAIL) but at least the PRI > is working as it should. http://bugs.digium.com/bug_view_page.php?bug_id=0002989 Patch attached to the bug. ___ Asterisk-Dev mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [Asterisk-Dev] zapata.conf priindication option
On December 5, 2004 02:12 pm, Matthew Simpson wrote: > > This was discovered because calling a busy POTS line from a PRI returned > > DIALSTATUS of CHANUNAVAIL instead of BUSY. > hrm... I have the same problem... anyone with some insight? Well what I have done is with priindication=outofband you get HANGUPCAUSE set correctly. DIALSTATUS is still wrong IMO (UNAVAIL instead of BUSY) but if you check HANGUPCAUSE first you will have a good starting point. I'm still trying to discover how to get IAX2 to see the BUSY now (Dial via IAX2 and remote has a busy you still get CHANUNAVAIL) but at least the PRI is working as it should. -A. ___ Asterisk-Dev mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [Asterisk-Dev] zapata.conf priindication option
Can someone please explain what in-band PRI indication is and why it's default is on? I was under the impression that PRI signalling was *always* out of band. This was discovered because calling a busy POTS line from a PRI returned DIALSTATUS of CHANUNAVAIL instead of BUSY. hrm... I have the same problem... anyone with some insight? ___ Asterisk-Dev mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
