Michal, Thanks for pointing me to the H.225 section 7.4.1. However I am afraid that that part is not sufficient. I am interested in the H.323 stuff and I am concerned about clear specifications of implemented functionality, otherwise a lot of lost energy in interoperability problem solving can be expected. Hereafter I explain why I think that this is the case: I quote from table 14 in section 7.4.1 in the H.225 spec: NOTE - If the Facility message is used for carrying Q.95x supplementary service signalling, one of either the Facility or Extended Facility information elements is required. If the Facility message is used for Supplementary Service control according to H.450.x-series Recommendations, or if the Facility message is used for the reroute to MC/GK functions, then the zero-length Facility information element is required. and further: The user-to-user information element contains the Facility-UUIE defined in the H.225.0 Message Syntax. The Facility-UUIE includes the following: ....... alternativeAliasAddress - Contains aliases that can be used to re-direct the call; if an alias is provided, alternativeAddress is not needed. As you can see the AlternativeAliasAddress is an element in an Facility-UUIE, which is not the same as the Facility-IE. Further you can see that the Facility-UUIE is only used in case of H.450 and reroute to MC/GK functions. So..I am afraid that the implementation isn't specified clearly and the only non H.450 implementations would have to implement Q.95x signaling in the Facility-IE and Extended Facility-IE. Dirk Los -----Original Message----- From: Zygmuntowicz Michal [SMTP:m.zygmuntowicz@onet.pl] Sent: Tuesday, November 25, 2003 1:09 AM To: openh323gk-users@lists.sourceforge.net Subject: Re: again on call forwarding If you are interested in H.323 communication - you will rarely need to dig other recommendations to H.323, H.225 and H.245. You will find enough information at: ITU-T H.225, Chapter 7.4.1 Facility ITU-T H.323, Chapter 8.1.10 Call forwarding ----- Original Message ----- From: "dirk los" <dirk@luna.nl> Sent: Tuesday, November 25, 2003 12:40 AM > As far as I could dig in the standards I came to the conclusion that it > should concern Q.932, which gives a description of the generic protocol to > be used for supplementary services for ISDN. > Q.931 describes the protocol for basic ISDN services. > However I don't know the standard, on which the implemented forwarding > functionality is based. > Do you know a way to come behind the screens? ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ List: Openh323gk-users@lists.sourceforge.net Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/ ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ List: Openh323gk-users@lists.sourceforge.net Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/
