I have two Cisco gateways terminating voip traffic: GW1 and GW2. No gatekeeper is inolved.
GW1 is able to place calls successfully, but from GW2 calls are failing.
the debug for cch323 and isqn q931 is listed (with some abbreviation).
Can someone point to the possible cause/s of the failure?
Other gateways are able to place successfully to GW1
thanx for any help
value H323_UserInformation ::=
{
h323-uu-pdu
{
h323-message-body setup :
{
protocolIdentifier { 0 0 8 2250 0 3 }
sourceAddress
{
h323-ID : {"VoIP2..."}
}
sourceInfo
{
gateway
{
protocol
{
voice :
{
supportedPrefixes
{
}
}
}
}
mc FALSE
undefinedNode FALSE
}
activeMC FALSE
conferenceID '100D7A02DA9311D6A5F0DCDBF50CDA43'H
conferenceGoal create : NULL
callType pointToPoint : NULL
sourceCallSignalAddress ipAddress :
{
ip 'XXXXXXXX'H
port 41923
}
callIdentifier
{
guid '100D7A02DA9311D6A5F1DCDBF50CDA43'H
}
mediaWaitForConnect FALSE
canOverlapSend FALSE
multipleCalls TRUE <------------------ why is this TRUE?
maintainConnection TRUE
}
h245Tunneling TRUE
nonStandardControl
{
{
nonStandardIdentifier h221NonStandard :
{
t35CountryCode 181
t35Extension 0
manufacturerCode 18
}
data 'C00100028006000400000003'H
}
}
}
}
Oct 9 09:53:42.283 CY: H225 NONSTD INCOMING ENCODE BUFFER::= C0
01000280 06000400 000003
Oct 9 09:53:42.283 CY:
Oct 9 09:53:42.287 CY: H225 NONSTD INCOMING PDU ::=
value H323_UU_NonStdInfo ::=
{
version 0
progIndParam progIndIEinfo :
{
progIndIE '00000003'H
}
}
Oct 9 09:53:42.287 CY: The length of progInd is:[4]
Oct 9 09:53:42.291 CY: cch323_h225_receiver: received msg of type
SETUPIND_CHOSEN
cch323_h225_setup_indcch323_h225_setup_ind: callingNumber[]
calledNumber[RRRRRRRRRRRRR]
Oct 9 09:53:42.291 CY: ======= PI in cch323_h225_setup_ind = 3
Oct 9 09:53:42.291 CY: Receive: infoXCap 0
Oct 9 09:53:42.291 CY: Receive infoXCap ccb 0
Oct 9 09:53:42.291 CY: src address = XXX.XXX.XXX.XXX of SETUPIND_CHOSEN
Oct 9 09:53:42.291 CY: dest address = YYY.YYY.YYY.YYY of SETUPIND_CHOSEN
cch323_run_h225_sm: received event H225_EVENT_SETUP_IND while at state
H225_IDLE
Oct 9 09:53:42.295 CY: h323chan_init_listen_socket: Listen socket [4]
setup successful
Oct 9 09:53:42.295 CY: cch323_h225_generic_setup_treatment: peer
8228DF05, (*peer)->voice_peer_tag 810, ccb: 82D6CFFCH.225 SM: changing
from H225_IDLE state to H225_SETUP state for callID 5
Oct 9 09:53:42.303 CY: src address = XXX.XXX.XXX.XXX of SETUPIND_CHOSEN
Oct 9 09:53:42.303 CY: dest address = YYY.YYY.YYY.YYY of SETUPIND_CHOSEN
Oct 9 09:53:42.319 CY: ISDN Se1/0:15: TX -> SETUP pd = 8 callref = 0x0003
Oct 9 09:53:42.323 CY: Bearer Capability i = 0x8090A3
Oct 9 09:53:42.323 CY: Channel ID i = 0xA9839F
Oct 9 09:53:42.327 CY: Progress Ind i = 0x8183 - Origination
address is non-ISDN
Oct 9 09:53:42.327 CY: Calling Party Number i = 0x2180, 'null',
Plan:ISDN, Type:National
Oct 9 09:53:42.331 CY: Called Party Number i = 0xA1,
'RRRRRRRRRRR', Plan:ISDN, Type:NationalH.225 SM: process event
H225_EVENT_CALLPROC, for callID 5
cch323_run_h225_sm: received event H225_EVENT_CALLPROC while at state
H225_SETUP
H.225 SM: changing from H225_SETUP state to H225_CALLPROC state for callID 5
Oct 9 09:53:42.339 CY: ======= PI in cch323_h225_generic_send_callproc = 0
Oct 9 09:53:42.339 CY: ifTunnelledMessage: no raw message data, no
Annex M2 tunnelling
Oct 9 09:53:42.339 CY: compose_TunnelledSignallingMessage_cisco: no
tunnelledSignallingMessage
Oct 9 09:53:42.339 CY: H225.0 OUTGOING PDU ::=
value H323_UserInformation ::=
{
h323-uu-pdu
{
h323-message-body callProceeding :
{
protocolIdentifier { 0 0 8 2250 0 3 }
destinationInfo
{
mc FALSE
undefinedNode FALSE
}
h245Address ipAddress :
{
ip 'YYYYYYYYY'H
port 11037
}
callIdentifier
{
guid '100D7A02DA9311D6A5F1DCDBF50CDA43'H
}
multipleCalls TRUE
maintainConnection TRUE
}
h245Tunneling FALSE
}
}
.........
D01
Oct 9 09:53:42.371 CY: h225CallProcRequest: Q.931 CALL PROCEEDING sent
fromsocket [3].
Oct 9 09:53:42.575 CY: ISDN Se1/0:15: RX <- CALL_PROC pd = 8 callref
= 0x8003
Oct 9 09:53:42.579 CY: Channel ID i = 0xA9839F
Oct 9 09:53:43.056 CY: h323chan_chn_process_read_socket: fd (4) of type
LISTENING has dataChanging to new event: ACCEPT
h323chan_chn_accept: 4
Oct 9 09:53:43.060 CY: h323chan_gw_accept: TCP connection
accepted from 213.166.20.2:41943 on socket [5]
Oct 9 09:53:43.060 CY: h323chan_chn_accept: Local(0x0) accepts TCP conn
from 213.166.20.2(0xD5A61402) port (0); fd (5)changing from LISTENING
state to ACCEPTED state
Oct 9 09:53:43.068 CY: h323chan_chn_process_read_socket: fd (5) of type
ACCEPTED has dataH.225 SM: process event H225_EVENT_H245_FAILED, for
callID 5
cch323_run_h225_sm: received event H225_EVENT_H245_FAILED while at state
H225_CALLPROC
Oct 9 09:53:43.076 CY: src address = XXX.XXX.XXX.XXX of h225TerminateRequest
Oct 9 09:53:43.080 CY: dest address = YYY.YYY.YYY.YYY Of h225TerminateRequest
Oct 9 09:53:43.080 CY: ifTunnelledMessage: no raw message data, no
Annex M2 tunnelling
Oct 9 09:53:43.080 CY: compose_TunnelledSignallingMessage_cisco: no
tunnelledSignallingMessage
Oct 9 09:53:43.080 CY: H225.0 OUTGOING PDU ::=
value H323_UserInformation ::=
{
h323-uu-pdu
{
h323-message-body releaseComplete :
{
protocolIdentifier { 0 0 8 2250 0 3 }
callIdentifier
{
guid '100D7A02DA9311D6A5F1DCDBF50CDA43'H
}
}
h245Tunneling FALSE
}
}
Oct 9 09:53:43.100 CY: h225TerminateRequest: Q.931 RELEASE COMPLETE
sent from socket [3]. Call state changed to [Null].H.225 SM: process
event H225_EVENT_RELEASE, for callID 5
cch323_run_h225_sm: received event H225_EVENT_RELEASE while at state
H225_CALLPROC
H.225 SM: changing from H225_CALLPROC state to H225_IDLE state for callID 5
Oct 9 09:53:43.104 CY: src address = XXX.XXX.XXX.XXX of h225TerminateRequest
Oct 9 09:53:43.104 CY: dest address = YYY.YYY.YYY.YYY of h225TerminateRequest
Oct 9 09:53:43.108 CY: ifTunnelledMessage: no raw message data, no
Annex M2 tunnelling
Oct 9 09:53:43.108 CY: compose_TunnelledSignallingMessage_cisco: no
tunnelledSignallingMessage
Oct 9 09:53:43.108 CY: H225.0 OUTGOING PDU ::=
value H323_UserInformation ::=
{
h323-uu-pdu
{
h323-message-body releaseComplete :
{
protocolIdentifier { 0 0 8 2250 0 3 }
callIdentifier
{
guid '100D7A02DA9311D6A5F1DCDBF50CDA43'H
}
}
h245Tunneling FALSE
}
}
Oct 9 09:53:43.116 CY: H225.0 OUTGOING ENCODE BUFFER::= 25 80060008
914A0003 11001100 100D7A02 DA9311D6 A5F1DCDB F50CDA43 10800100
Oct 9 09:53:43.120 CY:
Hex representation of the RELEASE COMPLETE TPKT to
send.0802A85E5A080280BF7E0022052580060008914A000311001100100D7A02DA9311D6A5F1DCDBF50CDA43108001000000FD01
Oct 9 09:53:43.124 CY: h225TerminateRequest: Q.931 RELEASE COMPLETE
sent from socket [3]. Call state changed to [Null].
Oct 9 09:53:43.132 CY: h323chan_close: TCP connection from socket
[5] closed
Oct 9 09:53:43.132 CY: h323chan_close: TCP connection from socket
[4] closed
Oct 9 09:53:43.148 CY: ISDN Se1/0:15: TX -> DISCONNECT pd = 8 callref
= 0x0003
Oct 9 09:53:43.152 CY: Cause i = 0x80BF - Service/option not
available, unspecified
Oct 9 09:53:43.184 CY: ISDN Se1/0:15: RX <- RELEASE pd = 8 callref =
0x8003
Oct 9 09:53:43.184 CY: Cause i = 0x8190 - Normal call clearing
Oct 9 09:53:43.196 CY: ISDN Se1/0:15: TX -> RELEASE_COMP pd = 8
callref = 0x0003
Oct 9 09:53:43.436 CY: h323chan_chn_process_read_socket: fd (3) of type
ACCEPTED has datacch323_h225_validate_crv: No CCB for crv :0xA85E
h225ParseData: RELEASE COMPLETE message with non-matching crv[43102]
received. Will take no action.
