Jump to content
Калькуляторы

ras registration confirm

Просвятите что должно возвращатся в RCF в поле callSignalAddress?

cisco возвращает 0, aquagk IP зарегистрированного шлюза, mera IP привратника.

Ткните плиз где почитать подробно можно, пока нашел только общие фразы.

Share this post


Link to post
Share on other sites

H.225.0, Version 2 (March 25, 1997)

 

77 RegistrationConfirm (RCF)

The RCF message includes the following:

requestSeqNum - This shall be the same value that was passed in the RRQ.
protocolIdentifier - identifies the vintage of the accepting gatekeeper.
nonStandardData - carries information not defined in this recommendation (for example, proprietary data)
callSignalAddress - this is an array of transport addresses for H.225.0 call signaling messages; one for each
transport that the gatekeeper will respond to. This address includes the TSAP identifier.
terminalAlias -This optional value is a list of alias addresses, by whichother terminals may identify this terminal.
gatekeeperIdentifier - string to identify the gatekeeper that has accepted the terminals registration.
endpointIdentifier - a gatekeeper assigned terminal identity string; shall be echoed in subseqent RAS messages.
alternateGatekeeper - sequence of prioritised alternateGatekeeper for gatekeeperIdentifer and rasAddress. The
client should use these alternateGatekeeper in the future should a request to the gatekeeper not respond or
return a reject without redirect.
timeToLive - Duration of the validity of the registration, in seconds. After this time the gatekeeper may consider the
registration stale.
tokens - This is some data which may be required to allow the operation. The data shall be inserted into the message
if available.
cryptoTokens - encrypted tokens
integrityCheckValue - provides improved message integrity/message authentication of the RAS messages. The
cryptographically based integrity check value is computed by the sender applying a negotiated integrity
algorithm and the secret key upon the entire message. Prior to integrityCheckValue computation this field
shall be ignored and shall be empty. After computation, the sender puts the computed integrity check value
in the integrityCheckValue field and transmits the message.
willRespondToIRR - true if the Gatekeeper will send an IACK or INAK message in response to an unsolicited IRR
message with its needsResponse field set to true.
preGrantedARQ - Indicates events for which the gatekeeper has pre-granted admission. This allows for faster call
setup times in environments where admission is guaranteed through means other than the ARQ/ACF
exchange. Note that even if these fields are set to TRUE, an endpoint can still send an ARQ to the
gatekeeper for reasons such as address translation, or the endpoint doesn't support this modified signaling
mode. If the preGrantedARQ sequence is not present, then ARQ signaling shall be used in all cases. The
flags are:
makeCall - If the makeCall flag is TRUE then the gatekeeper has pre-granted permission to the endpoint
to initiate calls without first sending an ARQ. If the makeCall flag is FALSE the endpoint shall
always send ARQ to get permission to make a call.
useGKCallSignalAddressToMakeCall - If the makeCall and useGKCallSignalAddressToMakeCall
flags are both set to TRUE, then if the endpoint does not send an ARQ to the gatekeeper to make a
call, the endpoint shall send all H.225 call signalling to the gatekeeper call signalling channel.
answerCall - If the answerCall flag is TRUE then the gatekeeper has pre-granted permission to the
endpoint to answer calls without first sending an ARQ. If the answerCall flag is FALSE the
endpoint shall always send ARQ to get permission to answer a call.
useGKCallSignalAddressToAnswer - If the answerCall and useGKCallSignalAddressToAnswer flags
are both set to true, then when an endpoint does not send an ARQ to the gatekeeper to answer a
call, the endpoint shall ensure that all H.225 call signalling comes from the gatekeeper. If an
endpoint has been instructed to use the gatekeeper when answering, but it does not know whether
an incoming call has come from the gatekeeper (which may involve looking at the transport
address), the endpoint shall issue ARQ irrespective of the state of the
useGKCallSignalAddressToAnswer flag.

Share this post


Link to post
Share on other sites

большое спасибо

Share this post


Link to post
Share on other sites

Если нужны будут сами брошюрки, обращайтесь в личку. )

Share this post


Link to post
Share on other sites

Если нужны будут сами брошюрки, обращайтесь в личку. )

уже нашел нашел брошурки, и разобрался с проблемой.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this