58
ScoopTeam - User manual - Draft 0002
Use a distinctive ISDN number on each codec: this is possible only if the ISDN line supports
more than one subscriber number. However this is not always possible with a public ISDN line.
Use a distinctive sub-address on each codec.
In either case the calling device can select the codec that should answer by calling for the appropriate
number and/or sub-address.
If an ISDN line is connected but this line is not the current network interface, the ScoopTeam will
however accept incoming ISDN calls, provided that it is not already busy with an AoIP connection. In
such event the unit will switch to the ISDN Interface when receiving the ISDN call. Once the
connection is released, the ScoopTeam will come back to its previous default interface.
AoIP incoming calls
Such calls are accepted if they are presented on the interface that is selected as default for outgoing
calls. However, there is an exception: while the current interface is the ISDN line, the unit can still
register on a SIP server via the primary Ethernet interface, and it can accept calls presented on this
interface (either directly or via a SIP server).
Receiving
SIP incoming calls
is very simple, regardless if it is a direct peer to peer link or a call via a SIP
server. There is nothing to do… When a call is received, the units negotiate automatically a commonly
acceptable coding algorithm, and set the link automatically. On the receiving side, ScoopTeam “follows”
the calling unit.
Direct RTP
incoming calls are less straightforward to set up, because the unit must be set up beforehand
with exactly the same coding configuration as the calling device. In addition, the caller must be aware, in
addition of the IP address of the ScoopTeam to call, of the port used for the RTP transmission.
More
explanation about the operation with Direct RTP is provided in the section related to the AoIP settings:
4.6.2, Network sub-menu, AoIP settings.
Dealing with the
double SIP codec
mode: the best for receiving calls in such mode is to use a couple of
SIP accounts on a server, one for each codec. In this case, the two codecs are unambiguously identified
with distinctive numbers, and a caller device can address specifically either codec. Otherwise, if there is
no SIP registration, or only one, all incoming calls are directed to the same single identifier (IP address or
SIP URI). Then the rule is that Codec 1 answers first if available. If it is already busy with a connection,
then the call is accepted by Codec 2.
