What is the new location for HKLM\SOFTWARE\Microsoft\RAT\Stingray\Debug\SIP\DIALOG_IDLE_TIMEOUT

Answered What is the new location for HKLM\SOFTWARE\Microsoft\RAT\Stingray\Debug\SIP\DIALOG_IDLE_TIMEOUT

  • Wednesday, July 13, 2011 1:01 PM
     
     

    I have found a technet article http://technet.microsoft.com/en-us/library/dd440976.aspx discussing HKLM\Software\Microsoft\RAT\Stingray\Debug\SIP\DIALOG_IDLE_TIMEOUT and a forum post or two.  However, my TMG 2010 systgem does not have this registry key.  It does not have even have HKLM\Software\Microsoft\RAT.

    I would really like to change that number so that PERHAPS my VoIP calls would not drop after 20 minutes.


    Thanks Roy

All Replies

  • Monday, July 18, 2011 5:43 AM
    Moderator
     
     Answered

    Hi,

     

    Thank you for the post.

     

    You have to create the registry path and value.

     

    Regards,


    Nick Gu - MSFT
  • Monday, July 18, 2011 3:23 PM
     
     

    Yes, creating the full key path worked.  Too bad the article did not say ADD the key/value.  Instead it said change the value.

    ALSO, as a bonus, it actually works.  I have a VoIP call that has lasted more then the default 20 (not 15 noted in the article) for the first time.  YEAH!!!


    Thanks Roy
  • Monday, January 23, 2012 8:15 PM
     
     

    Hi,

    I need to do the exact same thing as Roy did but I can't figure out what type of value I should use. I assume that DIALOG_IDLE_TIMEOUT is a registry value - no? So which type? If it is a key, am I supposed to put the new value in the (Default) for the key?

    Anyone know if MS explained this behaviour?

    /Jan

  • Monday, January 23, 2012 10:32 PM
     
     

    Create the VAULE DIALOG_IDLE_TIMEOUT under this key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\RAT\Stingray\Debug\SIP

    You will have to create part or all of the key path.

    The VALUE shoudl be a DWORD.

    I gave mine the value of 0x70000000 and all has been fine.


    Thanks Roy
  • Tuesday, January 24, 2012 4:52 PM
     
     

    Hi!

    Thanks Roy for the prompt reply. I tried setting value DIALOG_IDLE_TIMEOUT as a string yesterday but that didn't work out. I'll try the DWORD instead. Just to confirm, your value of 0x70000000 would equal to +500 hours IDLE timeout, correct? And all has been working with such a high timeout?

    Thanks again!

    /Jan

  • Tuesday, January 24, 2012 9:46 PM
     
     

    Yes, that is what I have and have had since July.

    I only have 1 user system with a softphone, but the softphone does connect to two different providers.  I cannot tell any adverse effects on either provider based on that value.  Before I put it in, my calls would terminate at 20 minutes +/- 5 seconds.  I can talk for hours now.


    Thanks Roy
  • Wednesday, January 25, 2012 1:29 PM
     
     

    Hi,

    Thanks for the clarification. It seems that the inbound calls we have still are breaking around the 20 minute mark. I am attaching a screenshot of my registery config. My setting with DWORD 3600000 (decimal) should equal 60 minutes, right? But it doesn't seem to take effect. I rebooted the system after I added this value.

    We are currently running TMG version 7.0.8108.200.

    I still also would like to know WHY this is the (intended?) behaviour, if someone knows. Solving the problem is more important right now though.

    /Jan

  • Thursday, January 26, 2012 10:37 AM
     
     

    I do not know why things work as they do out of the box.  A 20 min call limit sounds really silly and the fact that we have to put a value under something called Debug to change it is just plain strange.

    Anyway, my calls will go as long as I want for both inbound and outbound.  I am currently on version 7.0.9193.500.  I know I have added at least one rollup after applying the value, so I do not know how low of a level this works.


    Thanks Roy