IMTC Liaison

Sebestyen Istvan ICN WN ES SP 4 Istvan.Sebestyen at ICN.SIEMENS.DE
Mon Nov 16 08:58:18 EST 1998


Thanks for your comment.

CRV is unique just at one signalling link of a call (e.g. between EP A and
GK; and may be different between GK and EP2 of the same call) .

Since CallID may be preserved when calls are redirected (incl. transfer,
forward,...), the CallID actually identifies the call scenario and not
exactly one call. I think this is fine.

A CallLegID would be a new identifier that is somehow in between CallID and
CRV by identifying exactly one call (or call attempt) between two endpoints.
We might think about for H.225.0v3.


> -----Ursprüngliche Nachricht-----
> Von:  Chris Purvis [SMTP:CPurvis at MADGE.COM]
> Gesendet am:  Montag, 16. November 1998 12:52
> An:   ITU-SG16 at
> Betreff:      Re: Usage of CallID in H.323v2 for rerouted (diverted,
> transferre d,.. .) calls
> Karl,
> I agree with your comments on CallID being preserved when calls are
> transferred.  However...
> >As an alternative, we might add a new multilevel CallID (e.g.
> >to H.225.0 v3)
> >that consists of an identifier that indicates the "overal
> >call" and a second
> >identifier that indicates the call leg.
        Isn't this the CRV, that's always been there?

> Regards,
> Chris
> --
> Dr Chris Purvis - Senior Development Engineer, WAVE CC Software
> Madge Networks Ltd, Wexham Springs, Framewood Road, Wexham, Berks.
> Phone:+44 1753 661359  email: cpurvis at

More information about the sg16-avd mailing list