Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

Sent MSD Request ?

Hello

I start a debug cch323 h24 , and i have the follow message:

"Sent MSD Request"

After this, the call wait for 10 seconds and connect succefull.

What is mean "Sent MSD Request" ?

Can i do not sent this message to call is faster?

Looks the debug complete.

Thanks you.

Sep 12 18:31:39: Changing to new event H245_CONNECT_REQ_EVENT

Sep 12 18:31:39: cch323_h245_connection_sm:H245_CONNECT: received event H245_CONNECT_REQ_EVENT while at H245_NONE state

Sep 12 18:31:39: in connection_sm..doing tunneling

changing from H245_NONE state to H245_CONNECTED state

Sep 12 18:31:39: Set new event H245_EVENT_CAP_REQ, for callID 105

Sep 12 18:31:39: cch323_run_h245_cap_out_sm: received event H245_EVENT_CAP_REQ while at state H245_CAP_NONE

Sep 12 18:31:39: changing from H245_CAP_NONE state to H245_CAP_WAIT state

Sep 12 18:31:39: Changing to new event H245_EVENT_MSD, for callID 105

Sep 12 18:31:39: cch323_run_h245_ms_sm: received event H245_EVENT_MSD while at state H245_MS_NONE

Sep 12 18:31:39: changing from H245_MS_NONE state to H245_MS_OUTGOING_WAIT state

cch323_run_h245_ms_sm: Sent MSD Request

Sep 12 18:31:54: Set new event H245_EVENT_CAP_TIMER_EXPIRY, for callID 105

Sep 12 18:31:54: cch323_run_h245_cap_out_sm: received event H245_EVENT_CAP_TIMER_EXPIRY while at state H245_CAP_WAIT

Sep 12 18:31:54: CAP_TIMER_EXPIRY

Sep 12 18:31:54: changing from H245_CAP_WAIT state to H245_CAP_NONE state

Sep 12 18:31:54: Changing to new event H245_EVENT_MS_TIMER_EXPIRY, for callID 105

Sep 12 18:31:54: cch323_run_h245_ms_sm: received event H245_EVENT_MS_TIMER_EXPIRY while at state H245_MS_OUTGOING_WAIT

Error A, Recvd MSD ReleaseReject_ind to APPL!

Sep 12 18:31:54: changing from H245_MS_OUTGOING_WAIT state to H245_MS_NONE state

Sep 12 18:31:55: Changing to new event H245_PROCESS_H245CONTROL

Sep 12 18:31:55: cch323_h245_connection_sm:H245_CONNECT: received event H245_PROCESS_H245CONTROL while at H245_CONNECTED

state

Sep 12 18:31:55: Set new event H245_EVENT_CAP_IND, for callID 105

Sep 12 18:31:55: cch323_run_h245_cap_in_sm: received event H245_EVENT_CAP_IND while at state H245_CAP_IDLE

Sep 12 18:31:55: Set new event H245_EVENT_CAP_REQ, for callID 105

Sep 12 18:31:55: cch323_run_h245_cap_out_sm: received event H245_EVENT_CAP_REQ while at state H245_CAP_NONE

Sep 12 18:31:55: changing from H245_CAP_NONE state to H245_CAP_WAIT state

Sep 12 18:31:55: changing from H245_CAP_IDLE state to H245_CAP_AWAITING_RESPONSE state

Sep 12 18:31:55: Set new event H245_EVENT_CAP_RESP, for callID 105

Sep 12 18:31:55: cch323_run_h245_cap_in_sm: received event H245_EVENT_CAP_RESP while at state H245_CAP_AWAITING_RESPONSE

Sep 12 18:31:55: changing from H245_CAP_AWAITING_RESPONSE state to H245_CAP_IDLE state

Sep 12 18:31:55: cap_notify: check_data_and_usr_inp returned

Sep 12 18:31:55: Changing to new event H245_PROCESS_H245CONTROL

Sep 12 18:31:55: cch323_h245_connection_sm:H245_CONNECT: received event H245_PROCESS_H245CONTROL while at H245_CONNECTED

state

Sep 12 18:31:55: Changing to new event H245_EVENT_MS_IND, for callID 105

Sep 12 18:31:55: cch323_run_h245_ms_sm: received event H245_EVENT_MS_IND while at state H245_MS_NONE

MSDetermination: rtt=60 rsdnum=8674, ltt=60 lsdnum=48

MSDetermination: Am MASTER, ccb->h245.h245_mdStatus = 0x1

MS_Determine_indication to Appl!

Sep 12 18:31:55: changing from H245_MS_NONE state to H245_MS_INCOMING_WAIT state

cch323_run_h245_ms_sm: Sent MSD ACK!

Sep 12 18:31:55: Changing to new event H245_PROCESS_H245CONTROL

Sep 12 18:31:55: cch323_h245_connection_sm:H245_CONNECT: received event H245_PROCESS_H245CONTROL while at H245_CONNECTED

state

Sep 12 18:31:55: Set new event H245_EVENT_CAP_CFM, for callID 105

Sep 12 18:31:55: cch323_run_h245_cap_out_sm: received event H245_EVENT_CAP_CFM while at state H245_CAP_WAIT

Sep 12 18:31:55: changing from H245_CAP_WAIT state to H245_CAP_DONE state

1 REPLY
Silver

Re: Sent MSD Request ?

MSD is nothing but Master Slave determination which is an H245 message negotiated between two endpoints to determine who is master and who is slave.

This message cannot be disabled for a slow-start call scenario.And it is not sent or received for a fast-start call. In cisco routers fast start call is the default.

If you have following config in either/both of the router :

voice service voip

h323

call start slow

Then it is configured for slow start and MSDs will be exchanged.

You can remove the above configs on both orginating and terminating gateways to initiate a fast start voice call

370
Views
0
Helpful
1
Replies
CreatePlease to create content