[SR-Users] rtpengine

[volga629]

Hello Everyone,
What flags available on latest rtpegnine to acomplish transcoding and 
codec manipulation ?


Slava.


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] MSILO: SIP stored offline MESSAGE repetitive delivery

[David Villasmil]

Try and get a trace, so you can see wether the message is ack'd and bump up
kamailio's debug and make it actually sees the ackd

On Sun, Apr 8, 2018, 20:26 M S  wrote:

> Hi,
>
> When kamailio dumps the messages to destination party upon register, do
> you see its reply received by kamailio correctly? Most probable cause of
> the problem is that kamailio does not receives 200 OK for dumped message
> from destination party and assumes message delivery failure, therefore it
> stores the message again. This is all done automatically be msilo module.
>
> Thank you.
>
>
> On Sun, Apr 8, 2018 at 7:42 PM, Abdul Basit  wrote:
>
>> Dear Team,
>>
>> Still stuck with the issue. Kindly suggest where i did wrong.
>>
>>
>> --
>> regards,
>>
>> abdul basit | p: +92 32 1416 4196 | o: +92 30 0841 1445
>>
>> On 6 April 2018 at 20:50, Abdul Basit  wrote:
>>
>>> Hi team,
>>>
>>> I am facing an issue while setting up IM server based on kamailio.
>>> SIP-SIP online messaging is fine. For offline messaging i am using msilo
>>> module which is storing offline messages in 'silo' table.
>>>
>>> As B-party come online ... it receive offline messages stored in
>>> database. But
>>> *Problem is*.. these messages will deliver to B-party as many time it
>>> REGISTER online.
>>>
>>> How can I configure msilo module to mark messages delivery status?
>>> or how can i delete the delivered messages so that there will be no
>>> chance of delivering them again on next REGISTER?
>>>
>>> Message parts of kamailio.cfg are
>>> 
>>> /* add local domain aliases */
>>> alias="192.168.10.18"
>>> port=9060
>>>
>>>
>>> # - msilo params -
>>> modparam("msilo", "db_url", DBURL)
>>> modparam("msilo", "db_table", "silo")
>>> modparam("msilo", "sc_mid", "id")
>>> modparam("msilo","from_address","sip:registrar@192.168.10.18:9060")
>>> modparam("msilo","contact_hdr","Contact: registrar@192.168.10.18:9060
>>> ;msilo=yes\r\n")
>>> modparam("msilo","content_type_hdr","Content-Type: text/plain\r\n")
>>>
>>> 
>>>
>>> route[MSILO_MESSAGE] {
>>> if (!is_method("MESSAGE")) return;
>>> xlogl("L_NOTICE", "[$rm] r-uri: $ru d-uri: $du \n");
>>> if (lookup("location")) {
>>> xlogl("L_NOTICE", "[$rm] -> loaction found. Relying message
>>> [[$rb]] to the UAC \n");
>>> t_relay();
>>> } else {
>>> if (!t_newtran()) {
>>> xlogl("L_ERROR", "[$rm] -> ERROR creating new transaction
>>> \n");
>>> sl_reply_error();
>>> exit;
>>> };
>>> xlogl("L_NOTICE", "[$rm] -> Storing MSILO_MESSAGE \n
>>> [$ru]-[$tu]-[$ou] \n ");
>>> if (m_store("$ru")) {
>>> xlogl("L_NOTICE", "MSILO: offline message stored! \n");
>>> if (!t_reply("202", "Accpeted and Strored")) {
>>> xlogl("L_ERROR", "MSILO: Err sending 202 reply... \n");
>>> sl_reply_error();
>>> }
>>> } else {
>>> xlogl("L_ERROR", "MSILO: offline message NOT stored... \n");
>>> if (!t_reply("503", "Service Unavailable")) {
>>> sl_reply_error();
>>> }
>>> }
>>> }
>>> exit;
>>> }
>>>
>>> .
>>>
>>> # Handle SIP registrations
>>> route[REGISTRAR] {
>>> if (!is_method("REGISTER")) return; // discard all non-REGISTER
>>> methods
>>>
>>> if(isflagset(FLT_NATS)) {
>>> setbflag(FLB_NATB);
>>> #!ifdef WITH_NATSIPPING
>>> setbflag(FLB_NATSIPPING); //# do SIP NAT pinging
>>> #!endif
>>> }
>>> $avp(received) = "sip:" + $si + ":" + $sp + ";transport=" + $proto;
>>> xlogl("L_INFO", "[$rm] -> UAC actual location $avp(received) \n");
>>> if (!save("location",0x04)) {
>>> xlogl("L_ERROR", "[$rm] -> Unable to save user location \n");
>>> sl_reply_error();
>>> }
>>> else {
>>> xlogl("L_INFO", "[$rm] -> dumping messages with MSILO \n");
>>> # MSILO - dumping user's offline messages to user
>>> if (m_dump("$fu")) {
>>> xlogl("L_NOTICE", "MSILO: offline messages for $fu dumped -
>>> if they were \n");
>>> }
>>> else {
>>> xlogl("L_NOTICE", "MSILO: no offline messages dumped \n");
>>> };
>>> }
>>> exit;
>>> }
>>>
>>> Any idea?
>>>
>>> --
>>> regards,
>>>
>>> abdul basit
>>>
>>
>>
>> ___
>> Kamailio (SER) - Users Mailing List
>> sr-users@lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>
>>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] MSILO: SIP stored offline MESSAGE repetitive delivery

[M S]

Hi,

When kamailio dumps the messages to destination party upon register, do you
see its reply received by kamailio correctly? Most probable cause of the
problem is that kamailio does not receives 200 OK for dumped message from
destination party and assumes message delivery failure, therefore it stores
the message again. This is all done automatically be msilo module.

Thank you.


On Sun, Apr 8, 2018 at 7:42 PM, Abdul Basit  wrote:

> Dear Team,
>
> Still stuck with the issue. Kindly suggest where i did wrong.
>
>
> --
> regards,
>
> abdul basit | p: +92 32 1416 4196 | o: +92 30 0841 1445
>
> On 6 April 2018 at 20:50, Abdul Basit  wrote:
>
>> Hi team,
>>
>> I am facing an issue while setting up IM server based on kamailio.
>> SIP-SIP online messaging is fine. For offline messaging i am using msilo
>> module which is storing offline messages in 'silo' table.
>>
>> As B-party come online ... it receive offline messages stored in
>> database. But
>> *Problem is*.. these messages will deliver to B-party as many time it
>> REGISTER online.
>>
>> How can I configure msilo module to mark messages delivery status?
>> or how can i delete the delivered messages so that there will be no
>> chance of delivering them again on next REGISTER?
>>
>> Message parts of kamailio.cfg are
>> 
>> /* add local domain aliases */
>> alias="192.168.10.18"
>> port=9060
>>
>>
>> # - msilo params -
>> modparam("msilo", "db_url", DBURL)
>> modparam("msilo", "db_table", "silo")
>> modparam("msilo", "sc_mid", "id")
>> modparam("msilo","from_address","sip:registrar@192.168.10.18:9060")
>> modparam("msilo","contact_hdr","Contact: registrar@192.168.10.18:9060;m
>> silo=yes\r\n")
>> modparam("msilo","content_type_hdr","Content-Type: text/plain\r\n")
>>
>> 
>>
>> route[MSILO_MESSAGE] {
>> if (!is_method("MESSAGE")) return;
>> xlogl("L_NOTICE", "[$rm] r-uri: $ru d-uri: $du \n");
>> if (lookup("location")) {
>> xlogl("L_NOTICE", "[$rm] -> loaction found. Relying message
>> [[$rb]] to the UAC \n");
>> t_relay();
>> } else {
>> if (!t_newtran()) {
>> xlogl("L_ERROR", "[$rm] -> ERROR creating new transaction
>> \n");
>> sl_reply_error();
>> exit;
>> };
>> xlogl("L_NOTICE", "[$rm] -> Storing MSILO_MESSAGE \n
>> [$ru]-[$tu]-[$ou] \n ");
>> if (m_store("$ru")) {
>> xlogl("L_NOTICE", "MSILO: offline message stored! \n");
>> if (!t_reply("202", "Accpeted and Strored")) {
>> xlogl("L_ERROR", "MSILO: Err sending 202 reply... \n");
>> sl_reply_error();
>> }
>> } else {
>> xlogl("L_ERROR", "MSILO: offline message NOT stored... \n");
>> if (!t_reply("503", "Service Unavailable")) {
>> sl_reply_error();
>> }
>> }
>> }
>> exit;
>> }
>>
>> .
>>
>> # Handle SIP registrations
>> route[REGISTRAR] {
>> if (!is_method("REGISTER")) return; // discard all non-REGISTER
>> methods
>>
>> if(isflagset(FLT_NATS)) {
>> setbflag(FLB_NATB);
>> #!ifdef WITH_NATSIPPING
>> setbflag(FLB_NATSIPPING); //# do SIP NAT pinging
>> #!endif
>> }
>> $avp(received) = "sip:" + $si + ":" + $sp + ";transport=" + $proto;
>> xlogl("L_INFO", "[$rm] -> UAC actual location $avp(received) \n");
>> if (!save("location",0x04)) {
>> xlogl("L_ERROR", "[$rm] -> Unable to save user location \n");
>> sl_reply_error();
>> }
>> else {
>> xlogl("L_INFO", "[$rm] -> dumping messages with MSILO \n");
>> # MSILO - dumping user's offline messages to user
>> if (m_dump("$fu")) {
>> xlogl("L_NOTICE", "MSILO: offline messages for $fu dumped -
>> if they were \n");
>> }
>> else {
>> xlogl("L_NOTICE", "MSILO: no offline messages dumped \n");
>> };
>> }
>> exit;
>> }
>>
>> Any idea?
>>
>> --
>> regards,
>>
>> abdul basit
>>
>
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
>
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] MSILO: SIP stored offline MESSAGE repetitive delivery

[Abdul Basit]

Dear Team,

Still stuck with the issue. Kindly suggest where i did wrong.


--
regards,

abdul basit | p: +92 32 1416 4196 | o: +92 30 0841 1445

On 6 April 2018 at 20:50, Abdul Basit  wrote:

> Hi team,
>
> I am facing an issue while setting up IM server based on kamailio.
> SIP-SIP online messaging is fine. For offline messaging i am using msilo
> module which is storing offline messages in 'silo' table.
>
> As B-party come online ... it receive offline messages stored in database.
> But
> *Problem is*.. these messages will deliver to B-party as many time it
> REGISTER online.
>
> How can I configure msilo module to mark messages delivery status?
> or how can i delete the delivered messages so that there will be no chance
> of delivering them again on next REGISTER?
>
> Message parts of kamailio.cfg are
> 
> /* add local domain aliases */
> alias="192.168.10.18"
> port=9060
>
>
> # - msilo params -
> modparam("msilo", "db_url", DBURL)
> modparam("msilo", "db_table", "silo")
> modparam("msilo", "sc_mid", "id")
> modparam("msilo","from_address","sip:registrar@192.168.10.18:9060")
> modparam("msilo","contact_hdr","Contact: registrar@192.168.10.18:9060;m
> silo=yes\r\n")
> modparam("msilo","content_type_hdr","Content-Type: text/plain\r\n")
>
> 
>
> route[MSILO_MESSAGE] {
> if (!is_method("MESSAGE")) return;
> xlogl("L_NOTICE", "[$rm] r-uri: $ru d-uri: $du \n");
> if (lookup("location")) {
> xlogl("L_NOTICE", "[$rm] -> loaction found. Relying message
> [[$rb]] to the UAC \n");
> t_relay();
> } else {
> if (!t_newtran()) {
> xlogl("L_ERROR", "[$rm] -> ERROR creating new transaction \n");
> sl_reply_error();
> exit;
> };
> xlogl("L_NOTICE", "[$rm] -> Storing MSILO_MESSAGE \n
> [$ru]-[$tu]-[$ou] \n ");
> if (m_store("$ru")) {
> xlogl("L_NOTICE", "MSILO: offline message stored! \n");
> if (!t_reply("202", "Accpeted and Strored")) {
> xlogl("L_ERROR", "MSILO: Err sending 202 reply... \n");
> sl_reply_error();
> }
> } else {
> xlogl("L_ERROR", "MSILO: offline message NOT stored... \n");
> if (!t_reply("503", "Service Unavailable")) {
> sl_reply_error();
> }
> }
> }
> exit;
> }
>
> .
>
> # Handle SIP registrations
> route[REGISTRAR] {
> if (!is_method("REGISTER")) return; // discard all non-REGISTER methods
>
> if(isflagset(FLT_NATS)) {
> setbflag(FLB_NATB);
> #!ifdef WITH_NATSIPPING
> setbflag(FLB_NATSIPPING); //# do SIP NAT pinging
> #!endif
> }
> $avp(received) = "sip:" + $si + ":" + $sp + ";transport=" + $proto;
> xlogl("L_INFO", "[$rm] -> UAC actual location $avp(received) \n");
> if (!save("location",0x04)) {
> xlogl("L_ERROR", "[$rm] -> Unable to save user location \n");
> sl_reply_error();
> }
> else {
> xlogl("L_INFO", "[$rm] -> dumping messages with MSILO \n");
> # MSILO - dumping user's offline messages to user
> if (m_dump("$fu")) {
> xlogl("L_NOTICE", "MSILO: offline messages for $fu dumped - if
> they were \n");
> }
> else {
> xlogl("L_NOTICE", "MSILO: no offline messages dumped \n");
> };
> }
> exit;
> }
>
> Any idea?
>
> --
> regards,
>
> abdul basit
>
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Kamailio ​ds_ping_interval Performance

[Atul Thosar]

Thanks all for your responses.


I am new to Kamailio, so appreciate if some one can help me with sample
code where kamailio routes call to another FreeSWITCH server if 1st
FreeSWITCH server does not respond in some time, say 3 sec. Btw I have a
query on this approach. Consider a following scenario -

0. kamailio is configured w/ 2 FreeSWITCH servers in dispatcher and with
configuration where on not receiving response to INVITE in 3 sec, kamailio
will forward the call to another FreeSWITCH server.
1. kamailio receives INVITE and forwards INVITE to FreeSWITCH #1
2. FreeSWITCH #1 receives INVITE, but 100 trying response could not reach
to kamailio bec of network break, say for 4 sec.
3. So After 3 sec, since kamailio does not receive any response from
FreeSWITCH #1, it forwards INVITE to FreeSWITCH #2
4. FreeSWITCH #2 responds with 200 OK and kamailio receives it.
5. After 4 sec, when network recovers, FreeSWITCH #1 sends 200 OK to
kamailio. How kamailio would behave here? Will it drops the call w/
FreeSWITCH #1?


--
​Thanks,
Atul Thosar



On 7 April 2018 at 21:46, Julien Chavanton  wrote:

> Hi,
>
> I would set it to a low value to make sure you avoid sending calls a
> Freeswitch server facing problems, in the case of Freeswitch the same GW
> will also handle media, if it is having hardtime repliyng to SIP OPTIONS it
> will very likely have problem handling the media.
>
> It may also get worst during the call even stop responsding and loose
> transaction in progress or in dialog transactions later like session timers
> and BYEs.
>
> Off loading it may able help other calls already using it.
>
>
> You may push your strategy further thinking about :
>
> - The risk is that you run out of GW, could be handled when ds_select is
> returning nothing.
> - Another side effect, would be that you are sending more traffic to other
> GW, they must be able to handle the extra load.
>
> In kamailio 5 there is a new algorithm that behaves better when one GW is
> put out of service.
>
> “11” - use relative weight based load distribution. You have to set the
> attribute 'rweight' per each address in destination set. Active host usage
> probability is rweight/(SUM of all active host rweights in destination
> group).
>
> Regards
> Julien
>
> On Mon, Apr 2, 2018 at 6:06 PM, Atul Thosar  wrote:
>
>> Hi All,
>> I am using Kamailio
>> ​*​*
>> *v4.4.x* to load balanced traffic to FreeSWITCH servers. I have query
>> regarding ds_ping_interval and ds_probing_threshold. We have very high
>> traffic (around 200-400
>> ​ (CPS)​
>> calls per sec) hitting on Kamailio which then distribute it to 2-3
>> FreeSWITCH servers.
>> ​ ​
>> What is the optimal value should I set to ds_ping_interval and
>> ds_probing_threshold?
>>
>> If I set
>> ​​
>> ds_ping_interval=2 and
>> ​​
>> ds_probing_threshold=1 then in every 2 sec, I would come to know if my
>> ​​
>> FreeSWITCH server is down/up. But by setting such low values, I afraid
>> there would
>> ​be ​
>> lot of SIP traffic on network.
>> ​ If I set high (say
>> ​
>> ds_probing_threshold=5) then I may loose high number of calls (200 CPS, I
>> will loose 1000 calls) in case
>> ​
>> FreeSWITCH server is down. ​
>>
>>
>> As I said earlier we have very high traffic hitting on Kamailio, can't
>> kamailio use INVITE itself to probe FreeSWITCH server is down/up? In case
>> of low traffic can't it switch over to OPTION mechanism?
>>
>> --
>> ​Thanks in Advance​
>> ,
>> ​​
>> Atul
>> ​​
>> ​​
>> ​​
>>
>>
>>
>> ___
>> Kamailio (SER) - Users Mailing List
>> sr-users@lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>
>>
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
>
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users