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

ISDN to SIP (outbound) calls are failing after too many 183 sessions

Hi,

I am trying to make outbound SIP calls from my cisco gateway, some how i am recieving too many 183 session progress and than call fails from 408 Request timeout.

Please if some one help me to solve this issue.

here is my call trace, i am not showing all 183 session progress here

it has 3,4 more same messages

----------------------------------------------------------------------------------------------------------------------------------------

*Feb 21 22:42:17.875: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 183 Session Progress

Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK4F07DC16

From: <sip:4444444444@192.168.0.1>;tag=685B115C-562

To: <sip:55555555555@10.1.2.3>;tag=4EB5B022-3E9BA47-0A11F61A

Call-ID: 9A7CF310-78111D5-B39FFC41-39B5E64@192.168.0.1

CSeq: 101 INVITE

Timestamp: 982795330

Contact: <sip:10.1.2.3:5060;transport=udp>

Require: 100rel

RSeq: 1

Allow: CANCEL,INFO,OPTIONS,BYE,PRACK,UPDATE

Content-Length: 0

*Feb 21 22:42:25.971: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 183 Session Progress

Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK4F07DC16

From: <sip:4444444444@192.168.0.1>;tag=685B115C-562

To: <sip:55555555555@10.1.2.3>;tag=4EB5B022-3E9BA47-0A11F61A

Call-ID: 9A7CF310-78111D5-B39FFC41-39B5E64@192.168.0.1

CSeq: 101 INVITE

Timestamp: 982795330

Contact: <sip:10.1.2.3:5060;transport=udp>

Require: 100rel

RSeq: 1

Allow: CANCEL,INFO,OPTIONS,BYE,PRACK,UPDATE

Content-Length: 0

*Feb 21 22:42:39.775: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

OPTIONS sip:192.168.0.1:5060 SIP/2.0

Via: SIP/2.0/UDP 10.1.2.3:5060;branch=z9hG4bK08tahp30doe1qjcrb301.1

From: <sip:10.1.2.3>;tag=4EB5B03F-3E9BE5C-0A11F61A

To: <sip:192.168.0.1>

Call-ID: 4EB5B03F-00127829@asnmdjfj001

CSeq: 1227 OPTIONS

Supported: timer

Max-Forwards: 69

Content-Length: 0

*Feb 21 22:42:39.779: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 10.1.2.3:5060;branch=z9hG4bK08tahp30doe1qjcrb301.1

From: <sip:10.1.2.3>;tag=4EB5B03F-3E9BE5C-0A11F61A

To: <sip:192.168.0.1>;tag=685B8524-1C57

Date: Wed, 21 Feb 2001 22:42:39 GMT

Call-ID: 4EB5B03F-00127829@asnmdjfj001

Server: Cisco-SIPGateway/IOS-12.x

CSeq: 1227 OPTIONS

Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY

, INFO, UPDATE, REGISTER

Accept: application/sdp

Allow-Events: telephone-event

Content-Length: 164

Content-Type: application/sdp

v=0

o=CiscoSystemsSIP-GW-UserAgent 6831 9300 IN IP4 192.168.0.1

s=SIP Call

c=IN IP4 192.168.0.1

t=0 0

m=audio 0 RTP/AVP 18 0 8 4 2 3

c=IN IP4 192.168.0.1

*Feb 21 22:42:42.191: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

BYE sip:4444444444@192.168.0.1:5060 SIP/2.0

Via: SIP/2.0/UDP 10.1.2.3:5060;branch=z9hG4bK5hbef0104gg1cks1k081.1

From: <sip:55555555555@10.1.2.3>;tag=4EB5B022-3E9BA47-0A11F61A

To: <sip:4444444444@192.168.0.1>;tag=685B115C-562

Call-ID: 9A7CF310-78111D5-B39FFC41-39B5E64@192.168.0.1

CSeq: 1 BYE

Supported: timer

Max-Forwards: 69

Reason: SIP ;cause=408

Reason: Q.850 ;cause=127 ;text="Interworking, unspecified"

Content-Length: 0

*Feb 21 22:42:42.191: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 408 Request Timeout

Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK4F07DC16

From: <sip:4444444444@192.168.0.1>;tag=685B115C-562

To: <sip:55555555555@10.1.2.3>;tag=4EB5B022-3E9BA47-0A11F61A

Call-ID: 9A7CF310-78111D5-B39FFC41-39B5E64@192.168.0.1

CSeq: 101 INVITE

Timestamp: 982795330

Reason: Q.850 ;cause=127 ;text="Interworking, unspecified"

Content-Length: 0

*Feb 21 22:42:42.199: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

ACK sip:55555555555@10.1.2.3:5060 SIP/2.0

Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK4F07DC16

From: <sip:4444444444@192.168.0.1>;tag=685B115C-562

To: <sip:55555555555@10.1.2.3>;tag=4EB5B022-3E9BA47-0A11F61A

Date: Wed, 21 Feb 2001 22:42:42 GMT

Call-ID: 9A7CF310-78111D5-B39FFC41-39B5E64@192.168.0.1

Max-Forwards: 70

CSeq: 101 ACK

Content-Length: 0

-----------------------------------------------------------------------------------------------------

dial-peer voice 100 voip

description *****OUTBOUND********

destination-pattern 00T

translate-outgoing called 55

voice-class codec 12

session protocol sipv2

session target ipv4:10.1.2.3

1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

ISDN to SIP (outbound) calls are failing after too many 183 sess

Hi

You are recieving 183 message with the header "Require: 100rel"

It is expecting the Provisional response PRACK Response back.

Add this in your gateway

voice service voip

sip

  rel1xx supported

Regards,

Senthilkumar

6 REPLIES
Green

ISDN to SIP (outbound) calls are failing after too many 183 sess

Hi,

You calls are fail.ing due this :-

Reason: SIP ;cause=408

Reason: Q.850 ;cause=127 ;text="Interworking, unspecified"

Content-Length: 0

In order that we check your internetworking can you pleae post

show run

Regards

Alex

Regards, Alex. Please rate useful posts.
Community Member

Re: ISDN to SIP (outbound) calls are failing after too many 183

Hi Alex,

I am attaching the sh run, file as requested.

One question, In 183 session messages (require : 100rel) , which some how my gateway not sending 200ok.

why is that?

Or may be you will find answer in sh run.

Thanks in advance.

Green

Re: ISDN to SIP (outbound) calls are failing after too many 183

Hi,

can you first try adding the following to your config:-

!

voice service voip

allow-connections h323 to h323

allow-connections h323 to sip

allow-connections sip to h323

allow-connections sip to sip

sip

  bind control source-interface fast0/0

  bind media source-interface fast0/0

!

can you arrange a retest

regards

Alex

Regards, Alex. Please rate useful posts.
Community Member

ISDN to SIP (outbound) calls are failing after too many 183 sess

hi,

i done the retest, unfortunately result is same Failed with 408 time out, cause 127 after too many 183 sessions

voice service voip

allow-connections h323 to h323

allow-connections h323 to sip

allow-connections sip to h323

allow-connections sip to sip

fax protocol none

h323

sip

  bind control source-interface FastEthernet0/0

  bind media source-interface FastEthernet0/0

!

This gateway was working fine on these settings, but now when i am trying to send calls to my new carrier its failing.

Cisco Employee

ISDN to SIP (outbound) calls are failing after too many 183 sess

Hi

You are recieving 183 message with the header "Require: 100rel"

It is expecting the Provisional response PRACK Response back.

Add this in your gateway

voice service voip

sip

  rel1xx supported

Regards,

Senthilkumar

Community Member

ISDN to SIP (outbound) calls are failing after too many 183 sess

Hi Senthilkumar,

Thank you very much, you have solved my problem.

you are great.

I would like to Thanks Alex aswell, atleast he tried to help me.

Best Regards

Tausiif

1601
Views
0
Helpful
6
Replies
CreatePlease to create content