Difference between revisions of "Call hangs after 30 seconds"

From Kolmisoft Wiki
Jump to navigationJump to search
Line 14: Line 14:
  [Aug  6 11:50:43] NOTICE[22403]: chan_sip.c:2927 auto_congest: Auto-congesting SIP/prov253-0a1966d0
  [Aug  6 11:50:43] NOTICE[22403]: chan_sip.c:2927 auto_congest: Auto-congesting SIP/prov253-0a1966d0
  -- SIP/prov253-0a1966d0 is circuit-busy  
  -- SIP/prov253-0a1966d0 is circuit-busy  
  Scheduling destruction of SIP dialog '0ceffd014862f2c043209aa56d4930f4@82.194.82.123' in 32000 ms (Method: INVITE)
  Scheduling destruction of SIP dialog '0ceffd014862f2c043209aa56d4930f4@82.194.82.123' in '''32000 ms''' (Method: INVITE)


Clearly points that there is no response from dialed server, so timeout occurred.
Clearly points that there is no response from dialed server, so timeout occurred.

Revision as of 07:56, 13 August 2009

  • Check timeout - maybe call can't last more then 30s?
  • Write down all IPs of all devices which participate in the session
  • Enable sip debug and look for BYE packet, who is sending it.
  • If there is no BYE packet - big chance that problem is in the network - e.g. BYE packet does not reach our end or other end has problems with SIP protocol implementation
    • Check IP in SIP debug and compare to real IPs
    • If it is possible - try to capture SIP debug at the other end and compare to SIP debug in MOR





Such lines: 

[Aug  6 11:50:43] NOTICE[22403]: chan_sip.c:2927 auto_congest: Auto-congesting SIP/prov253-0a1966d0
-- SIP/prov253-0a1966d0 is circuit-busy 
Scheduling destruction of SIP dialog '0ceffd014862f2c043209aa56d4930f4@82.194.82.123' in 32000 ms (Method: INVITE)

Clearly points that there is no response from dialed server, so timeout occurred.

Possible solutions:

  • Check IP/port settings in configuration
  • Check network settings (bad routing/bad settings/etc)
  • Change device at the other end
Retrieved from "https://wiki.kolmisoft.com/index.php?title=Call_hangs_after_30_seconds&oldid=4398"