[asterisk-dev] How to reject calls

[Hans Petter Selasky]

On Tuesday 03 October 2006 11:05, Christian wrote:
> >Yes, but how can you distinguish the two. On a ISDN bus, in point to
> >multipoint, all connected units will start ringing when there is an
> > incoming call, for example. If the one phone sends a RELEASE_COMPLETE
> > message to the NT, then the NT knows that the phone does not want the
> > call, but the other phones are still ringing, and the user that is
> > calling does still hear the ringing signal.
>
> this RELEASE_COMPLETE should not create a AST_CONTROL_HANGUP on the
> A-Leg (incoming call) (B-Legs are the ISDN Phones Ringing).
>

Right.

> >But if you send a RELEASE_COMPLETE, with cause equal to
> >Reject,
> >
> >m(CAUSE_Q850_CALLREJ      ,=0x15, "call rejected")\
> >
> >then all phones will stop ringing, and the calling party will also get a
> >rejected message.
>
> Exactly this RELEASE_COMPLETE should create a AST_CONTROL_HANGUP with
> cause 0x15 on the A-Leg

Yes, but what about the opposite way.

> So for what situation do you need the AST_CONTROL_REJECT Frame else for?

Say you have a list of unwanted incoming numbers, that you want to block from 
your ISDN bus. How can you do that with Asterisk, unless you implement 
AST_CONTROL_REJECT as a response to incoming calls. Currently you can only 
"Hangup" incoming calls, but like that is implemented in "chan_capi", it does 
not "Reject" the call. So I am just saying: Why is there no 
"AST_CONTROL_REJECT". Maybe implementing this needs a counterpart in the 
dialplan: "exten => ...., Reject". And to be backwards compatible, will 
fallback to "Hangup" if not implemented by the channel driver.

--HPS



>
> Christian
>
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
>
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev