How to send 183 Progress in IVR

Hi!

I am using Yate with external IVR.
I process call.route message and answer with dumb/.
Then listen to call.execute to get targetid and then attach wave file as
it is written in examples.
Everything works fine but i have to answer call to send media.
Yate doesn't want to send progress message with sdp to provide early media.

I set progress=enable in ysipchan.conf but no luck.

Could you help me with this.

Re: How to send 183 Progress in IVR

Hi,

To send 183 you must use call.progress. Before than you must attach a 
source using chan.attach.

This is how it should look:
        case "call.execute":
            $params = $ev->params;
            $caller = $ev->getValue("caller");
            $partycallid = $ev->GetValue("id");

            $ev->params["targetid"] = $ourcallid;
            $ev->handled = true;
            /* We must ACK this message before dispatching a 
call.progress */
            $ev->Acknowledge();

            $m = new Yate("chan.attach");
            $m->params["source"] = "wave/play/$vm_base/$prompt";
            $m->params["notify"] = $ourcallid;
            $m->Dispatch();

            $m = new Yate("call.progress");
            $m->params["targetid"] = $partycallid;
            $m->params["id"] = $ourcallid;
            $m->params["earlymedia"] = true;
            $m->Dispatch();

            // we already ACKed this message
            $ev = false;

Codec packet size in both ways

route calls differently for registered suers

hi,

what i wanted to know was if there was an account in regfile and the 
phone used that account to register to yate and get authorized then how 
do i set dialplan or lets say configure the routing only for that 
regfile account and not apply it to everyones account globally. 
currently i have added certain ip addresses of other servers sending 
calls to yate so they dont get authorized under [check_addr_auth] and 
that works fine and those calls are routed to their destination using 
the routing defined under the [default] section. what i want to do is 
set routing separately for gateway account, for registered and 
authenticated users. i tried searching but couldnt come across any 
sample or any wiki page, any sample scripting is greately appreciated

Regards,
Bipin

__________ Information from ESET NOD32 Antivirus, version of virus signature database 4485 (20091006) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

Re: route calls differently for registered suers

Hi,

In yate you have 3 routing modules: register, regfile and regexroute. 
Besides that you can make your custom scripts: check route.php in the 
share/scripts directory that catches the message that you need.

You said you want to: "set routing separately for gateway account, for 
registered and authenticated users". If you know the prefixes of the 
numbers that could be called when routing to gateway account then you 
could set them in regexroute and then leave the calls that don't match 
to go to regfile. Just set a lower priority for regfile than regexroute.

If you choose to use the register module you will need to move the 
registering of users in the database also (besides defining the rules). 
You can then define the routing by combining different queries.

Regards,
Monica Tepelus

Bipin wrote:
> hi,
>
> what i wanted to know was if there was an account in regfile and the 
> phone used that account to register to yate and get authorized then 
> how do i set dialplan or lets say configure the routing only for that 
> regfile account and not apply it to everyones account globally. 
> currently i have added certain ip addresses of other servers sending 
> calls to yate so they dont get authorized under [check_addr_auth] and 
> that works fine and those calls are routed to their destination using 
> the routing defined under the [default] section. what i want to do is 
> set routing separately for gateway account, for registered and 
> authenticated users. i tried searching but couldnt come across any 
> sample or any wiki page, any sample scripting is greately appreciated
>
>
> Regards,
> Bipin
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus 
> signature database 4485 (20091006) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com

Re: route calls differently for registered suers

hi,

basically for gateway calls i have configured the ip of the server 
sending calls under trusted gateways and that works like a charm but now 
regarding the users registering to yate directly i want them be able to 
use yate to route their calls to providers or trunks separately. i 
usually dont use prefixes so now the problem is calls coming to yate 
using gateway connections are all dialed using 00 as prefix so calls to 
india would be 0091..... and regexroute catches 0091 and sends call to a 
specific ip or sip account which i use for wholesale traffic but now 
users registering to yate directly, thats all is retail traffic so they 
also dial numbers starting with 00 so if they call india using 
0091...... then i want to route their call to some other gateway or sip 
provider not the route used for those gateway calls

eg:

below works fine
server ------> yate routes to GW1 -------> sip provider(GW1)

below is also what i want to do specially for users registering to yate
client registering to yate ---------> yate routes to GW2 -----------> 
sip provider (GW2)

Regards,
Bipin

-------- Original Message  --------
Subject: Re: [yate] route calls differently for registered suers
From: Monica Tepelus <monica@...>
To: Bipin <bipin@...>
Date: Wednesday, October 07, 2009 1:01:00 PM

> Hi,
> 
> In yate you have 3 routing modules: register, regfile and regexroute. 
> Besides that you can make your custom scripts: check route.php in the 
> share/scripts directory that catches the message that you need.
> 
> You said you want to: "set routing separately for gateway account, for 
> registered and authenticated users". If you know the prefixes of the 
> numbers that could be called when routing to gateway account then you 
> could set them in regexroute and then leave the calls that don't match 
> to go to regfile. Just set a lower priority for regfile than regexroute.
> 
> If you choose to use the register module you will need to move the 
> registering of users in the database also (besides defining the rules). 
> You can then define the routing by combining different queries.
> 
> Regards,
> Monica Tepelus
> 
> Bipin wrote:
>> hi,
>>
>> what i wanted to know was if there was an account in regfile and the 
>> phone used that account to register to yate and get authorized then 
>> how do i set dialplan or lets say configure the routing only for that 
>> regfile account and not apply it to everyones account globally. 
>> currently i have added certain ip addresses of other servers sending 
>> calls to yate so they dont get authorized under [check_addr_auth] and 
>> that works fine and those calls are routed to their destination using 
>> the routing defined under the [default] section. what i want to do is 
>> set routing separately for gateway account, for registered and 
>> authenticated users. i tried searching but couldnt come across any 
>> sample or any wiki page, any sample scripting is greately appreciated
>>
>>
>> Regards,
>> Bipin
>>
>>
>> __________ Information from ESET NOD32 Antivirus, version of virus 
>> signature database 4485 (20091006) __________
>>
>> The message was checked by ESET NOD32 Antivirus.
>>
>> http://www.eset.com
> 
> 
> __________ Information from ESET NOD32 Antivirus, version of virus 
> signature database 4485 (20091006) __________
> 
> The message was checked by ESET NOD32 Antivirus.
> 
> http://www.eset.com
> 
> 
> 
> 

__________ Information from ESET NOD32 Antivirus, version of virus signature database 4485 (20091006) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

Re: route calls differently for registered suers

hi,

there is nothing much in the configuration that i have changed

(GW1 terminates calls to india, GW2 terminates calls to pakistan and the 
rest of the wholesale traffic goes to GW3)
(ip under trusted gateway is just a demo ip)

regwxroute has the following modifications only
[default]
${rtp_forward}possible=;rtp_forward=yes
^0091.*$=sip/sip:\0 <at> GW1
^0092.*$=sip/sip:\0 <at> GW2
^00.*$=sip/sip:\0 <at> GW3
${username}^$=call check_addr_auth

;[check_addr_auth]
${address}^1\.2\.3\.4:=return
.*=-;error=noauth

regfile has only user accounts that clients use to register to yate

Regards,
Bipin

-------- Original Message  --------
Subject: Re: [yate] route calls differently for registered suers
From: Monica Tepelus <monica@...>
To: Bipin <bipin@...>
Date: Wednesday, October 07, 2009 1:31:35 PM

> Please send me the configuration file that you have now.
> 
> Monica Tepelus
> 
> Bipin wrote:
>> hi,
>>
>> basically for gateway calls i have configured the ip of the server 
>> sending calls under trusted gateways and that works like a charm but 
>> now regarding the users registering to yate directly i want them be 
>> able to use yate to route their calls to providers or trunks 
>> separately. i usually dont use prefixes so now the problem is calls 
>> coming to yate using gateway connections are all dialed using 00 as 
>> prefix so calls to india would be 0091..... and regexroute catches 
>> 0091 and sends call to a specific ip or sip account which i use for 
>> wholesale traffic but now users registering to yate directly, thats 
>> all is retail traffic so they also dial numbers starting with 00 so if 
>> they call india using 0091...... then i want to route their call to 
>> some other gateway or sip provider not the route used for those 
>> gateway calls
>>
>> eg:
>>
>> below works fine
>> server ------> yate routes to GW1 -------> sip provider(GW1)
>>
>> below is also what i want to do specially for users registering to yate
>> client registering to yate ---------> yate routes to GW2 -----------> 
>> sip provider (GW2)
>>
>>
>> Regards,
>> Bipin
>>
>>
>>
>> -------- Original Message  --------
>> Subject: Re: [yate] route calls differently for registered suers
>> From: Monica Tepelus <monica@...>
>> To: Bipin <bipin@...>
>> Date: Wednesday, October 07, 2009 1:01:00 PM
>>
>>> Hi,
>>>
>>> In yate you have 3 routing modules: register, regfile and regexroute. 
>>> Besides that you can make your custom scripts: check route.php in the 
>>> share/scripts directory that catches the message that you need.
>>>
>>> You said you want to: "set routing separately for gateway account, 
>>> for registered and authenticated users". If you know the prefixes of 
>>> the numbers that could be called when routing to gateway account then 
>>> you could set them in regexroute and then leave the calls that don't 
>>> match to go to regfile. Just set a lower priority for regfile than 
>>> regexroute.
>>>
>>> If you choose to use the register module you will need to move the 
>>> registering of users in the database also (besides defining the 
>>> rules). You can then define the routing by combining different queries.
>>>
>>> Regards,
>>> Monica Tepelus
>>>
>>> Bipin wrote:
>>>> hi,
>>>>
>>>> what i wanted to know was if there was an account in regfile and the 
>>>> phone used that account to register to yate and get authorized then 
>>>> how do i set dialplan or lets say configure the routing only for 
>>>> that regfile account and not apply it to everyones account globally. 
>>>> currently i have added certain ip addresses of other servers sending 
>>>> calls to yate so they dont get authorized under [check_addr_auth] 
>>>> and that works fine and those calls are routed to their destination 
>>>> using the routing defined under the [default] section. what i want 
>>>> to do is set routing separately for gateway account, for registered 
>>>> and authenticated users. i tried searching but couldnt come across 
>>>> any sample or any wiki page, any sample scripting is greately 
>>>> appreciated
>>>>
>>>>
>>>> Regards,
>>>> Bipin
>>>>
>>>>
>>>> __________ Information from ESET NOD32 Antivirus, version of virus 
>>>> signature database 4485 (20091006) __________
>>>>
>>>> The message was checked by ESET NOD32 Antivirus.
>>>>
>>>> http://www.eset.com
>>>
>>>
>>> __________ Information from ESET NOD32 Antivirus, version of virus 
>>> signature database 4485 (20091006) __________
>>>
>>> The message was checked by ESET NOD32 Antivirus.
>>>
>>> http://www.eset.com
>>>
>>>
>>>
>>>
>>
>>
>> __________ Information from ESET NOD32 Antivirus, version of virus 
>> signature database 4485 (20091006) __________
>>
>> The message was checked by ESET NOD32 Antivirus.
>>
>> http://www.eset.com
> 
> 
> __________ Information from ESET NOD32 Antivirus, version of virus 
> signature database 4486 (20091007) __________
> 
> The message was checked by ESET NOD32 Antivirus.
> 
> http://www.eset.com
> 
> 
> 
> 

__________ Information from ESET NOD32 Antivirus, version of virus signature database 4486 (20091007) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com