* You are viewing Posts Tagged ‘app’

Getting channel ‘SIP/192.168.1.69-00000000′ refused to negotiate T.38

Hi,

I recently configured T.38 on Asterisk 10.4.2. When I send the fax to
Asterisk, it gives the errors as listed below;

WARNING[25986]: app_fax.c:442 transmit_audio: channel
‘SIP/192.168.1.69-00000000′ refused to negotiate T.38
WARNING[25986]: app_fax.c:174 span_message: WARNING T.30 ECM carrier not
found

As in sip.conf the configuration is listed below;

t38pt_udptl = yes,fec,maxdatagram=400
faxdetect = t38

And the rest are the standard configuration.

Please advise to resolve this issue.

swift_port_close

Hi,

i am trying to install the just from git cloned app_swift version.
Compiling works fine. Install as well. But if i try to load the module
at Asterisk it fails with.

Command ‘module load app_swift.so ‘ failed.
[Jun 20 11:29:51] WARNING[24217]: loader.c:460 load_dynamic_module:
Error loading module ‘app_swift.so':
/usr/lib/asterisk/modules/app_swift.so: undefined symbol: swift_port_close
[Jun 20 11:29:51] WARNING[24217]: loader.c:850 load_resource: Module
‘app_swift.so’ could not be loaded.

My System Informations:

server*CLI> core show version
Asterisk 1.8.13.0 built by root @ server on a x86_64 running Linux on
2012-06-20 08:55:14 UTC

root@server:~# uname -r
3.2.0-25-generic

root@server:~# ldd /usr/lib/asterisk/modules/app_swift.so
linux-vdso.so.1 => (0x00007fff6d3ff000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f2010a65000)
/lib64/ld-linux-x86-64.so.2 (0x00007f2011041000)

root@server:~# cat /etc/ld.so.conf.d/swift.conf
/opt/swift/lib

root@server:~#ldconfig -v | grep swift
/opt/swift/lib:

libswift.so.6 -> libswift.so.6.0
libceplex_de.so.6 -> libceplex_de.so.6.0
libceplang_de.so.6 -> libceplang_de.so.6.0

root@server:~# swift -V

Cepstral Swift v6.0.1, March 2012

Default Voice: Matthias-8kHz v6.0.0
Language: German v5.1.0
Lexicon: unknown v0.0.0

Concurrency: 1 Port(s) Registered
0 Port(s) In Use

Distribution: No audio distribution license was found.
Saving audio to a file is disabled.

Copyright (C) 2000-20012, Cepstral LLC.

Do You have any Ideas why that won’t work?

Best Regards Jakob Böttger

default iconsmime.p7s

app_swift beta release

Hi folks,

Just a note to let everyone know I’ve finally finished up the new BETA release of app_swift (now v3.0.1 b1).

This release introduces some pretty major changes to app_swift such as:

– The entire code-base has now been unified and the build system auto detects which Asterisk version you’re using (yay! one branch!)

– Auto-detection and support for both the Cepstral 5.0 and 6.0 engines

– Support for Asterisk 1.4, 1.6, 1.8, 1.8 Certified, and 10

– Asterisk 1.2 support has been dropped.

I have only been able to do some basic testing with all these permutations of Asterisk and the Cepstral engines on a few of my machines here at the house and need some volunteers to help out and be guinea-pigs.

Please email me directly with any feedback you might have.

I’ve updated my github repo with the new app_swift code which can be downloaded using git.

git clone git://github.com/dmsessions/app_swift.git

Thanks,

– D

IMAP integration with MS Exchange 2010

Greetings,

Has anybody here successfully integrated IMAP voicemail with Exchange 2010? If so – could you point me in the right direction to configure this properly?

I’m running Asterisk 1.8.11-cert2.

My voicemail.conf:

[general]
format=wav49
imapserver=mail.domain.com
authuser=asterisk_master
authpassword=asterisk_master_password
expungeonhangup=no
pollmailboxes=yes
pollfreq=30
imapgreetings=no
userscontext=customercontext
searchcontexts=yes

(*I have tried adding imapport=993 and imapflags=ssl, but just adds a ‘security problem’ error message to the logfiles).

my voicemail users are in Realtime, and I have a column populated and set for imapuser (you can see in the log errors below that we are successfully getting imapuser from the database and inserting it in the connect string).

Here’s what happens when I try to leave a voicemail message:

[2012-06-04 15:34:48] WARNING[32327]: app_voicemail_imapstorage.c:2849 mm_log: IMAP Warning: Can’t use Kerberos: invalid /authuser
[2012-06-04 15:34:48] WARNING[32327]: app_voicemail_imapstorage.c:2849 mm_log: IMAP Warning: SECURITY PROBLEM: insecure server advertised AUTH=PLAIN
[2012-06-04 15:34:48] WARNING[32327]: app_voicemail_imapstorage.c:2849 mm_log: IMAP Warning: Retrying PLAIN authentication after AUTHENTICATE failed.
[2012-06-04 15:34:48] WARNING[32327]: app_voicemail_imapstorage.c:2849 mm_log: IMAP Warning: SECURITY PROBLEM: insecure server advertised AUTH=PLAIN
[2012-06-04 15:34:49] WARNING[32327]: app_voicemail_imapstorage.c:2849 mm_log: IMAP Warning: Retrying PLAIN authentication after AUTHENTICATE failed.
[2012-06-04 15:34:49] WARNING[32327]: app_voicemail_imapstorage.c:2849 mm_log: IMAP Warning: SECURITY PROBLEM: insecure server advertised AUTH=PLAIN
[2012-06-04 15:34:49] ERROR[32327]: app_voicemail_imapstorage.c:2852 mm_log: IMAP Error: Can not authenticate to IMAP server: AUTHENTICATE failed.
[2012-06-04 15:34:49] WARNING[32327]: app_voicemail_imapstorage.c:2849 mm_log: IMAP Warning: [CLOSED] IMAP connection broken (server response)
[2012-06-04 15:34:49] ERROR[32327]: app_voicemail_imapstorage.c:2598 init_mailstream: Can’t connect to imap server {mail.domain.com:143/imap/authuser=asterisk_master/notls/user=username}INBOX
[2012-06-04 15:34:49] ERROR[32327]: app_voicemail_imapstorage.c:2122 __messagecount: Houston we have a problem – IMAP mailstream is NULL
[2012-06-04 15:34:49] NOTICE[32327]: app_voicemail_imapstorage.c:6159 leave_voicemail: Can not leave voicemail, unable to count messages

Am I just headed down a dead end road?

Regards,

Ric Marques

Messaging capable app_sms

Hi,

has someone done a patch for app_sms so it is capable of sending the SMS
down the messaging-infrastructure in asterisk-10?

Regards,

Jay

No caller id when using cadence with DAHDI

Hello everyone,

Just thought to let you know of a weird issue in Asterisk 1.8.? + Dahdi
2.6.? (and 2.5.?).

When you specify any cadence in an app (Dial, Queue) then caller id does
not work.

For instance with the default cadences (everything commented out in
chan_dahdi.conf) :

Dial(DAHDI/54) caller id works

Dial(DAHDI/54r1) caller id does not work (even for r1)

I just found this issue did not have time to investigate further. Can
anyone else verify that this is true for tonezones other than 13 (gr) which
I am using?

Cheers,

Panos