RE: Recommendation for SUA modifications

Brian,

When an ASP registers with an SG (either via static configuration or
dynamic configuration), one of the optional parameters is destination
address.

IF the ASP has a routing key of destination address and IF the
destination address contains a point code, then the point can be derived
from the set of routing keys that define that RC.  (In the case of
dynamic registration, if the ASP is sending a point code in the
destination address, the this whole issue is moot since the ASP knows
the PC).

Else the point code of the ASP is the same as the point code of the SG.

Regards,
Lincoln

-----Original Message-----
From: Brian F. G. Bidulock [mailto:[email protected]] 
Sent: Wednesday, October 12, 2005 2:45 PM
To: Haresign Lincoln
Cc: [email protected]; [email protected]; [email protected]
Subject: Re: [Sigtran] Recommendation for SUA modifications

Haresign,

Haresign Lincoln wrote:
(Wed, 12 Oct 2005 14:25:49)

-X-snip-X-
> 
> With regards to what you indicated below and the RC.  What I proposed 
> is "the affected PC is optional".  Meaning if the ASP knows the 
> affected PC, it can send it in the SCON (sending SCON is optional).  
> But in the case that the ASP does not know it's PC (e.g., it is 
> sharing the same PC as the SG), then the SG can infer the PC based 
> upon RC.  In the example you gave below, the ASP is sending messages 
> with a particular (and
> known) PC.  The problem that I'm trying to solve (which I've already 
> outlined extensively as a valid scenario) is that the ASP does not 
> know it's PC.

Please detail how the SG infers the point code from the RC.

--brian

--
Brian F. G. Bidulock
[email protected]
http://www.openss7.org/