Comments on: Chan Unicall for Asterisk 1.4.18

By: acriollo

acriollo — Thu, 04 Sep 2008 22:24:36 +0000

Hi Moy ,

Since i moved the asterisk to another box everything is working fine. Just some times i geting this kind of errors :

[Sep 4 17:21:23] NOTICE[4776]: chan_unicall.c:2516 handle_uc_event: Unicall/1 event Dialing
[Sep 4 17:21:23] NOTICE[4776]: chan_unicall.c:1912 unicall_exception: Exception on 17, channel 1
[Sep 4 17:21:40] NOTICE[4776]: chan_unicall.c:2516 handle_uc_event: Unicall/1 event Protocol failure
[Sep 4 17:21:40] ERROR[4776]: chan_unicall.c:2520 handle_uc_event: Unicall/1 protocol error. Cause 32769
[Sep 4 17:21:40] WARNING[4776]: app_dial.c:743 wait_for_answer: Unable to forward voice or dtmf

This is normal situation ? carrier issue or unicall issue ?

Thanks in advance.

By: acriollo

acriollo — Fri, 29 Aug 2008 00:04:55 +0000

Thanks moy , i did reinstall the asterisk in another box with centos 4.1 and seems like everything is working better.

thanks for the code.

Regards

By: moy

moy — Wed, 27 Aug 2008 01:56:54 +0000

You should better try asterisk-users mailing list and provide a better technical description about your issue, codecs involved, if it happens just on IAX/SIP etc etc

By: acriollo

acriollo — Wed, 27 Aug 2008 01:01:40 +0000

Hi Moy.

After some time we decided to upgrade our dell 2950 from asterisk 1.2 to astunicall 1.4.18, everything works well unitl our users begin to complain about cuts on calls.

After making some research we notice that even when the calls are between two local phones the calls sufers cuts after five or six minutes.

I know that is not a unicall specific problem but I just dont know what to do because i do not have this problem before the upgrade.

Any Ideas ? Some else had this problem before ?

Regards.

By: crangeltpmex

crangeltpmex — Mon, 11 Aug 2008 19:25:58 +0000

Hello Moy
My name is Carlos. I had a TE110P configured with Asterisk 1.2 working (E1 from Telmex) for about two years using a patch from zarzamora.com. Now I had to change the server and installed your chan unicall 1.4.18 with Trixbox 2.6.07 which basically comes with Asterisk 1.4.18 and centos 5 in a Dell Optiplex 755. Everything was smooth and didn’t have any problems (except a kernel upgrade to match zaptel). I have the server working with no problems at all. Thanks a lot for this great work. I have also installed a2billing for those insterested…. thanks

By: moy

moy — Wed, 16 Jul 2008 02:30:35 +0000

I think you did not compile and installed the new libunicall included in the package before compiling libmfcr2. Try with that.

By: norman

norman — Wed, 16 Jul 2008 02:02:28 +0000

Hello!
In the past I successfuly compiled and use your “Unicall 0.0.5 & spandsp 0.0.4 with Asterisk 1.4.9″ pack. Now I tried this 1.4.18 version. I compile and install the included zaptel (1.4.9.2) and spandsp (0.0.4) with no problems, but when I try to compile libmfcr2-0.0.3, it bombs out with error:

# make
make all-am
make[1]: Entering directory `/home/teste/asterisk_unicall/astunicall-1.4.18-0.2/unicall-0.0.5pre1/libmfcr2-0.0.3′
if /bin/sh ./libtool –tag=CC –mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I. -I/usr/include/libxml2 -g -O2 -MT mfcr2.lo -MD -MP -MF “.deps/mfcr2.Tpo” -c -o mfcr2.lo mfcr2.c; \
then mv -f “.deps/mfcr2.Tpo” “.deps/mfcr2.Plo”; else rm -f “.deps/mfcr2.Tpo”; exit 1; fi
gcc -DHAVE_CONFIG_H -I. -I. -I. -I/usr/include/libxml2 -g -O2 -MT mfcr2.lo -MD -MP -MF .deps/mfcr2.Tpo -c mfcr2.c -fPIC -DPIC -o .libs/mfcr2.o
mfcr2.c:109: error: syntax error before “delete_context”
mfcr2.c:109: warning: data definition has no type or storage class
mfcr2.c:191: error: initializer element is not constant
mfcr2.c:191: error: (near initialization for `protocol_descriptor.xx_call_control’)
mfcr2.c:192: warning: initialization from incompatible pointer type
mfcr2.c:193: warning: initialization from incompatible pointer type
mfcr2.c:194: warning: initialization from incompatible pointer type
mfcr2.c:195: warning: initialization from incompatible pointer type
mfcr2.c:196: warning: initialization from incompatible pointer type
mfcr2.c:197: warning: initialization from incompatible pointer type
mfcr2.c:198: warning: initialization from incompatible pointer type
mfcr2.c:199: warning: initialization from incompatible pointer type
mfcr2.c:200: warning: initialization from incompatible pointer type
mfcr2.c:201: warning: initialization from incompatible pointer type
mfcr2.c:203: warning: excess elements in struct initializer
mfcr2.c:203: warning: (near initialization for `protocol_descriptor’)
mfcr2.c:4212: error: `delete_context’ redeclared as different kind of symbol
mfcr2.c:109: error: previous declaration of `delete_context’
mfcr2.c:4212: warning: `delete_context’ was declared `extern’ and later `static’
make[1]: *** [mfcr2.lo] Error 1
make[1]: Leaving directory `/home/teste/asterisk_unicall/astunicall-1.4.18-0.2/unicall-0.0.5pre1/libmfcr2-0.0.3′
make: *** [all] Error 2

Any help will be greatly appreciated…

By: moy

moy — Tue, 01 Jul 2008 01:28:23 +0000

I have no experience with Uruguay variant, try ITU, if that does not work let me know and probably we can work together to add Uruguay support.

By: edwin.lam

edwin.lam — Tue, 01 Jul 2008 01:26:14 +0000

thanks Moy. i changed the uc_statet2str to uc_state2str in unicall.h, that seems to work.
now the phone company i connect to uses Uruguay R2 variant. i’ve noticed there’s no Uruguay in mfcr2.c. would that compatible with ITU? if not. is there any pointers on how do i go about customizing it?

By: moy

moy — Fri, 27 Jun 2008 03:29:05 +0000

jsolares: “I would need the full logs to be able to tell” was meant for you.

edwin.Iam: I just discussed this bug in my blog at http://www.moythreads.com/wordpress/2008/05/25/a-tale-of-two-bugs/ , the first bug I mention is the bug you are facing, you can find the answer there. It’s just a typo in a Unicall header that is causing the crash.