Question On Ring Count On Incoming Circuits
Who controls how many times an incoming call from an external (DID)
provider will ring before Asterisk picks up the call and handles it internally–the provider or Asterisk? If it’s the DID provider, I’ll work on that with them; if it’s Asterisk, I didn’t find anything anywhere that looks like it has anything to do with incoming ring count unless you set up a ring-no-answer system. For my purposes, that would mean defining a dummy extension that has no hardware attached to it that would fail over to my current call handling code after it rings once. Is this the proper method for handling this?
You might wonder why I wouldn’t want a call to a system that simply plays a message and then takes an optional voicemail message to pick up immediately. Short answer: Don’t ask (groan). It’s what the project supporter wants, presumably so that the person calling into the system will know their call went through and to be ready to hear the outgoing message, I don’t know, it’s a customer request so I feel duty-bound to figure it out and implement it.
—
3 thoughts on - Question On Ring Count On Incoming Circuits
Asterisk and this is defined with your timeout on the dial command, mine is 26 seconds so around 5 rings.
Doug
—
Just as you said at the top of this reply, no audio of any kind gets passed, so all the Wait(6) did was provide six seconds of dead-air silence before the outgoing message played. Oh well. Customers can’t have everything. 😉
—
Well, yes, that’s what you wanted, right? Or maybe I misunderstood. If you want people to hear *something* but not have it answer immediately, for those 6 seconds, amend that to:
exten => s,1,Progress()
same => n,Playback(foobar,noanswer)
same => n,Answer()
same => n,DoSomething()
For example, this is common for playing an outgoing message or voicemail greeting, without supervising immediately, so if the caller hangs up before leaving a message, s/he is not charged for the call. Are you trying to do something like that?
—