<br><br><div class="gmail_quote">On Sat, Jan 9, 2010 at 9:40 AM, Joseph L. Casale <span dir="ltr"><<a href="mailto:jcasale@activenetwerx.com">jcasale@activenetwerx.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
It seems there are two ways to configure an spa3102's fxo port w/<br>
pbx's, you can set the dial plan to <phone_#_of_pstn>@<freeswitch_ip><br>
or <ext_to_dial>@<freeswitch_ip>.<br>
<br>
>From fs's perspective, what exactly is the difference here?<br>
Are there any significant differences between the two methods?<br>
Are there any best practices that should be considered?<br></blockquote><div><br>I've only got a PAP2T (2 FXS) but from what you describe I'd say that it makes sense for the FXO port to be "phone_#_of_pstn" and FXS to be "ext_to_dial." I believe FS tries to be endpoint-type agnostic in this scenario. It's a SIP call in and gets routed in the dialplan. <br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Incoming sip did's and a zap line I had all were configured so that<br>
they entered the public context filtered by <phone_#>.<br>
<br></blockquote><div>If a call is coming in from an actual PSTN line then hitting the public context makes a lot of sense. <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Most of the examples I see for setting up the spa don't function like this<br>
but a couple do?<br></blockquote><div>As usual "it depends." However, the simplest rule of thumb would be that FXS ports are analogous to SIP users and FXO ports are analogous to SIP gateways. <br><br>Out of curiosity, what is your application?<br>
-MC<br></div></div><br>