<div dir="ltr">On Sun, May 19, 2013 at 11:25 AM, Łukasz Zwierko <span dir="ltr"><<a href="mailto:lzwierko@gmail.com" target="_blank">lzwierko@gmail.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I'm aware that chan_phone is probably not very widely used, still I'd<br>
have a question about it. I really do hope Mark Spencer or any module<br>
co-authors (if there were any) can answer this simple question:<br></blockquote><div><br></div><div>I've never used the chan_phone module, nor have I ever had the (mis)fortune to ever look at that code. However, I'll point out a couple of things that might help.<br>
</div><div><br></div><div>In Asterisk, the confusion between FXO and FXS typically comes from whether you're talking about the *ports* or the *signaling*. <br><br>An FXO port connects to the central office (remember the O in FXO and Office), but to the central office it acts (or signals) like a station. Hence an FXO port in Asterisk uses FXS signaling.<br>
<br></div><div>An FXS port connections to a station (a telephone), but to the telephone is acts (or signals) like the central office. Hence an FXS port uses FXO signaling.<br><br></div><div>Last but not least, in most of the configuration files and what code I've looked at, Asterisk typically deals with the *signaling* side of the equation. As I said earlier, I don't know chan_phone at all, but in chan_dahdi, you'd configure something like "fxsls" signaling for an FXO port -- where fxsls stands for "FXS Loop Start".<br>
<br></div><div>Hopefully that helps get rid of some confusion.<br><br>--<br></div><div>Jared Smith<br></div></div></div></div>