RE: Is an xxUA SGP capable of serving multiple SGs

"Barry Nagelberg" <[email protected]>
Newsgroups gmane.ietf.sigtran
Message-ID <[email protected]>
Brian,

Good point. "1 SG supporting multiple networks" is an equally valid way to express the idea.

I nevertheless contend that "multiple SGs in an SGP" is a valid concept. I find it an easy way to conceptualize the
setup that I described below, sort of a mirror image of "multiple ASs in an ASP".

Barry Nagelberg
Adax, Inc.

-----Original Message-----
From: Brian F. G. Bidulock [mailto:[email protected]]
Sent: Tuesday, February 07, 2006 9:30 AM
To: Barry Nagelberg
Cc: [email protected]
Subject: Re: [Sigtran] Is an xxUA SGP capable of serving multiple SGs


Barry,

I would call that 1 SG supporting multiple networks, not an SGP
belonging to multiple SGs.

--brian

Barry Nagelberg wrote:                                               (Tue, 07 Feb 2006 15:24:47)
> Tolga,
>
> There is no need for the "SGP to inform ASP about which SGs that specific SGP is part of". This is known to the craft
> administrator at each end, SGP and ASP.
>
> Let's consider the example in which a single SGP is serving 2 SGs. SG1 represents SS7 network 1 and SG2 represents
> network 2.
> The ASP wishes to register to receive data only for network 1, i.e. SG1. The craft administrators agree that a value
of
> '1' in the Network Appearance param will represent network 1.
>
> 1. When the ASP sends a REG_REQ msg, it includes the Network Appearance param, and sets it to '1'. This tells the SGP
> that the ASP wishes to register to receive data for network 1, i.e. SG1.
>
> 2. The SGP approves the registration request and responds with Routing Context 1. Now the ASP and SGP have established
> that all communications between them for network 1 will be indicated by routing context 1.
>
> Barry Nagelberg
> Adax, Inc.
>

--
Brian F. G. Bidulock
[email protected]
http://www.openss7.org/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.