asterisk users - Dec 2007 - No SMDI interfaces are available

Hi,

I'm a brand newbie to asterisk trying to set it up for the first time 
and I can't get a softphone to connect, the connection times out.
I had a trixbox pro install working, but I need more control and would 
like to learn to do it with asterisk.

 In /var/log/asterisk/messages I see:

WARNING[17401] res_smdi.c: No SMDI interfaces are available to listen 
on, not starting SMDI listener.

on startup.  Can someone clue me in as to what this means?  Is it the 
cause of my timeouts?

Asterisk version 1.4.16.2, no hardware, zaptel is running with the 
ztdummy driver.

thanks,

--charlie

-- 
------------------------------------------------------------------------
Charles Farinella 
Appropriate Solutions, Inc. (www.AppropriateSolutions.com)
cfarinella at AppropriateSolutions.com
voice: 603.924.6079   fax: 603.924.8668

> -----Original Message-----
> From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-
> bounces at lists.digium.com] On Behalf Of Charlie Farinella
> Sent: Thursday, December 27, 2007 11:11 AM
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: [asterisk-users] No SMDI interfaces are available
> 
> Hi,
> 
> I'm a brand newbie to asterisk trying to set it up for the first time
> and I can't get a softphone to connect, the connection times out.
> I had a trixbox pro install working, but I need more control and would
> like to learn to do it with asterisk.
> 
>  In /var/log/asterisk/messages I see:
> 
> WARNING[17401] res_smdi.c: No SMDI interfaces are available to listen
> on, not starting SMDI listener.
> 
> on startup.  Can someone clue me in as to what this means?  Is it the
> cause of my timeouts?
> 
> Asterisk version 1.4.16.2, no hardware, zaptel is running with the
> ztdummy driver.
> 
> thanks,
> 
> --charlie
> 
> --
>
------------------------------------------------------------------------
> Charles Farinella
> Appropriate Solutions, Inc. (www.AppropriateSolutions.com)
> cfarinella at AppropriateSolutions.com
> voice: 603.924.6079   fax: 603.924.8668
> 
> 
Simplified Message Desk Interface (SMDI) defines a way for a phone
system to provide voice-messaging systems with the information that the
system needs to intelligently process incoming calls. Each time that the
phone system routes a call, it sends an SMDI message through an
EIA/TIA-232 connection to the voice-messaging system that tells it the
line that it is using, the type of call that it is forwarding, and
information about the source and destination of the call.

So this is NOT the problem in your case.

I would start by checking the basic TCP/ip connectivity b/w the machine
running the * PBX and your Softphone.

Try this:
iptables -L
	are they any rules listed, by default many linux distros setup a
basic fierewall for you that by default rejects or drops everything but
ssh and/or http. 

Ping your PBX from your softphone PC. Is it reachable?

Is asterisk running?  (asterisk -rvvvvv)

On Thursday 27 December 2007, Alexander Lopez wrote:
> I would start by checking the basic TCP/ip connectivity b/w the 
machine
> running the * PBX and your Softphone.
> 
> Try this:
> iptables -L
> 	are they any rules listed, by default many linux distros setup a
> basic fierewall for you that by default rejects or drops everything 
but
> ssh and/or http. 
> 
> Ping your PBX from your softphone PC. Is it reachable?
> 
> Is asterisk running?  (asterisk -rvvvvv)
Duh!!

Everything was set correctly except for the fact that eth0 was *not* set 
as a trusted device!  Thanks for the pointer.

--charlie

-- 
------------------------------------------------------------------------
Charles Farinella 
Appropriate Solutions, Inc. (www.AppropriateSolutions.com)
cfarinella at AppropriateSolutions.com
voice: 603.924.6079   fax: 603.924.8668