Hello,

if the timeout is sent back by kamailio, then it tried to forward the request but the next hop didn't reply. The next hop may be over capacity or, if the next hop is not responding fast, be sure you have adequate values for tm timeout parameters.

Hi,

 

Yeah we get calls time out please see the below

 

SIP messages for Call-ID bdc7441b322047868e294188984bbd09

 

15:46:49.599 [+0.00ms] [TX] INVITE to 192.168.3.204:5060

INVITE sip:12345@192.168.3.204:5060 SIP/2.0

Via: SIP/2.0/UDP 192.168.1.79:5070;rport;branch=z9hG4bKPj27345a1420fb41f89b76cce55b29282b

Max-Forwards: 70

From: sip:55123@192.168.3.204;tag=d8efe9d097c442478ede1f148cb2271d

To: sip:12345@192.168.3.204

Contact: <sip:55123@192.168.1.79:5070>

Call-ID: bdc7441b322047868e294188984bbd09

CSeq: 5624 INVITE

Allow: INFO, PRACK, SUBSCRIBE, NOTIFY, REFER, INVITE, ACK, BYE, CANCEL, UPDATE

Supported: 100rel, timer

User-Agent: StarTrinity.SIP 2016-07-13 16.10 UTC

Session-Expires: 3600;refresher=uac

Content-Type: application/sdp

Content-Length:   329

 

v=0

o=- 3680351217 3680351217 IN IP4 192.168.1.79

s=o14160.proxy.stream0

c=IN IP4 192.168.1.79

t=0 0

m=audio 16114 RTP/AVP 8 0 4 18 101

a=rtcp:16115 IN IP4 192.168.1.79

a=rtpmap:8 PCMA/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:4 G723/8000

a=rtpmap:18 G729/8000

a=sendrecv

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

 

============================================================end of message=================

15:46:49.604 [+5.11ms] [RX] trying -- your call is important to us from 192.168.3.204:5060

SIP/2.0 100 trying -- your call is important to us

Via: SIP/2.0/UDP 192.168.1.79:5070;rport=5070;branch=z9hG4bKPj27345a1420fb41f89b76cce55b29282b;received=192.168.1.79

From: sip:55123@192.168.3.204;tag=d8efe9d097c442478ede1f148cb2271d

To: sip:12345@192.168.3.204

Call-ID: bdc7441b322047868e294188984bbd09

CSeq: 5624 INVITE

Content-Length: 0

 

 

============================================================end of message=================

15:46:51.554 [+1,955.27ms] [RX] Request Timeout from 192.168.3.204:5060

SIP/2.0 408 Request Timeout

Via: SIP/2.0/UDP 192.168.1.79:5070;rport=5070;branch=z9hG4bKPj27345a1420fb41f89b76cce55b29282b;received=192.168.1.79

From: sip:55123@192.168.3.204;tag=d8efe9d097c442478ede1f148cb2271d

To: sip:12345@192.168.3.204;tag=604fc74b9f0d3ee4c15ae560ab8f892f-8007

Call-ID: bdc7441b322047868e294188984bbd09

CSeq: 5624 INVITE

Content-Length: 0

 

 

============================================================end of message=================

15:46:51.554 [+1,955.29ms] [TX] ACK to 192.168.3.204:5060

ACK sip:12345@192.168.3.204:5060 SIP/2.0

Via: SIP/2.0/UDP 192.168.1.79:5070;rport;branch=z9hG4bKPj27345a1420fb41f89b76cce55b29282b

Max-Forwards: 70

From: sip:55123@192.168.3.204;tag=d8efe9d097c442478ede1f148cb2271d

To: sip:12345@192.168.3.204;tag=604fc74b9f0d3ee4c15ae560ab8f892f-8007

Call-ID: bdc7441b322047868e294188984bbd09

CSeq: 5624 ACK

Content-Length:  0

 

 

-- 
Daniel-Constantin Mierla
http://www.asipto.com - http://www.kamailio.org
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda