Hello,
I find that when 2 extensions are connected, and one of the extensions
hangs up on the call, the other will receive a busy signal (as if to
indicate that the call is over).
Does this sound like a config problem, or is it the default behavior of
*?
Example:
[ext-testing]
exten => 111,1,Dial(SIP/2001)
exten => 111,2,Hangup
exten => h,1,Hangup
Zap/2 dials 111:
-- Starting simple switch on 'Zap/2-1'
-- Executing Dial("Zap/2-1", "SIP/2001") in new stack
-- Called 2001
-- SIP/2001-b164 is ringing
-- SIP/2001-b164 answered Zap/2-1
After SIP/2001 hangs up:
-- Executing Hangup("Zap/2-1", "") in new stack
-- Hungup 'Zap/2-1'
... followed by Zap/2 getting a "beep-beep-beep-..." 'busy
tone'.
If this is the default behavior, can it be changed? After the remote
end hangs-up on a call, I'd expect to hear either dialtone or silence.
Thanks
Ryan
As you see, * generates no busy tone, it hangs up the channel. It's your client which generates the tone. This is not something to be done from *. Regards, Doichin Dokov Ryan Courtnage wrote:> Hello, > > I find that when 2 extensions are connected, and one of the extensions > hangs up on the call, the other will receive a busy signal (as if to > indicate that the call is over). > > Does this sound like a config problem, or is it the default behavior > of *? > > Example: > > [ext-testing] > exten => 111,1,Dial(SIP/2001) > exten => 111,2,Hangup > exten => h,1,Hangup > > Zap/2 dials 111: > -- Starting simple switch on 'Zap/2-1' > -- Executing Dial("Zap/2-1", "SIP/2001") in new stack > -- Called 2001 > -- SIP/2001-b164 is ringing > -- SIP/2001-b164 answered Zap/2-1 > > After SIP/2001 hangs up: > -- Executing Hangup("Zap/2-1", "") in new stack > -- Hungup 'Zap/2-1' > > ... followed by Zap/2 getting a "beep-beep-beep-..." 'busy tone'. > > If this is the default behavior, can it be changed? After the remote > end hangs-up on a call, I'd expect to hear either dialtone or silence. > > Thanks > Ryan > > _______________________________________________ > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users
Normal behavior I think. If you don't hang up your regular phone after the other party has dropped you'll get the busy signal after a few seconds too. I've seen this in hardware phones but not in software phones. I guess you have to be told to put the receiver back? Mark On Mon, 29 Mar 2004 15:20:04 -0700, Ryan Courtnage wrote:> > Hello, > > I find that when 2 extensions are connected, and oneof> the extensions > hangs up on the call, the other will receive a busy > signal (as if to > indicate that the call is over). > > Does this sound like a config problem, or is it the > default behavior of > *? > > Example: > > [ext-testing] > exten => 111,1,Dial(SIP/2001) > exten => 111,2,Hangup > exten => h,1,Hangup > > Zap/2 dials 111: > -- Starting simple switch on 'Zap/2-1' > -- Executing Dial("Zap/2-1", "SIP/2001") in new > stack > -- Called 2001 > -- SIP/2001-b164 is ringing > -- SIP/2001-b164 answered Zap/2-1 > > After SIP/2001 hangs up: > -- Executing Hangup("Zap/2-1", "") in new stack > -- Hungup 'Zap/2-1' > > ... followed by Zap/2 getting a "beep-beep-beep-..." > 'busy tone'. > > If this is the default behavior, can it be changed? > After the remote > end hangs-up on a call, I'd expect to hear either > dialtone or silence. > > Thanks > Ryan > > _______________________________________________ > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com >http://lists.digium.com/mailman/listinfo/asterisk-users> To UNSUBSCRIBE or update options visit: > >http://lists.digium.com/mailman/listinfo/asterisk-users