E153 - timedout while waiting 'OK' in response to 'AT'

[joseph]

Hullo,

I have been using chan_datacard with 13 E153s without a problem for
about 3 weeks. This week though I have been having a few problems; the
modems keep getting disconnected and showing "GSM not registered".
This seems to have started when I changed SIMs to test a different
network. The only visible errors are chan_datacard.c:422
do_monitor_phone: [datacard1] timedout while waiting 'OK' in response
to 'AT' for the different modems.

Could this problem be related to the network, the modem or
chan_datacard itself.

The modems are all directly connected to the computer save for 3 that
are hooked to a NEC chip USB expansion card.

Relevant details:

Asterisk 1.6.2.7
chan_datacard: Datacard Channel Driver, Version 1.0, Revision 310
Linux 2.6.35-27-generic-pae #48-Ubuntu SMP

Thanks, Joseph

[joseph]

This problem seems to be getting worse. Now every so often, asterisk
will just hang and only way to get into it is to restart it.

Is there anyone using E153s on this forum or who has had a similar
problem that can help?

Joseph

[joseph]

Went through the logs and found this:

rtp.c: Unable to allocate RTP socket: Too many open files
acl.c: Cannot create socket
pbx_spool.c: Unable to open directory /var/spool/asterisk/outgoing:
Too many open files

I enabled SYSMAXFILES=262144 and MAXFILES=32768 in /usr/sbin/
safe_asterisk and errors went away.

However, these errors (also from logs) are what am now
troubleshooting:

channel.c: [r1] Request to call on device which can not make call at
this moment
app_dial.c: Unable to create channel of type 'Datacard' (cause 44 -
Requested channel not available)

This seems to occur when datacards are in the 'dialing' state. Seems
asterisk doesn't know the channel is busy when it is in the dialing
state and still tries to send a call to it.

This is despite have a call-limit of 10 on the sip peer (12 datacards
installed) and all cards are either in 'dialing' or 'active' state.

[S Adrian]

It does know it's in dialing state, that's why you get the error ! :)
but you don't know it's in dialing state and still try to dial !

[Ramón Lozano SOLID PC, S.L.]

Maybe signal problems? Interferences?

The strange thing is you didn't have those problems before... so maybe it's no signal related.

Ramón Lozano
SOLID PC. S.L.
www.solidpc.net

2011/3/31 joseph <klas...@gmail.com>