cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
marco
New Contributor II

How to route inbound FXO calls to FXS line

Hello experts,

I have an ATLAS 550 wiht an octal FXO and octal FXS.

The FXO is connected to two outside lines.

How do I route a call coming in on FXO 1 to a number related to port 1 on the FXS, or directly to port 1 of the FXS

same for the ports FXO 2 and FXS 2.

I'm not sure if the incoming lines show DNIS.

Thanks in advance,

Best regards,

Marco

Tags (4)
0 Kudos
4 Replies
patrick
Valued Contributor
Valued Contributor

Re: How to route inbound FXO calls to FXS line

Hello Marco, and thank you for using the ADTRAN Support Community Forums.

In order to route a call into an FXO port and out an FXS port you will have to configure the ports under the DIAL PLAN, with the FXO being in the NETWORK TERM and the FXS as a USER TERM.

In a standard POTS (plain old telephone service) line, the DNIS or DID is not delivered; only the ring voltage. So in the ATLAS, for the FXO port under the IFCE CONFIG (or interface configuration) there is a TRUNK NUMBER option. This is where you define what number to associate with this port, so when the ATLAS receives the ring voltage it will route the call based on the TRUNK NUMBER. So you will then configure the FXS ports with an IN#ACCEPT of the appropriate TRUNK NUMBER defined for the FXO port.

As a note, the ATLAS FXO port does not pass caller ID information.

Hope this answers your question,
Patrick

marco
New Contributor II

Re: How to route inbound FXO calls to FXS line

Hi Patrick,

Thanks for your quick response.

I could not find the TRUNK NUMBER option.

I filled in the number under DID prefix, that does the job.

Two extra questions here.

If i have to one a new threat for this please let me know.

1. Can the trunk number be sourced with outgoing calls ?

2. Can I force an outgoing call to be a data call ?

Thanks in advance,

Marco

patrick
Valued Contributor
Valued Contributor

Re: How to route inbound FXO calls to FXS line

On the FXO IFCE CONFIG, if you have "Direct Inward Dialing" set to ENABLED, then you do not have a TRUNK NUMBER option, because DID means the ATLAS will receive digits on an inbound call. Since it doesn't  sound like the ATLAS is receiving digits, you may have a delay while the ATLAS waits for digits, before it times out (the default is 16 seconds).

1) The TRUNK NUMBER cannot be used with outbound calls, but you can use SOURCE IDs. On the FXS ports, under the IFCE CONFIG you assign a SOURCE ID (SID) of 0-9 (with 0 being the default). Then under the NETWORK TERM, you can configure the OUT#ACCEPT to accept SID=X (with X being the SID you want it to accept) and an ACCEPT NUMBER of "$".

You can have FXS #1 keep SID=0, and under the NETWORK TERM you configure FXO #1 with an OUT#ACCEPT having an SID=0 and ACCEPT NUMBER="$" (the SID forces a call originating from FXS #1 to go out FXO #1)

You can have FXS #2 set SID=1, and under the NETWORK TERM you configure FXO #2 with an OUT#ACCEPT having an SID=1 and ACCEPT NUMBER="$" (the SID forces a call originating from FXS #2 to go out FXO #2)

2) You cannot force an outgoing call to be data with a POTS line. There is no "call type" negotiation sent on a POTS line to the telephone company. The line goes offhook and the DTMF digits are sent to the Telco. The Telco decides how to route the call. So ALL calls are audio. Modems and Faxes pass audio tones in order to send data across the connection. There is no "data" call on a POTS line.

marco
New Contributor II

Re: How to route inbound FXO calls to FXS line

Hi
Patrick,

Thanks for your detailed reply.

See my answers inline


Best regards,
Marco




ADTRAN Support
Community
How to route inbound FXO calls to FXS line
created by patrick
in ATLAS 550 Series - View the full discussion


On the FXO IFCE
CONFIG, if you have "Direct Inward Dialing" set to ENABLED, then you do not have
a TRUNK NUMBER option, because DID means the ATLAS will receive digits on an
inbound call. Since it doesn't  sound like the ATLAS is receiving digits, you
may have a delay while the ATLAS waits for digits, before it times out (the
default is 16 seconds).

> Aha, I'll disable it. and then set the Trunk
#
> I seems that I receive the digits, because it does not time
out.
> but the trunk option looks like the more flexible way to
go.
> I can arrange the MSN's to end up at the specific FXO, to do some
more
> call routing if needed.

1) The TRUNK NUMBER cannot be used
with outbound calls, but you can use SOURCE IDs. On the FXS ports, under the
IFCE CONFIG you assign a SOURCE ID (SID) of 0-9 (with 0 being the default). Then
under the NETWORK TERM, you can configure the OUT#ACCEPT to accept SID=X (with X
being the SID you want it to accept) and an ACCEPT NUMBER of "$".
You can
have FXS #1 keep SID=0, and under the NETWORK TERM you configure FXO #1 with an
OUT#ACCEPT having an SID=0 and ACCEPT NUMBER="$" (the SID forces a call
originating from FXS #1 to go out FXO #1)
You can have FXS #2 set SID=1, and
under the NETWORK TERM you configure FXO #2 with an OUT#ACCEPT having an SID=1
and ACCEPT NUMBER="$" (the SID forces a call originating from FXS #2 to go out
FXO #2)

> Ok, that is clarifies the use of the SID to me.
> this
will work fine for me.

2) You cannot force an outgoing call to be data
with a POTS line. There is no "call type" negotiation sent on a POTS line to the
telephone company. The line goes offhook and the DTMF digits are sent to the
Telco. The Telco decides how to route the call. So ALL calls are audio. Modems
and Faxes pass audio tones in order to send data across the connection. There is
no "data" call on a POTS line.

> Sorry, That I should have known.