APC numbers.

Sakae OKUBO okubo at giti.or.jp
Thu Oct 22 06:01:57 EDT 1998


> -----Original Message-----
> From: Ericsson User [SMTP:etxjaeh at AL.ETX.ERICSSON.SE]
> Sent: Thursday, October 15, 1998 4:31 AM
> To:   TIPHON at LIST.ETSI.FR
> Subject:      Re: Gk-GK Call signalling
>
> Jim,
> It was written into the scope of Annex G that the Annex is only about
> RAS.
>
> An Example:
> If you have one Gatekeeper only. That Gatekeeper have a lot of
> information about the user. This information is non-standardized
> properties, e.g the language of the user, the maximum cost of a call to
> PSTN / minute etc ...
> further more the Gatekeeper has a lot of information about the Gateways
> e.g. the cost for breaking out to PSTN.
>
>
> An other example is the phone-to-phone case when ISUP is involved on
> both sides.
> The following parameters are missing or can not be transported
> correctly: (i.e they are also impossible to re-generate in the Gateways)
>
> Access delivery information
> Automatic congestion level
> Backward call indicators
> Call diversion information
> Call history information
> Calling party number (Presentation indicators can not be transported)
> Calling party's category
> Closed user group interlock code
> Connected number(Presentation indicators can not be transported)
> Connection request
> Echo control information
> Facility indicator
> Forward call indicators
> Freephone indicators
> Generic digits
> Generic number(Presentation indicators can not be transported if
> required)
> Generic reference
> Hop counter
> Information indicators @
> Information request indicators
> Location number
> MCID request indicator
> MCID response indicator
> Message compatibility information
> MLPP precedence
> Nature of connection indicators
> Network specific facilities
> Optional backward call indicators
> Optional forward call indicators
> Original called number
> Origination ISC point code
> Parameter compatibility information
> Propagation delay counter
> Redirecting number(Presentation indicators can not be transported)
> Redirection information
> Redirection number(Presentation indicators can not be transported)
> Redirection number restriction
> Service activation @
> Signalling point code @
> Subsequent number
> Suspend/Resume indicators
>
> There are also a number of Messages that cant be interworked.
>
> /Best Regards Jan Holm
>
>
> Jim Toga wrote:
> >
> > Jan,
> >
> > Being one of the contributors of some of the text.... There was no
> intent
> > to limit  GK-GK communications to RAS or Call Control.  The plan of
> attack
> > was to initially solve some specific issues with being able to complete
> > Inter-zone calls.
> >
> > The fact that the messages are carried in RAS format was simply a
> straw-man
> > proposal.  The content and logic was the important starting point.
> >
> > As is always the case, this work moves forward with contributions.
> What
> > specific functions do you want to acomplish?  It might help me (and
> others)
> > to understand where the specific holes are, in order to figure out what
> the
> > next holes are (in the IP context) rather simply saying we need to port
> > ISUP to GKs.
> >
> > Best Regards,
> > jimt.
> >
> > At 01:39 PM 10/13/98 +0100, Ericsson User wrote:
> > >Hello All,
> > >I participated in the SG 16 meeting in Geneva in september.
> > >
> > >One thing that suprised me was that the ongoing work with Annex G
> (GK-GK
> > >signalling) did not consider call control, only the RAS signalling.
> > >
> > >When I asked why, they did not understand why any change is required.
> > >After a while they understood that something could be needed, but it
> was
> > >postponed to future releases of H.323.
> > >
> > >Future releases must be version 4 or something (around year 2001  or
> > >later ??).
> > >
> > >The conclusion is then (looking on TIPHON project plan) that H.323
> can't
> > >be used between Gatekeepers in TIPHON compliant system.
> > >
> > >The question is then: What do we use then? ISUP? B-ISUP? SIP? Extended
> > >subset of H.323?
> > >
> > >
> > >/Jan Holm
> > >Ericsson Telecom AB
> > >
> > >-------------------------------------------------------------------
> > >ATTENTION !!!  TIPHON list distribution parameters have changed:
> > >==> if you REPLY to a TIPHON mail your mail will be sent to the
> > >original sender only.
> > >==> if you use REPLY ALL your mail will be sent to TIPHON and
> > >to the original sender.
> > >-------------------------------------------------------------------
> > >
> >
> > *****************************************************
> > ***  +1-503-264-8816(voice)              Intel - Hillsboro, OR.
> >     ***
> > ***  mailto:jim.toga at intel.com         mailto:james.toga at ties.itu.int
> ***
> > ***  PGP keyID 36 07 86 49 7D 74 DF 57  50 CB BA 32 08 9C 7C 41 ***
> > *****************************************************
> >
> > -------------------------------------------------------------------
> > ATTENTION !!!  TIPHON list distribution parameters have changed:
> > ==> if you REPLY to a TIPHON mail your mail will be sent to the
> > original sender only.
> > ==> if you use REPLY ALL your mail will be sent to TIPHON and
> > to the original sender.
> > -------------------------------------------------------------------
>
> -------------------------------------------------------------------
> ATTENTION !!!  TIPHON list distribution parameters have changed:
> ==> if you REPLY to a TIPHON mail your mail will be sent to the
> original sender only.
> ==> if you use REPLY ALL your mail will be sent to TIPHON and
> to the original sender.
> -------------------------------------------------------------------



More information about the sg16-avd mailing list