[ previous ] [ next ] [ threads ]
 To :  yate@v...
 From :  Gamaliel Bedolla <gbf@t...>
 Subject :  Re: [yate] ISUP question
 Date :  Fri, 3 Feb 2012 11:57:09 -0700
Hi all,

Just closing up this thread. I found this post of Paul:

> > -----Original Message-----
> > From: Paul Chitescu [mailto:paulc@v...]
> > Sent: Monday, December 14, 2009 12:47
> > To: yate@v...
> > Subject: Re: [yate] SS7 + Sangoma A108E
> >
> > Hi!
> >
> > You can change the parameters of IAM by altering the call.execute message
> > parameters like:
> > sig.ForwardCallIndicators=international,isdn-orig
> >
> > You can do that by altering the call.preroute or call.route message since
> > the
> > same message gets renamed and redispatched.
> >
> > Note that any existing Forward Call Indicators computed from other
> message
> > parameters will be overwritten so make sure to set everything you need.
> >
> > To change the ACM you will need little more tweaking of same message:
> > message-oprefix=osig
> > osig.BackwardCallIndicators=interworking,isdn-end
> >
> > The ST (stop sending) is encoded in Yate as a period '.' so just add a
> > period
> > at the end of the number.

I configured the ST and I received the ACM at the time expected.

Regards.


2012/2/2 Gamaliel Bedolla 

> Let me test this, and will let you know if it works.
> Thanks a lot Jice!
>
> 2012/2/2 
>
> I was asking the question because I am concerned this behaviour may cause
>> interconnect tests with peer to fail.
>> It is possible to change INN and CgPN screening indicator in
>> regexroute.conf:
>>
>> .* = ; inn=true ; callerscreening=user-provided-**passed
>>
>> before sending the call to the ISUP trunk
>>
>> Jice
>>
>>
>>
>> On Thu, 2 Feb 2012 12:30:03 -0700, Gamaliel Bedolla wrote:
>>
>>> Hi Jice
>>>
>>> Thanks for your answer. I'm trying to replace another SS7 controller
>>> with YATE, and everything works OK, except for domestic calls. When
>>> the other SS7 controller sends IAM, the provider sends ACM in near 3
>>> or 4 seconds, but when YATE sends IAM, it takes near 15 seconds to
>>> receive ACM. I check diferences between YATE's IAM and the another
>>> controller, and there only 3 differences, one of them is the USI, that
>>> is not sent on the other controller, but YATE does.
>>> The other differences are:
>>> INN denied in YATE.
>>> Screening Indicator--Value 3 in YATE, Value 1 in the other controller.
>>> Do you ask this question because the same behavior?
>>> Thanks again.
>>> Gamaliel
>>>
>>
>>
>



Hi all,

Just closing up this thread. I found this post of Paul:

> > -----Original Message-----
> > From: Paul Chitescu [mailto:paulc@v.....]
> > Sent: Monday, December 14, 2009 12:47
> > To: yate@v...
> > Subject: Re: [yate] SS7 + Sangoma A108E
> >
> > Hi!
> >
> > You can change the parameters of IAM by altering the call.execute message
> > parameters like:
> > sig.ForwardCallIndicators=international,isdn-orig
> >
> > You can do that by altering the call.preroute or call.route message since
> > the
> > same message gets renamed and redispatched.
> >
> > Note that any existing Forward Call Indicators computed from other
> message
> > parameters will be overwritten so make sure to set everything you need.
> >
> > To change the ACM you will need little more tweaking of same message:
> > message-oprefix=osig
> > osig.BackwardCallIndicators=interworking,isdn-end
> >
> > The ST (stop sending) is encoded in Yate as a period '.' so just add a
> > period
> > at the end of the number.
I configured the ST and I received the ACM at the time expected.
Regards.

2012/2/2 Gamaliel Bedolla <gbf@t...>
Let me test this, and will let you know if it works.
Thanks a lot Jice!

2012/2/2 <jice@i...>

I was asking the question because I am concerned this behaviour may cause interconnect tests with peer to fail.
It is possible to change INN and CgPN screening indicator in regexroute.conf:

.* = ; inn=true ; callerscreening=user-provided-passed

before sending the call to the ISUP trunk

Jice



On Thu, 2 Feb 2012 12:30:03 -0700, Gamaliel Bedolla wrote:
Hi Jice

Thanks for your answer. I'm trying to replace another SS7 controller
with YATE, and everything works OK, except for domestic calls. When
the other SS7 controller sends IAM, the provider sends ACM in near 3
or 4 seconds, but when YATE sends IAM, it takes near 15 seconds to
receive ACM. I check diferences between YATE's IAM and the another
controller, and there only 3 differences, one of them is the USI, that
is not sent on the other controller, but YATE does.
The other differences are:
INN denied in YATE.
Screening Indicator--Value 3 in YATE, Value 1 in the other controller.
Do you ask this question because the same behavior?
Thanks again.
Gamaliel