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

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

No voice calls TX -> CONNECT sent after rtp stream establish

Hello Guys,

I have a strange behavior on the IPTel network of one of my customer. Sometimes (1-2 times a week) the customer had a faulty calls. When he received an incoming calls, he heard nothing. The callers sometimes heard somethings (not each time).

I enable a lot of logs on the gateway and I found the following:

The RTP stream is established only in one way but the:

36620774: Oct  3 08:34:49.464: ISDN Se0/0/0:15 Q931: TX -> CONNECT pd = 8  callref = 0x8345

Is sent after the RTP stream is ended (stream has a duration of 5 sec), when the caller/called hang off.

Normally the "TX -> CONNECT" is sent before the RTP stream establishement.

I attached the complete call flow. I change the phone number:

Caller ID is:YYYYYYYYYY

Called ID is: XXXXXXXXXX

Internal extension: 811

Thanks a lot for your help !

Hervé Jacquemin

1 REPLY

Re: No voice calls TX -> CONNECT sent after rtp stream establis

Your gateway doesn't send the ACK in response of received 200OK. Try to disable PRACK.

Could be not correctly handled.

Sent:

INVITE sip:811@192.168.150.3:5060 SIP/2.0

Via: SIP/2.0/TCP 192.168.150.2:5060;branch=z9hG4bK1E8EAF0

Call-ID: AF63FA16-2B2C11E3-992DD659-40589DE0@192.168.150.2

CSeq: 101 INVITE

Received:

SIP/2.0 100 Trying (concerned to INVITE)

Via: SIP/2.0/TCP 192.168.150.2:5060;branch=z9hG4bK1E8EAF0

Call-ID: AF63FA16-2B2C11E3-992DD659-40589DE0@192.168.150.2

CSeq: 101 INVITE

Received:

SIP/2.0 180 Ringing (concerned to INVITE)

Via: SIP/2.0/TCP 192.168.150.2:5060;branch=z9hG4bK1E8EAF0

Call-ID: AF63FA16-2B2C11E3-992DD659-40589DE0@192.168.150.2

CSeq: 101 INVITE

Sent:

PRACK sip:811@192.168.150.3:5060;transport=tcp SIP/2.0

Via: SIP/2.0/TCP 192.168.150.2:5060;branch=z9hG4bK1E8F9A1

Call-ID: AF63FA16-2B2C11E3-992DD659-40589DE0@192.168.150.2

CSeq: 102 PRACK

Received:

SIP/2.0 200 OK (concerned to PRACK)

Via: SIP/2.0/TCP 192.168.150.2:5060;branch=z9hG4bK1E8F9A1

Call-ID: AF63FA16-2B2C11E3-992DD659-40589DE0@192.168.150.2

CSeq: 102 PRACK

Received:

SIP/2.0 200 OK (concerned to INVITE)

Via: SIP/2.0/TCP 192.168.150.2:5060;branch=z9hG4bK1E8EAF0

Call-ID: AF63FA16-2B2C11E3-992DD659-40589DE0@192.168.150.2

CSeq: 101 INVITE

Sent:

ACK sip:811@192.168.150.3:5060;transport=tcp SIP/2.0  (concerned to PRACK)

Via: SIP/2.0/TCP 192.168.150.2:5060;branch=z9hG4bK1E906A1

Call-ID: AF63FA16-2B2C11E3-992DD659-40589DE0@192.168.150.2

CSeq: 101 ACK

Received:

SIP/2.0 200 OK  (concerned to INVITE)

Via: SIP/2.0/TCP 192.168.150.2:5060;branch=z9hG4bK1E8EAF0

Call-ID: AF63FA16-2B2C11E3-992DD659-40589DE0@192.168.150.2

CSeq: 101 INVITE

Received:

SIP/2.0 200 OK (concerned to INVITE)

Via: SIP/2.0/TCP 192.168.150.2:5060;branch=z9hG4bK1E8EAF0

Call-ID: AF63FA16-2B2C11E3-992DD659-40589DE0@192.168.150.2

CSeq: 101 INVITE

Sent:

ACK sip:811@192.168.150.3:5060;transport=tcp SIP/2.0  (concerned to PRACK)

Via: SIP/2.0/TCP 192.168.150.2:5060;branch=z9hG4bK1E906A1

Call-ID: AF63FA16-2B2C11E3-992DD659-40589DE0@192.168.150.2

CSeq: 101 ACK

Sent:

ACK sip:811@192.168.150.3:5060;transport=tcp SIP/2.0  (concerned to PRACK)

Via: SIP/2.0/TCP 192.168.150.2:5060;branch=z9hG4bK1E906A1

Call-ID: AF63FA16-2B2C11E3-992DD659-40589DE0@192.168.150.2

CSeq: 101 ACK

Received:

SIP/2.0 200 OK  (concerned to INVITE)

Via: SIP/2.0/TCP 192.168.150.2:5060;branch=z9hG4bK1E8EAF0

Call-ID: AF63FA16-2B2C11E3-992DD659-40589DE0@192.168.150.2

CSeq: 101 INVITE

200 ok timeout

Regards.

206
Views
0
Helpful
1
Replies