[OpenSIPS-Users] CSeq and automatic call termination issue
Hi all,
In my testing environment, there are one SIP outbound proxy and one SIP
server. The message flow of call setup is like caller->SIP outbound
proxy->SIP server->SIP outbound proxy->callee. When the SIP outbound proxy
receives an INVITE request from the SIP server, it calls create_dialog("B").
The automatic call termination timer is set to 30 minutes
(modparam("dialog", "default_timeout", 1800)). This feature works well when
no REFER/PRACK requests are sent during a dialog. If some REFER/PRACK are
sent in the same dialog (CSeq increase), the BYE sent from SIP outbound
proxy will be *reject by the client due to 500 (lower Cseq)*. I call
match_dialog() in the SIP outbound proxy/SIP server when receiving
REFER/PRACK. Can someone share how to address this issue? Any comment is
greatly appreciated.
Best regards,
Chen-Che
--
View this message in context:
http://opensips-open-sip-server.1449251.n2.nabble.com/CSeq-and-automatic-call-termination-issue-tp7595684.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Planning OpenSIPS 2.1 release - heads up
Bogdan, I am running 2.1.x and so far great, I had issue with sipteace with homer which I already reported. So please look into it before release. -- Sent from my iPhone > On Mar 8, 2015, at 7:02 PM, Terrance Devor wrote: > > Good news, > > What is rtpengine support. Will the proxy manage RTP directly? Or will > we still have to use RTP/Media Proxy > > > Terrance > > ___ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Planning OpenSIPS 2.1 release - heads up
Good news, What is rtpengine support. Will the proxy manage RTP directly? Or will we still have to use RTP/Media Proxy Terrance ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] URGENT: ERROR:siptrace:pipport2su: bad protocol udp
I got your point, but our plan is to use 2.1.x and we are already using it
since last 6 month without issue.
But it should work in 2.1.x right?
On Sun, Mar 8, 2015 at 3:20 PM, wrote:
> OpenSIPS v2.x is much different then v1.x. So, if you are not familiar
> with it, you should better use 1.x
>
> Thank you.
>
>
>
> On 2015-03-08 19:52, Satish Patel wrote:
>
> I tried same configuration on 1.11 version and it works! so look like
> something wrong in 2.1.x version please fix that bug as soon as possible
>
> On Sun, Mar 8, 2015 at 2:04 PM, Satish Patel wrote:
>
>> sorry for push but it wired error!
>>
>> I have configure siptrace to send packet to "Homer" but getting following
>> error in logs
>>
>> ERROR:siptrace:pipport2su: bad protocol udp
>> ERROR:siptrace:pipport2su: bad protocol udp
>> ERROR:siptrace:pipport2su: bad protocol udp
>>
>> Opensips 2.1.x
>>
>> SIP Capture agent
>> loadmodule "siptrace.so"
>> modparam("siptrace", "duplicate_uri", "sip:192.168.1.200:9060")
>> modparam("siptrace", "duplicate_with_hep", 1)
>> modparam("siptrace", "trace_to_database", 0)
>> modparam("siptrace", "trace_flag", 22)
>> modparam("siptrace", "trace_on", 1)
>> #HEPv2 == timestamp will be included to HEP header
>> modparam("siptrace", "hep_version", 1)
>> modparam("siptrace", "db_url", "mysql://opensips:xx@localhost
>> /opensips")
>>
>> ...
>> ...
>> route{
>>
>> setflag(22);
>>
>> sip_trace();
>>
>>
>>
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] URGENT: ERROR:siptrace:pipport2su: bad protocol udp
OpenSIPS v2.x is much different then v1.x. So, if you are not
familiar with it, you should better use 1.x
Thank you.
On 2015-03-08
19:52, Satish Patel wrote:
> I tried same configuration on 1.11
version and it works! so look like something wrong in 2.1.x version
please fix that bug as soon as possible
>
> On Sun, Mar 8, 2015 at
2:04 PM, Satish Patel wrote:
>
>> sorry for
push but it wired error!
>> I have configure siptrace to send packet to
"Homer" but getting following error in logs
>>
>>
ERROR:siptrace:pipport2su: bad protocol udp
>>
ERROR:siptrace:pipport2su: bad protocol udp
>>
ERROR:siptrace:pipport2su: bad protocol udp
>>
>> Opensips 2.1.x
>>
>> SIP Capture agent
>> loadmodule "siptrace.so"
>>
modparam("siptrace", "duplicate_uri", "sip:192.168.1.200:9060 [1]")
>>
modparam("siptrace", "duplicate_with_hep", 1)
>> modparam("siptrace",
"trace_to_database", 0)
>> modparam("siptrace", "trace_flag", 22)
>>
modparam("siptrace", "trace_on", 1)
>> #HEPv2 == timestamp will be
included to HEP header
>> modparam("siptrace", "hep_version", 1)
>>
modparam("siptrace", "db_url",
"mysql://opensips:xx@localhost/opensips")
>>
>> ...
>> ...
>>
>> route{
>>
>> setflag(22);
>>
>> sip_trace();
Links:
--
[1] http://192.168.1.200:9060
[2]
mailto:satish@gmail.com
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] URGENT: ERROR:siptrace:pipport2su: bad protocol udp
I tried same configuration on 1.11 version and it works! so look like
something wrong in 2.1.x version please fix that bug as soon as possible
On Sun, Mar 8, 2015 at 2:04 PM, Satish Patel wrote:
> sorry for push but it wired error!
>
> I have configure siptrace to send packet to "Homer" but getting following
> error in logs
>
> ERROR:siptrace:pipport2su: bad protocol udp
> ERROR:siptrace:pipport2su: bad protocol udp
> ERROR:siptrace:pipport2su: bad protocol udp
>
> Opensips 2.1.x
>
> SIP Capture agent
> loadmodule "siptrace.so"
> modparam("siptrace", "duplicate_uri", "sip:192.168.1.200:9060")
> modparam("siptrace", "duplicate_with_hep", 1)
> modparam("siptrace", "trace_to_database", 0)
> modparam("siptrace", "trace_flag", 22)
> modparam("siptrace", "trace_on", 1)
> #HEPv2 == timestamp will be included to HEP header
> modparam("siptrace", "hep_version", 1)
> modparam("siptrace", "db_url", "mysql://opensips:xx@localhost
> /opensips")
>
> ...
> ...
> route{
>
> setflag(22);
>
> sip_trace();
>
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] URGENT: ERROR:siptrace:pipport2su: bad protocol udp
sorry for push but it wired error!
I have configure siptrace to send packet to "Homer" but getting following
error in logs
ERROR:siptrace:pipport2su: bad protocol udp
ERROR:siptrace:pipport2su: bad protocol udp
ERROR:siptrace:pipport2su: bad protocol udp
Opensips 2.1.x
SIP Capture agent
loadmodule "siptrace.so"
modparam("siptrace", "duplicate_uri", "sip:192.168.1.200:9060")
modparam("siptrace", "duplicate_with_hep", 1)
modparam("siptrace", "trace_to_database", 0)
modparam("siptrace", "trace_flag", 22)
modparam("siptrace", "trace_on", 1)
#HEPv2 == timestamp will be included to HEP header
modparam("siptrace", "hep_version", 1)
modparam("siptrace", "db_url", "mysql://opensips:xx@localhost/opensips")
...
...
route{
setflag(22);
sip_trace();
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Version question
We have upgraded 1.12.x to 2.1.x and its been 5 month no issue so far,
everything works! i am waiting for 2.1.x stable release so i can push it
out but i would say so far its good and stable.
Just question to Liviu, How do i use latest 2.1.x feature? currently i am
using 1.x config. but i would like to use latest feature of 2.1.x
On Sun, Mar 8, 2015 at 1:12 PM, Liviu Chircu wrote:
> Syntax-wise, these are the only major changes in 2.1:
>
> * for udp/tcp/sctp/tls listeners, you must also do a `loadmodule
> "proto_xxx.so"` command after setting your mpath.
> * the global tcp_xxx and tls_xxx params must now be rewritten as
> modparam("proto_", "_", ...)
>
> Now, from a stability point of view, the network layer has been completely
> re-organized in order to easily support the addition of new transport
> protocols. This code is currently in a beta phase - it needs testing. But
> modules are unchanged and should behave exactly the same. So yes, "it
> should all work in general" :)
>
> Liviu Chircu
> OpenSIPS Developerhttp://www.opensips-solutions.com
>
> On 08.03.2015 18:43, John Nash wrote:
>
> OK. Thank you. I have one more related question. If I use 2.1 version (I
> understand there may be some bugs) and use it with 1.X scripts (I mean
> without using async features in script for now) should it all work in
> general?...Like all modules?
>
> On Sun, Mar 8, 2015 at 9:52 PM, Liviu Chircu wrote:
>
>> Hello John,
>>
>> 1.11.3 LTS seems to be what you're looking for [1]. You can get it with:
>> git clone https://github.com/OpenSIPS/opensips.git -b 1.11
>>
>> [1] http://www.opensips.org/About/AvailableVersions
>>
>> Best regards,
>>
>> Liviu Chircu
>> OpenSIPS Developerhttp://www.opensips-solutions.com
>>
>> On 08.03.2015 17:59, John Nash wrote:
>>
>> I had started testing 1.X series taken from github master branch couple
>> of months ago (It shows version as Server:: OpenSIPS (1.12.0dev-notls
>> (x86_64/linux))
>>
>> Now I need to install it in one of the production server and before I do
>> that I want to update to the latest version of 1.X series. Which branch
>> should I use to use most upto date 1.X opensips (As master branch now is
>> 2.1)
>>
>>
>> ___
>> Users mailing
>> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>>
>> ___
>> Users mailing list
>> Users@lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>
>
> ___
> Users mailing
> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Version question
Syntax-wise, these are the only major changes in 2.1:
* for udp/tcp/sctp/tls listeners, you must also do a `loadmodule
"proto_xxx.so"` command after setting your mpath.
* the global tcp_xxx and tls_xxx params must now be rewritten as
modparam("proto_", "_", ...)
Now, from a stability point of view, the network layer has been
completely re-organized in order to easily support the addition of new
transport protocols. This code is currently in a beta phase - it needs
testing. But modules are unchanged and should behave exactly the same.
So yes, "it should all work in general" :)
Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com
On 08.03.2015 18:43, John Nash wrote:
OK. Thank you. I have one more related question. If I use 2.1 version
(I understand there may be some bugs) and use it with 1.X scripts (I
mean without using async features in script for now) should it all
work in general?...Like all modules?
On Sun, Mar 8, 2015 at 9:52 PM, Liviu Chircu > wrote:
Hello John,
1.11.3 LTS seems to be what you're looking for [1]. You can get it
with:
git clone https://github.com/OpenSIPS/opensips.git -b 1.11
[1] http://www.opensips.org/About/AvailableVersions
Best regards,
Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com
On 08.03.2015 17:59, John Nash wrote:
I had started testing 1.X series taken from github master branch
couple of months ago (It shows version as Server:: OpenSIPS
(1.12.0dev-notls (x86_64/linux))
Now I need to install it in one of the production server and
before I do that I want to update to the latest version of 1.X
series. Which branch should I use to use most upto date 1.X
opensips (As master branch now is 2.1)
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Version question
OK. Thank you. I have one more related question. If I use 2.1 version (I understand there may be some bugs) and use it with 1.X scripts (I mean without using async features in script for now) should it all work in general?...Like all modules? On Sun, Mar 8, 2015 at 9:52 PM, Liviu Chircu wrote: > Hello John, > > 1.11.3 LTS seems to be what you're looking for [1]. You can get it with: > git clone https://github.com/OpenSIPS/opensips.git -b 1.11 > > [1] http://www.opensips.org/About/AvailableVersions > > Best regards, > > Liviu Chircu > OpenSIPS Developerhttp://www.opensips-solutions.com > > On 08.03.2015 17:59, John Nash wrote: > > I had started testing 1.X series taken from github master branch couple > of months ago (It shows version as Server:: OpenSIPS (1.12.0dev-notls > (x86_64/linux)) > > Now I need to install it in one of the production server and before I do > that I want to update to the latest version of 1.X series. Which branch > should I use to use most upto date 1.X opensips (As master branch now is > 2.1) > > > ___ > Users mailing > listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > ___ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Version question
Hello John, 1.11.3 LTS seems to be what you're looking for [1]. You can get it with: git clone https://github.com/OpenSIPS/opensips.git -b 1.11 [1] http://www.opensips.org/About/AvailableVersions Best regards, Liviu Chircu OpenSIPS Developer http://www.opensips-solutions.com On 08.03.2015 17:59, John Nash wrote: I had started testing 1.X series taken from github master branch couple of months ago (It shows version as Server:: OpenSIPS (1.12.0dev-notls (x86_64/linux)) Now I need to install it in one of the production server and before I do that I want to update to the latest version of 1.X series. Which branch should I use to use most upto date 1.X opensips (As master branch now is 2.1) ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] Version question
I had started testing 1.X series taken from github master branch couple of months ago (It shows version as Server:: OpenSIPS (1.12.0dev-notls (x86_64/linux)) Now I need to install it in one of the production server and before I do that I want to update to the latest version of 1.X series. Which branch should I use to use most upto date 1.X opensips (As master branch now is 2.1) ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] dispatcher wired behavior
I have two Freeswitch in dispatcher, everything works great but i have
notice in sip trace if FS1 receive 404 SIP code then it sending it to next
FS2, i think it should stop there instead of forwarding next FS2
Following is my config
Dispatcher
loadmodule "dispatcher.so"
modparam("dispatcher", "dst_avp", "$avp(271)")
modparam("dispatcher", "grp_avp", "$avp(272)")
modparam("dispatcher", "cnt_avp", "$avp(273)")
modparam("dispatcher", "ds_ping_interval", 5)
modparam("dispatcher", "ds_probing_threshhold", 5)
modparam("dispatcher", "ds_probing_mode", 0)
modparam("dispatcher", "options_reply_codes", "501, 403, 200")
modparam("dispatcher", "db_url", "mysql://opensips:@localhost
/opensips")
...
...
route[to_dispatcher] {
# Dispatch to FS
if ( !ds_select_dst("1", "4", "FM10")) {
send_reply("500","Unable to dispatch call to Freeswitch");
exit;
} else {
xlog("L_WARN", "dispatcher: Attempting to dispatch call to $du\n");
}
t_on_failure("dispatcher_rollover");
t_relay();
}
failure_route[dispatcher_rollover] {
if (t_was_cancelled()) {
exit;
}
if (t_check_status("408") && t_local_replied("all")) {
xlog("L_NOTICE", "dispatcher: connection timeout: $rd\n");
ds_mark_dst("p");
}
if(!ds_next_dst()) {
xlog("L_ERR", "dispatcher: No more dispatcher in route
set\n");
t_reply("500", "Temporary failure");
exit;
}
xlog("L_INFO", "dispatcher: attempting relay to new dispatcher:
$du\n");
t_on_failure("dispatcher_rollover");
t_relay();
}
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
