[chan-capi-users] Release Cause "Number Changed 22" with New number

[Armin Schindler]

On Fri, 16 Jan 2009, Saeed Ahmed wrote:
> To get it working I can buy recommended cards. But somehow I badly need it
> in working condition.
>
> I could also make a BRI connection with my Switch, because my idea is using
> Asterisk for signaling only, so that every call will hit to asterisk and
> will get some prefix in front and swith will re route it (Do you think BRI
> will be ok to handle couple of hundred calls per seconds?)

I don't think so. Asterisk is channel based, so if a call comes in the 
channel is allocated, even if you don't need it. The deflect will take
a moment and if two channels are 'in use', a third call may already
cause problems. Even with a PRI this may have a limit depending on the
speed of
   SETUP -> REROUTE -> RELEASE

> I hope my switch will support it
> (http://www.iskratel.si/internet/ProductsSolutions/SI2000/)

I cannot tell this, but it depends on which feature you really want to
use. Maybe with PRI you have other possibilities too than just reroute.
QSIG for example may also be a possibility here, but I don't know enough
about this.

> Please recommend me the cards which you think are ok, so that I can start my
> tests.

Most people know that the only hardware I recommend is Dialogic DIVA Server.
I always work with these cards when a good production system is needed. 
Their firmware for a lot of protocols is very good and robust. And the CAPI 
interface has very good support.
If you just need d-channel signaling, then the DIVA Server cards maybe too 
much for you because of their very good b-bchannel features (including the
onboard DSPs).
But first you should know which feature you really need.

Armin


> -----Original Message-----
> From: chan-capi-users-bounces at lists.melware.net
> [mailto:chan-capi-users-bounces at lists.melware.net] On Behalf Of Armin
> Schindler
> Sent: Friday, January 16, 2009 1:48 PM
> To: chan-capi users
> Subject: Re: [chan-capi-users] Release Cause "Number Changed 22" with New
> number
>
> On Fri, 16 Jan 2009, Saeed Ahmed wrote:
>> Hi all,
>>
>> Since long I am searching for a way to return Number changed (22) release
>> cause with new modified number to my TDM switch (SS7/DSS1) which is
>> connected to asterisk on PRI line, but I found no way, asterisk dev also
>> replied with no. Finally someone referred me to chap-capi that its
> possible
>> with it. Could you please guys ensure me if its possible? Here's what I am
>> trying to do:
>>
>> 1  When call comes from  my TDM switch
>>
>> 2  I want to return Number changed release cause (22), additionally with
> new
>> modified number
>>
>> 3  So that my TDM switch can re-route the call according to routing (in
> that
>> case the call could go to some other switch instead of capi asterisk box,
>> based on routing)
>>
>> The similar thing I am able to do in SIP with Transfer() application.
>
> I cannot tell anything about SS7, but when talking about DSS1 it seems this
> is not completely possible.
> First you want to release the call with a special cause code. Looking at
> this only, it will work (if the ISDN card driver supports it, but most CAPI
> drivers do). With chan_capi you can Hangup() with any cause code.
>
> But then you want the call to be rerouted to new number!? Well then the
> first step (release) should not be done. For BRI lines you can use
> call-deflect which is supported by chan_capi. With PtP BRI lines and PRI
> the same chan_capi function triggers call-reroute. But this must be
> supported by the hardware driver as well (and the switch!).
>
> Armin
>
> _______________________________________________
> Chan-capi-users mailing list
> Chan-capi-users at lists.melware.net
> http://lists.melware.net/mailman/listinfo/chan-capi-users
>
> _______________________________________________
> Chan-capi-users mailing list
> Chan-capi-users at lists.melware.net
> http://lists.melware.net/mailman/listinfo/chan-capi-users
>