GotSpeech.NET

The online community for Microsoft Speech Server developers
Welcome to GotSpeech.NET Sign in | Join | Help
in Search
Computer-Talk

Determining no answer on an outbound app

Last post 09-16-2008, 11:24 AM by msclaricode. 10 replies.
Sort Posts: Previous Next
  •  08-13-2008, 2:55 PM 6684

    Determining no answer on an outbound app

    Hi -

    I'm trying to figure out how to determine when a call has not been answered.  Currently, the gateway just lets the call ring and ring and ring, there is no cutoff, and I am not finding anything obvious as a gateway setting for this.  I'm using the DMG1008LSW (analog) for a gateway.  Is this a gateway setting somewhere, or do I need to set a time limit somewhere in my speech app?

    Thanks.

  •  08-13-2008, 3:29 PM 6685 in reply to 6684

    Re: Determining no answer on an outbound app

    Bring up the dialogic administration web page and click on VoIP, General in the Configuration section.  Change the “TCP Inactivity Timer” section to the desired number of seconds.  Each ring is equivalent to about 6 seconds.  I believe that will do it.

  •  08-14-2008, 8:53 AM 6699 in reply to 6685

    Re: Determining no answer on an outbound app

    I don't have a VoIP tab on my administration website, I would guess because I'm using an analog gateway, as I do have an analog tab.  I did find that I'm not patient enough, that it does detect a no answer after about a 1.5-2 minutes.  It's a lot of ringing, and shortening that would be helpful I think.  Any more ideas?

    Catie

  •  08-14-2008, 9:12 AM 6700 in reply to 6699

    Re: Determining no answer on an outbound app

    Are you running the latest 6.0 version?  It ships configured with a previous software version.  You can download from the Dialogic web site.

    Do you have an outbound call connect timeout under a configuration section?  I believe Marshall Harrison has an analog Dialogic gateway.

  •  08-14-2008, 10:03 AM 6703 in reply to 6700

    Re: Determining no answer on an outbound app

    I'm not running 6.0 yet.  I do have an outbound call connect timeout, and have played around with that, but making it shorter means the gateway determines the call has connected after that period of time, and tells me the call has completed successfully, instead of me getting a telephony fault.

  •  08-14-2008, 1:10 PM 6706 in reply to 6703

    Re: Determining no answer on an outbound app

    Maybe using the System.Threading.Timer can solve your problems if you start it at the beginning of the workflow and if a certain outcome is not met withing the specified interval, then disconnect the call. I don't know how well it can work because I have never tried it in WF.

  •  08-15-2008, 10:10 AM 6716 in reply to 6706

    Re: Determining no answer on an outbound app

    You should hae a VOIP link on there someplace. I also suggest you follow Martial's advice and upgrade the firmware. It's really easy and the new interface is worth it.

    Here are the settings I have on my Dialogic Gateway. Check the ones that I have bolded.

    TDM Analog Settings
    Timing
    Flash Hook (ms)
    Wait for Dial Tone after Flash Hook YesNo
    Delay After Flash-Hook (ms)
    Loop Current Off Debounce (ms)
    Incoming Rings Before Answer
    Ringing Timeout (ms)
    Feature Code
    Consult Call Dialtone Drop Code
    Consult Call Proceeding Drop Code
    Consult Call Busy Drop Code
    Consult Call Error Drop Code
    Consult Call Connected Drop Code
    Consult Call Disconnected Drop Code
    Message Waiting Control
    MWI Confirmation Tone YesNo
    Use Same Port for Mwi Clear/Set YesNo
    CPID Settings
    Analog Interface Type PBXCentral Office
    Central Office CID Type NoneBellcore FSKDTMF
    Central Office CID Alert Type Pause in Ring CycleRing BurstPolarity Reversal
    FSK CID expiration
    FSK CID timeout
    Auto-Answer Inbound TDM Calls (Type II CPID) YesNo
    Initial Wait for Inband CPID (ms)
    Inband CPID Complete Timeout (ms)


    Marshall Harrison
    Microsoft MVP, Office Communications Server


    www.GoldSys.com
    W: 303.447.2774
    H: 904.342-6205

    the gotspeech guy
  •  08-18-2008, 1:47 PM 6735 in reply to 6716

    Re: Determining no answer on an outbound app

    I just upgraded to the 6.0 firmware and have the VoIP tab now.  Since upgrading, I just tested out dialing again, and am seeing VOIP: Not Accepted as a fail reason.  Previously I was seeing TDM fail reasons.  I'm not set up for VoIP and don't know why I'm now attempting to use it.  I uploaded all the *,ini files by accident, would that have anything to do with this?

    Marshell - thank you for your config information, my Analog Interface Type is PBX at the moment, since I'm interfacing with a PBX.  I couldn't tell if you were pointing me to actual configuration settings, or having me check them, as your setup includes all drop down information.

    Catie

  •  08-18-2008, 2:23 PM 6736 in reply to 6735

    Re: Determining no answer on an outbound app

    I got calling working again for my gateway, I needed to add another Inbound VoIP Rule for calls and it works again (whew!).  I did looka t the VoIP tab to see what my timeouts are for tcp inactivity timer (and tls inactivity timer) and they are both at 30 secs at the moment, though it takes 2 minutes to time out.
  •  08-21-2008, 8:45 AM 6753 in reply to 6736

    Re: Determining no answer on an outbound app

    Under Config, VOIP, General, what do you have the invite expiration set to?
  •  09-16-2008, 11:24 AM 7084 in reply to 6753

    Re: Determining no answer on an outbound app

    And now back to this one after a long break.  My invite expiration was set to 120 secs. I changed it to 36 secs, and that fixed my problem.  Thank you all very much!

    Catie

View as RSS news feed in XML