RE: SUA: Relay: SG-SG

"May, Howard" <[email protected]>
Newsgroups gmane.ietf.sigtran
Message-ID <39CC97884CA19A4D8D6296FE94357BCB047C1AC0@swsmsx404>
Brian, Ilie,

Allow me to modify my request in light of your previous comments:

I would value seeing example message flows for the following:
1) IPSP to Relay communication
2) Relay to Relay communication

Regards

Howard


 

>-----Original Message-----
>From: Brian F. G. Bidulock [mailto:[email protected]] 
>Sent: 20 February 2006 10:05
>To: May, Howard
>Cc: [email protected]; [email protected]
>Subject: Re: [Sigtran] SUA: Relay: SG-SG
>
>Howard,
>
>May, Howard wrote:                           (Mon, 20 Feb 2006 
>09:36:42)
>> Hi Brian, Ilie
>> 
>> Consider the following simple system:
>> 
>> AS1(PC10)/ASP1 connecting to SGP1.
>> AS2(PC20)/ASP2 connected to SGP2.
>> SGP1 and SGP2 both contain the relay function and connect to 
>each other.
>> 
>> Assume the following initial state:
>> 
>> ASP1/ASP2 UP and AS1/AS2 ACTIVE.
>> SGP1/SGP2 association down.
>> 
>> My question is:
>> 
>> Once the association between SGP1 and SGP2 is established 
>what message
>> flow would be expected.
>
>Some more questions:
>
>Do SGP1 and SGP2 belong to the same SG?  Different SG?
>
>If different SG, why do you have an association between
>SGP1(SG1) and SGP2(SG2)?  By definition, SGs are connected to
>the SS7 network and therefore technically can signal each other
>over the SS7 network.
>
>If you want to rule out the SS7 network in your example, make
>them IPSPs instead of SGs (i.e., take away the SG function).  In
>which case the ASPs are really more appropriately described as
>SE IPSPs without the relay or SG function.
>
>--brian
>
>> 
>> To put it another way; I would find it very helpful to see 
>some example
>> message flows for SG-SG relay functionality.
>> 
>> Regards
>> 
>> Howard
>> 
>
>-- 
>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.