Dean Hoover wrote: > Our company has an Asterisk server where one of the T1s is connected to > an IVR. Asterisk is configured for FXO Loopstart, and the IVR is > configured FXS.
If Asterisk is configured for FXO signaling (not port type), then that means it is expecting to be providing battery and ringing to the other endpoint, since it would the FXS *port*. In this configuration, when a channel is dialed, the port will be put into ringing state, and if configured, Caller ID will be sent. No digits will ever be sent unless done after the call is up by an application. If, on the other hand, Asterisk is configured for FXS signaling, it is acting as an FXO port, and thus under normal circumstances a digit string would be sent when calls are placed on those channel. This is under control of the dialplan, though... using Dial(DAHDI/4) without adding an extension to dial after it would cause chan_dahdi to go off hook, skip sending any digits, and go into 'answered' mode. -- Kevin P. Fleming Digium, Inc. | Director of Software Technologies 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA skype: kpfleming | jabber: kflem...@digium.com Check us out at www.digium.com & www.asterisk.org -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users