[asterisk-r2] doubt about how to handle calls with openr2

Mon Apr 12 12:37:16 CDT 2010

ok. please post full log of a single call, meaning both the R2 logs and the
Asterisk debugging logs should be enabled (typically the content of
/var/log/asterisk/full, but that may vary according to logger.conf). I need
the logs for both the trixbox making the call and the one receiving the
call.

Moises Silva
Senior Software Engineer
Sangoma Technologies Inc. | 50 McIntosh Drive, Suite 120, Markham ON L3R 9T3
Canada
t. 1 905 474 1990 x 128 | e. moy at sangoma.com

2010/4/12 Juan Manuel Rafael Suárez <jrafael at telsyssolution.com>

>  Trixbox 2.8  asterisk 1.6 (over centos)
>
> Kernel 2.6.18-128.1.10.el5xen
>
>
>
> Card is an openvox DE115E
>
> Pci exprés echo cancelation.
>
>
>
>
>
> I am working on there in this momento, so any sugestion will be tested…
>
>
>
>
>
> Thanks for your help
>
>
>
> JM
>
>
>
>
>
>
>
>
>
> * *
>
> *Juan Manuel Rafael Suárez** – **Director Comercial*
>
> *www.telsyssolution.com* <http://www.telsyssolution.com>*  |  **
> jrafael at telsyssolution.com** | ** t *(81) 8881-0101 ext 444*| ** c  *044
> 8110801650
>
>
>
>
>
>
>
> [image: cid:image002.jpg at 01C92397.57F83D10]
>
>
>
> *Business Continuity with Intelligent communication***
>
>
>
>
>
> *De:* Moises Silva [mailto:moises.silva at gmail.com]
> *Enviado el:* Lunes, 12 de Abril de 2010 12:27 p.m.
>
> *Para:* asterisk-r2 at lists.digium.com
> *CC:* jrafael at telsyssolution.com
>
> *Asunto:* Re: [asterisk-r2] doubt about how to handle calls with openr2
>
>
>
> Which card and operating system are you using?
>
> Moises Silva
> Senior Software Engineer
> Sangoma Technologies Inc. | 50 McIntosh Drive, Suite 120, Markham ON L3R
> 9T3 Canada
> t. 1 905 474 1990 x 128 | e. moy at sangoma.com
>
>  2010/4/12 Juan Manuel Rafael Suárez <jrafael at telsyssolution.com>
>
> Here we have some logs...
>
>
> First the sending call asterisk
>
> [12:06:15:938] [Thread: 84269968] [Chan 1] - Call started at Mon Apr 12
> 12:06:15 2010 on chan 1 [openr2 version 1.3.0, revision (release)]
> [12:06:15:938] [Thread: 84269968] [Chan 1] - Outgoing call proceeding:
> ANI=100, DNIS=1, Category=National Subscriber
> [12:06:15:938] [Thread: 84269968] [Chan 1] - CAS Tx >> [SEIZE] 0x00
> [12:06:15:938] [Thread: 84269968] [Chan 1] - CAS Raw Tx >> 0x01
> [12:06:15:938] [Thread: 84269968] [Chan 1] - scheduled timer id 2
> (r2_seize)
> [12:06:15:944] [Thread: 84269968] [Chan 1] - Bits changed from 0x08 to 0x0C
> [12:06:15:944] [Thread: 84269968] [Chan 1] - CAS Rx << [SEIZE ACK] 0x0C
> [12:06:15:944] [Thread: 84269968] [Chan 1] - Attempting to cancel timer
> timer 2
> [12:06:15:944] [Thread: 84269968] [Chan 1] - timer id 2 found, cancelling
> it
> now
> [12:06:15:944] [Thread: 84269968] [Chan 1] - MFC/R2 call acknowledge!
> [12:06:15:944] [Thread: 84269968] [Chan 1] - Sending DNIS digit 1
> [12:06:15:944] [Thread: 84269968] [Chan 1] - MF Tx >> 1 [ON]
> [12:06:29:385] [Thread: 84269968] [Chan 1] - Attempting to cancel timer
> timer 0
> [12:06:29:385] [Thread: 84269968] [Chan 1] - Cannot cancel timer 0
> [12:06:29:385] [Thread: 84269968] [Chan 1] - CAS Tx >> [CLEAR FORWARD] 0x08
> [12:06:29:385] [Thread: 84269968] [Chan 1] - CAS Raw Tx >> 0x09
> [12:06:29:402] [Thread: 3996560] [Chan 1] - Bits changed from 0x0C to 0x08
> [12:06:29:402] [Thread: 3996560] [Chan 1] - CAS Rx << [IDLE] 0x08
> [12:06:29:402] [Thread: 3996560] [Chan 1] - Call ended
> [12:06:29:402] [Thread: 3996560] [Chan 1] - Attempting to cancel timer
> timer
> 0
> [12:06:29:402] [Thread: 3996560] [Chan 1] - Cannot cancel timer 0
>
>
>
>
> Then the asterisk that receive the call on mfcR2
>
> [Apr 12 12:06:15] DEBUG[14965] chan_dahdi.c: Chan 1 - Bits changed from
> 0x08
> to 0x00
> [Apr 12 12:06:15] DEBUG[14965] chan_dahdi.c: Chan 1 - CAS Rx << [SEIZE]
> 0x00
> [Apr 12 12:06:15] DEBUG[14965] chan_dahdi.c: Chan 1 - Call started at Mon
> Apr 12 12:06:15 2010 on chan 1 [openr2 version 1.3.0, revision (release)]
> [Apr 12 12:06:15] DEBUG[14965] chan_dahdi.c: Chan 1 - Initialized R2 MF
> detector
> [Apr 12 12:06:15] DEBUG[14965] chan_dahdi.c: Chan 1 - CAS Tx >> [SEIZE ACK]
> 0x0C
> [Apr 12 12:06:15] DEBUG[14965] chan_dahdi.c: Chan 1 - CAS Raw Tx >> 0x0D
> [Apr 12 12:06:15] NOTICE[14965] chan_dahdi.c: New MFC/R2 call detected on
> chan 1.
> [Apr 12 12:06:29] DEBUG[14965] chan_dahdi.c: Chan 1 - Bits changed from
> 0x00
> to 0x08
> [Apr 12 12:06:29] DEBUG[14965] chan_dahdi.c: Chan 1 - CAS Rx << [CLEAR
> FORWARD] 0x08
> [Apr 12 12:06:29] NOTICE[14965] chan_dahdi.c: Chan 1 - Far end
> disconnected.
> Reason: Normal Clearing
> [Apr 12 12:06:29] NOTICE[14965] chan_dahdi.c: MFC/R2 call disconnected on
> chan 1
> [Apr 12 12:06:29] DEBUG[14965] chan_dahdi.c: Chan 1 - Call ended
> [Apr 12 12:06:29] DEBUG[14965] chan_dahdi.c: Chan 1 - CAS Tx >> [IDLE] 0x08
> [Apr 12 12:06:29] DEBUG[14965] chan_dahdi.c: Chan 1 - CAS Raw Tx >> 0x09
> [Apr 12 12:06:29] NOTICE[14965] chan_dahdi.c: MFC/R2 call end on chan 1
>
>
>
> Here we can see the digit 1 is sent and then it stops, no more anction
> until
> hang up call.
>
>
>
>
>
> Juan Manuel Rafael Suárez – Director Comercial
> www.telsyssolution.com  |  jrafael at telsyssolution.com |  t (81) 8881-0101
> ext 444|  c  044 8110801650
>
>
>
>
>
> Business Continuity with Intelligent communication
>
>
> -----Mensaje original-----
> De: asterisk-r2-bounces at lists.digium.com
> [mailto:asterisk-r2-bounces at lists.digium.com] En nombre de
> jrafael at telsyssolution.com
> Enviado el: Lunes, 12 de Abril de 2010 09:40 a.m.
> Para: asterisk-r2 at lists.digium.com
> Asunto: Re: [asterisk-r2] doubt about how to handle calls with openr2
>
> Hellos thanks for reply, actually it is mexico variant.
>
> The other side is another trixbox 2.8 with openr2 installed and running.
>
> When i change sides, i could send call with just one dnig digit.
>
> But not audio.
>
> And i saw answer detected before accepted in logs.
>
> A couple of configuuration changes and i can not complete calls anymore.
>
> any comments?, thanks for the news contact us is not working i ll check it.
>
> Jm
> Enviado desde mi oficina móvil BlackBerry® de Telcel
>
> -----Original Message-----
> From: Moises Silva <moises.silva at gmail.com>
> Date: Mon, 12 Apr 2010 10:11:38
> To: <asterisk-r2 at lists.digium.com>
> Subject: Re: [asterisk-r2] doubt about how to handle calls with openr2
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-r2 mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-r2
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-r2 mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-r2
>
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-r2 mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-r2
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-r2/attachments/20100412/53d1773d/attachment.htm 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 3608 bytes
Desc: not available
Url : http://lists.digium.com/pipermail/asterisk-r2/attachments/20100412/53d1773d/attachment.jpeg 