Re: Doubt regarding Dynamic registration and DE model

Mohammad,

Mohammad Arif wrote:                               (Wed, 27 Jun 2007 17:56:04)
> 
>    Hi ,
> 
> 
> 
>    IF  one M3UA peer supports SE model and another supports DE model,then
>    how will they communicate.?

Both must support SE.  See RFC 4666/4.3:

 4.3.  AS and ASP/IPSP State Maintenance

   ...

   In order to ensure interoperability, an M3UA implementation
   supporting IPSP communication MUST support the IPSP SE model and MAY
   implement the IPSP DE model.

> 
>    How  will  local M3UA endpoint knows that the remote end is supporting
>    the same model( SE or DE)?

Well, if it supports IPSP at all, it MUST support SE and only MAY support DE.
Therefore, for DE mode operation, both ends will have to be configured for DE
operation.

>    My Second doubt is,
> 
>    Can  Routing  Key  be  a  static configurable  data ( to be entered by
>    user)? Or it is always generated from OPC,DPC,SLS. ?

Any data can be used.  See RFC 4666/1.4.2.1:

   ... 

   Possible SS7 address/routing information that comprise a Routing Key
   entry includes, for example, the OPC, DPC, and SIO found in the MTP3
   routing label.  Some example Routing Keys are: the DPC alone, the
   DPC/OPC combination, or the DPC/OPC/SI combination.  The particular
   information used to define an M3UA Routing Key is application and
   network dependent, and none of the above examples are mandated.

>    Does the static configuring of routing key depend on SE or DE model?

No. See RFC 4666/1.4.2.3:

   There are two ways to provision a Routing Key at an SGP.  A Routing
   Key may be configured statically using an implementation dependent
   management interface, or dynamically using the M3UA Routing Key
   registration procedure.

>    I have an understanding that DE model supports dynamic registration so
>    routing key is  not configurable , it is generated.

No. See RFC 4666/1.4.2.3:

   There are two ways to provision a Routing Key at an SGP.  A Routing
   Key may be configured statically using an implementation dependent
   management interface, or dynamically using the M3UA Routing Key
   registration procedure.

--brian

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