* You are viewing the archive for August 16th, 2012

Grandstream VoIP Phones

Who else on the list is using them, particularly in a hosted environment?
We’ve just decided to transition to them as our primary recommendation instead of the Cisco SPA series. We did it because of the value and feature set, like having an inexpensive phone with a small BLF, which a lot of customers asked for. I’m wondering if others have tips they’ve learned along the way, or any advice they want to offer. Also anyone using the advanced features like the browser for anything useful?

For those who haven’t tried them, or who like us, didn’t like their older models, take another look. We have been surprised at the value they give us. The prices are low, but the functionality and quality are high. They aren’t Polycom 600s to be sure, but they are nice phones that have a huge set of features for a great price. Customers are liking them a lot.

Has anyone used the new DECT phone? We currently use the Panasonic DECT
phones but they are a nightmare to configure.

If anyone wants to get in touch with them, our Grandstream contact is Dennis Ryan, dryan@grandstream.com .

TDM Fax

Has anyone experimented with increasing the DAHDI chunk size in improve fax reliability? If so, did it help, hurt, or not make any difference?

Requiring Agent To Confirm Queue Calls Only When Forwarded To External Device

I’d like to allow my users to forward their calls using the forwarding feature on their SIP handsets and continue to receive Queue() calls. Currently I set the ‘i’ option in Queue() so that if a user forwards to their cell phone, or any other extension that has voicemail, the voicemail doesn’t eat all the calls to the queue.

I’m aware that I can configure the queue to require agents to acknowledge the call. However, most of the calls go to internal devices where confirmation isn’t necessary, so I’d like to avoid the extra inconvenience in that most common case.

What I’d like to do is somehow detect that a handset has responded with a SIP 302 response, and only when this is the case, require the agent to confirm humanness before answering the call from the queue. Any ideas on how this could be implemented?

Fax Detect On Demand

Using Asterisk 1.8.mumble. We would like to use fax detect on demand.

Both chan_dahdi and chan_sip support setting fax detetect on a static basis, but no way I’ve been able to find to enable/disable it on demand in the dialplan.

In 1.4 we used the NVFaxDetect 3rd party app, but that no longer appears to be maintained.

Does anyone have any suggestions?

Still Having CDR Problems.

Hi all,

I’m ironing out some remaining issues from a 1.6.x to 10.2.x upgrade.

I’ve been able to recover the ability to get CDR’s in my Mysql database, but I
had to unload cdr_adaptive_odbc.so and revert back to cdr_odbc.so to get it to work… partially.

I really need to use adaptive cdr’s because I’m trying to store jitter statistics and such.

If I unload cdr_odbc and load cdr_adaptive_odbc.so, I no longer get new cdr’s.

My cdr_odbc.conf contains:
================================================[global]
dsn => diehlnet username => user password => password pre-connect => yes loguniqueid=yes dispositionstring=yes
================================================
The diehlnet dsn refers to an ODBC datasource, so here is my
/etc/unixODBC/odbc.ini:

================================================[diehlnet]
Description = MySQL test database Trace = Off TraceFile = stderr Driver = MySQL
SERVER = EXAMPLE.com USER = USER
PASSWORD = PASSWORD
PORT = 3306
DATABASE = DATABASE
================================================
When I try to load cdr_adaptive_odbc.so, I get this on the console: (trimmed)

================================================CLI> module load cdr_adaptive_odbc.so Loaded cdr_adaptive_odbc.so
[Aug 15 20:16:10] == Parsing ‘/etc/asterisk/cdr_adaptive_odbc.conf': [Aug 15
20:16:10] == Found
[Aug 15 20:16:10] — Found adaptive CDR table cdr@diehlnet.
[Aug 15 20:16:10] > Found calldate column with type -10 with len
16777215, octetlen 16777215, and numlen (0,0)
[Aug 15 20:16:10] > Found duration column with type -5 with len 19, octetlen 19, and numlen (0,10)
[Aug 15 20:16:10] > Found billsec column with type -5 with len 19, octetlen 19, and numlen (0,10)
[Aug 15 20:16:10] > Found disposition column with type -9 with len 45, octetlen 135, and numlen (0,0)
[Aug 15 20:16:10] > Found amaflags column with type -5 with len 19, octetlen 19, and numlen (0,10)
[Aug 15 20:16:10] > Found accountcode column with type -9 with len 20, octetlen 60, and numlen (0,0)
[Aug 15 20:16:10] > Found uniqueid column with type -9 with len 32, octetlen 96, and numlen (0,0)
[Aug 15 20:16:10] > Found userfield column with type -9 with len 255, octetlen 765, and numlen (0,0)
[Aug 15 20:16:10] > Found clid column with type -9 with len 80, octetlen 240, and numlen (0,0)
[Aug 15 20:16:10] > Found src column with type -9 with len 80, octetlen
240, and numlen (0,0)
[Aug 15 20:16:10] > Found dst column with type -9 with len 80, octetlen
240, and numlen (0,0)
[Aug 15 20:16:10] > Found dcontext column with type -9 with len 80, octetlen 240, and numlen (0,0)
[Aug 15 20:16:10] > Found channel column with type -9 with len 80, octetlen 240, and numlen (0,0)
[Aug 15 20:16:10] > Found dstchannel column with type -9 with len 80, octetlen 240, and numlen (0,0)
[Aug 15 20:16:10] > Found lastapp column with type -9 with len 80, octetlen 240, and numlen (0,0)
[Aug 15 20:16:10] > Found lastdata column with type -9 with len 80, octetlen 240, and numlen (0,0)
[Aug 15 20:16:10] > Found id column with type 4 with len 10, octetlen
10, and numlen (0,10)
[Aug 15 20:16:10] > Found recvip column with type -9 with len 16, octetlen 48, and numlen (0,0)
[Aug 15 20:16:10] > Found peerip column with type -9 with len 16, octetlen 48, and numlen (0,0)

[Aug 15 20:16:10] Loaded cdr_adaptive_odbc.so => (Adaptive ODBC CDR backend)
================================================
When I complete a call, I get this on the console:
================================================[Aug 15 20:20:01] WARNING[10348]: cdr_adaptive_odbc.c:686 odbc_log: Column type -9 (field ‘diehlnet:cdr:disposition’) is unsupported at this time.
[Aug 15 20:20:01] WARNING[10348]: cdr_adaptive_odbc.c:686 odbc_log: Column type -9 (field ‘diehlnet:cdr:accountcode’) is unsupported at this time.
[Aug 15 20:20:01] WARNING[10348]: cdr_adaptive_odbc.c:686 odbc_log: Column type -9 (field ‘diehlnet:cdr:uniqueid’) is unsupported at this time.
[Aug 15 20:20:01] WARNING[10348]: cdr_adaptive_odbc.c:686 odbc_log: Column type -9 (field ‘diehlnet:cdr:clid’) is unsupported at this time.
[Aug 15 20:20:01] WARNING[10348]: cdr_adaptive_odbc.c:686 odbc_log: Column type -9 (field ‘diehlnet:cdr:src’) is unsupported at this time.
[Aug 15 20:20:01] WARNING[10348]: cdr_adaptive_odbc.c:686 odbc_log: Column type -9 (field ‘diehlnet:cdr:dst’) is unsupported at this time.
[Aug 15 20:20:01] WARNING[10348]: cdr_adaptive_odbc.c:686 odbc_log: Column type -9 (field ‘diehlnet:cdr:dcontext’) is unsupported at this time.
[Aug 15 20:20:01] WARNING[10348]: cdr_adaptive_odbc.c:686 odbc_log: Column type -9 (field ‘diehlnet:cdr:channel’) is unsupported at this time.
[Aug 15 20:20:01] WARNING[10348]: cdr_adaptive_odbc.c:686 odbc_log: Column type -9 (field ‘diehlnet:cdr:dstchannel’) is unsupported at this time.
[Aug 15 20:20:01] WARNING[10348]: cdr_adaptive_odbc.c:686 odbc_log: Column type -9 (field ‘diehlnet:cdr:lastapp’) is unsupported at this time.
[Aug 15 20:20:01] WARNING[10348]: cdr_adaptive_odbc.c:686 odbc_log: Column type -9 (field ‘diehlnet:cdr:lastdata’) is unsupported at this time.
[Aug 15 20:20:01] WARNING[10348]: cdr_adaptive_odbc.c:686 odbc_log: Column type -9 (field ‘diehlnet:cdr:recvip’) is unsupported at this time.
[Aug 15 20:20:01] WARNING[10348]: cdr_adaptive_odbc.c:686 odbc_log: Column type -9 (field ‘diehlnet:cdr:peerip’) is unsupported at this time.
[Aug 15 20:20:01] WARNING[10348]: cdr_adaptive_odbc.c:686 odbc_log: Column type -9 (field ‘diehlnet:cdr:src_number’) is unsupported at this time.
[Aug 15 20:20:01] WARNING[10348]: cdr_adaptive_odbc.c:686 odbc_log: Column type -9 (field ‘diehlnet:cdr:dst_number’) is unsupported at this time.
[Aug 15 20:20:01] WARNING[10348]: cdr_adaptive_odbc.c:686 odbc_log: Column type -9 (field ‘diehlnet:cdr:trunk’) is unsupported at this time.
[Aug 15 20:20:01] WARNING[10348]: cdr_adaptive_odbc.c:686 odbc_log: Column type -8 (field ‘diehlnet:cdr:direction’) is unsupported at this time.
[Aug 15 20:20:01] > [INSERT IGNORE INTO cdr (duration,billsec,amaflags) VALUES
(13,8,3)]
================================================
I know that my Mysql is configured for ut8 encoding and I’m running unixODBC
2.3.0. Asterisk is configured to use Unicode and has been made clean and re-installed.

Any ideas on how to get this to work?