<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#3333ff">
Buenas tardes, alguien de la lista habla español o portugues, y que
este disponible para hacerme un pequeño trabajo en opensips?<br>
<br>
disculpe pero no hablo ingles<br>
<br>
saludos<br>
<br>
<br>
<br>
<br>
<a class="moz-txt-link-abbreviated" href="mailto:users-request@lists.opensips.org">users-request@lists.opensips.org</a> escreveu:
<blockquote
cite="mid:mailman.11599.1323980456.13472.users@lists.opensips.org"
type="cite">
<pre wrap="">Send Users mailing list submissions to
<a class="moz-txt-link-abbreviated" href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>
To subscribe or unsubscribe via the World Wide Web, visit
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
or, via email, send a message with subject or body 'help' to
<a class="moz-txt-link-abbreviated" href="mailto:users-request@lists.opensips.org">users-request@lists.opensips.org</a>
You can reach the person managing the list at
<a class="moz-txt-link-abbreviated" href="mailto:users-owner@lists.opensips.org">users-owner@lists.opensips.org</a>
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Users digest..."
Today's Topics:
1. Re: how does OpenSIPS manage 183's message?? (spady)
2. Re: Siptraces not shown on OpenSIPS-CP (spady)
3. Re: uac_replace_from corruption (Jeff Pyle)
4. SIP/SIMPLE to XMPP Gateway for SMS (DMF)
5. Re: B2BUA Ripping/Truncating Callid (Logan)
----------------------------------------------------------------------
Message: 1
Date: Thu, 15 Dec 2011 06:21:01 -0800 (PST)
From: spady <a class="moz-txt-link-rfc2396E" href="mailto:spady77@gmail.com"><spady77@gmail.com></a>
Subject: Re: [OpenSIPS-Users] how does OpenSIPS manage 183's message??
To: <a class="moz-txt-link-abbreviated" href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>
Message-ID: <a class="moz-txt-link-rfc2396E" href="mailto:1323958861503-7097238.post@n2.nabble.com"><1323958861503-7097238.post@n2.nabble.com></a>
Content-Type: text/plain; charset=us-ascii
Hi Denis, that was it!!!!!!! It was setted to "auto" .
I set it to "none" and now it works as aspected!!!! Perfet.
Thank you very much for your hint ;-)
Best regards
--
View this message in context: <a class="moz-txt-link-freetext" href="http://opensips-open-sip-server.1449251.n2.nabble.com/how-does-OpenSIPS-manage-183-s-message-tp7090462p7097238.html">http://opensips-open-sip-server.1449251.n2.nabble.com/how-does-OpenSIPS-manage-183-s-message-tp7090462p7097238.html</a>
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
------------------------------
Message: 2
Date: Thu, 15 Dec 2011 08:14:30 -0800 (PST)
From: spady <a class="moz-txt-link-rfc2396E" href="mailto:spady77@gmail.com"><spady77@gmail.com></a>
Subject: Re: [OpenSIPS-Users] Siptraces not shown on OpenSIPS-CP
To: <a class="moz-txt-link-abbreviated" href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>
Message-ID: <a class="moz-txt-link-rfc2396E" href="mailto:1323965670161-7097614.post@n2.nabble.com"><1323965670161-7097614.post@n2.nabble.com></a>
Content-Type: text/plain; charset=us-ascii
Can someone help me with this?
I checked again config and seems ok but form CP nothing yet.
Regards
--
View this message in context: <a class="moz-txt-link-freetext" href="http://opensips-open-sip-server.1449251.n2.nabble.com/Siptraces-not-shown-on-OpenSIPS-CP-tp7052741p7097614.html">http://opensips-open-sip-server.1449251.n2.nabble.com/Siptraces-not-shown-on-OpenSIPS-CP-tp7052741p7097614.html</a>
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
------------------------------
Message: 3
Date: Thu, 15 Dec 2011 12:27:38 -0500
From: Jeff Pyle <a class="moz-txt-link-rfc2396E" href="mailto:jpyle@fidelityvoice.com"><jpyle@fidelityvoice.com></a>
Subject: Re: [OpenSIPS-Users] uac_replace_from corruption
To: OpenSIPS users mailling list <a class="moz-txt-link-rfc2396E" href="mailto:users@lists.opensips.org"><users@lists.opensips.org></a>
Message-ID:
<a class="moz-txt-link-rfc2396E" href="mailto:CACYJG3JmK1T5Qw3ak7XKpD0VTUh-oaMX21cQKUEWXGUGCbJCtw@mail.gmail.com"><CACYJG3JmK1T5Qw3ak7XKpD0VTUh-oaMX21cQKUEWXGUGCbJCtw@mail.gmail.com></a>
Content-Type: text/plain; charset="iso-8859-1"
Brett,
Is the other end an Acme? If so, they need to implement some custom
parameters (which I do not have) to* *honor some parts of section 12 of
RFC3261 in such a way that won't break uac_replace_from(). Let me know if
this is the case and we'll talk more.
Rasvan,
Can you share more about the "new" way to do it with the dialog module? Is
this available in 1.6?
- Jeff
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <a class="moz-txt-link-rfc2396E" href="http://lists.opensips.org/pipermail/users/attachments/20111215/d914028f/attachment-0001.htm"><http://lists.opensips.org/pipermail/users/attachments/20111215/d914028f/attachment-0001.htm></a>
------------------------------
Message: 4
Date: Thu, 15 Dec 2011 10:03:47 -0800 (PST)
From: DMF <a class="moz-txt-link-rfc2396E" href="mailto:dmflists+opensips@gmail.com"><dmflists+opensips@gmail.com></a>
Subject: [OpenSIPS-Users] SIP/SIMPLE to XMPP Gateway for SMS
To: <a class="moz-txt-link-abbreviated" href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>
Message-ID: <a class="moz-txt-link-rfc2396E" href="mailto:1323972227724-7097996.post@n2.nabble.com"><1323972227724-7097996.post@n2.nabble.com></a>
Content-Type: text/plain; charset=us-ascii
Hi all,
I'm looking for a SIP/SIMPLE to XMPP gateway solution and my google searches
have brought me here. I have an account with a voip provider that supports
SMS via SIP/SIMPLE MESSAGE (<a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/rfc3428">http://tools.ietf.org/html/rfc3428</a>).
Unfortunately, I'm stuck using an old Blackberry which doesn't have any good
SIP apps, the only one that I've found that supports RFC3428 doesn't work
properly. I'm hoping that I can setup OpenSIPS to receive the SIP/SIMPLE
messages from my voip provider and forward them to an XMPP server like
openfire and be able to receive/respond to these messages via an XMPP
client. Would this be possible with OpenSIPS? Also, would it be possible to
have each message come from a unique XMPP user so that responses can be
tracked to the proper source?
Thanks.
--
View this message in context: <a class="moz-txt-link-freetext" href="http://opensips-open-sip-server.1449251.n2.nabble.com/SIP-SIMPLE-to-XMPP-Gateway-for-SMS-tp7097996p7097996.html">http://opensips-open-sip-server.1449251.n2.nabble.com/SIP-SIMPLE-to-XMPP-Gateway-for-SMS-tp7097996p7097996.html</a>
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
------------------------------
Message: 5
Date: Thu, 15 Dec 2011 20:20:38 +0000 (GMT)
From: Logan <a class="moz-txt-link-rfc2396E" href="mailto:voipmaster@me.com"><voipmaster@me.com></a>
Subject: Re: [OpenSIPS-Users] B2BUA Ripping/Truncating Callid
To: OpenSIPS users mailling list <a class="moz-txt-link-rfc2396E" href="mailto:users@lists.opensips.org"><users@lists.opensips.org></a>
Message-ID: <a class="moz-txt-link-rfc2396E" href="mailto:c54aa743-2fae-475c-e63c-98c47c137922@me.com"><c54aa743-2fae-475c-e63c-98c47c137922@me.com></a>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Out of curiosity, based on the feedback in this bug; is this something that's being fixed? I notice this bug was for 1.6.4, but my experience is in 1.7.1. so I want to make sure if this was fixed, I report a new bug for 1.7.1
Hi Bogdan,
This bug fix requires further work in tm module, in local_route processing,
so as to update the shortcuts in tm when lumps are applied for headers
also. The fix that was committed last week solved this problem only when
body lumps were applied.
Unfortunately, I don't have time to work on this, so I have removed the
assignation to me for this bug report.
Regards,
Anca
On Dec 12, 2011, at 09:05 AM, Ovidiu Sas <a class="moz-txt-link-rfc2396E" href="mailto:osas@voipembedded.com"><osas@voipembedded.com></a> wrote:
Yes, indeed. Thanks for pointing out.
Regards,
Ovidiu Sas
On Mon, Dec 12, 2011 at 1:26 AM, Ryan Bullock <a class="moz-txt-link-rfc2396E" href="mailto:rrb3942@gmail.com"><rrb3942@gmail.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I think this is related to a bug that is already open:
<a class="moz-txt-link-freetext" href="http://sourceforge.net/tracker/?func=detail&aid=3316230&group_id=232389&atid=1086410">http://sourceforge.net/tracker/?func=detail&aid=3316230&group_id=232389&atid=1086410</a>
On Fri, Dec 9, 2011 at 5:46 PM, Ovidiu Sas <a class="moz-txt-link-rfc2396E" href="mailto:osas@voipembedded.com"><osas@voipembedded.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Yeah, it's the first request after the modified INVITE that is
malformed (I reproduced this running a snapshot from trunk). ?Please
open a bug report.
Regards,
Ovidiu Sas
--
VoIP Embedded, Inc.
<a class="moz-txt-link-freetext" href="http://www.voipembedded.com">http://www.voipembedded.com</a>
On Fri, Dec 9, 2011 at 1:52 PM, Logan <a class="moz-txt-link-rfc2396E" href="mailto:voipmaster@me.com"><voipmaster@me.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I added the log and everything looks fine. It's only adding the PAI to the
initial invite which is what I want. The odd thing is there are no issues
with the invites, it just looks like the Cancel messages that are being
mangled. I posted a separate issue to the list prior to this report but no
one responded, I'm not sure it went through correctly but resulting cancel
coming out of the B2BUA looked like this:
?Reference:
192.168.1.146 = Opensips Proxy
192.168.1.145 = Opensips B2BUA
10.2.3.245 = Carrier
U 2011/12/01 22:51:11.558887 192.168.1.146:5060 -> 192.168.1.145:5090
CANCEL <a class="moz-txt-link-freetext" href="sip:9993512125551212@192.168.1.145:5090">sip:9993512125551212@192.168.1.145:5090</a> SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.146;branch=z9hG4bK2df7.78db1d81.0.
From: "James Logan" <a class="moz-txt-link-rfc2396E" href="sip:8884442222@192.168.1.137"><sip:8884442222@192.168.1.137></a>;tag=as06eabdcd.
Call-ID: <a class="moz-txt-link-abbreviated" href="mailto:40c30c6459b3eaa4683991082381cadb@192.168.1.137">40c30c6459b3eaa4683991082381cadb@192.168.1.137</a>.
To: "12125551212" <a class="moz-txt-link-rfc2396E" href="sip:12125551212@192.168.1.146"><sip:12125551212@192.168.1.146></a>.
CSeq: 102 CANCEL.
Max-Forwards: 70.
User-Agent: Opensips.
Content-Length: 0.
.
U 2011/12/01 22:51:11.559378 192.168.1.145:5090 -> 192.168.1.146:5060
SIP/2.0 200 canceling.
Via: SIP/2.0/UDP 192.168.1.146;branch=z9hG4bK2df7.78db1d81.0.
From: "James Logan" <a class="moz-txt-link-rfc2396E" href="sip:8884442222@192.168.1.137"><sip:8884442222@192.168.1.137></a>;tag=as06eabdcd.
Call-ID: <a class="moz-txt-link-abbreviated" href="mailto:40c30c6459b3eaa4683991082381cadb@192.168.1.137">40c30c6459b3eaa4683991082381cadb@192.168.1.137</a>.
To: "12125551212"
<a class="moz-txt-link-rfc2396E" href="sip:12125551212@192.168.1.146"><sip:12125551212@192.168.1.146></a>;tag=3330ae74b9cf9aed85afbc9203dd6238-715f
CSeq: 102 CANCEL.
Server: B2BUA.
Content-Length: 0.
.
U 2011/12/01 22:51:11.559527 192.168.1.145:5090 -> 10.2.3.245:5060
CANCEL ............i...............i.. SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.145:5090;branch=z9hG4bK5421.22999dd2.0.
........B2B.256.3572553sip:+12125551212@10.2.3.245sip:8884442222@192.168.1.1379120d3`.....p..i...........................................q.i............
........ CANCEL.
User-Agent: OpenSIPS (1.7.1-notls (x86_64/linux)).
Max-Forwards: 70.
User-Agent: Opensips.
Init-CallID: <a class="moz-txt-link-abbreviated" href="mailto:40c30c6459b3eaa4683991082381cadb@192.168.1.137">40c30c6459b3eaa4683991082381cadb@192.168.1.137</a>.
Contact: <a class="moz-txt-link-rfc2396E" href="sip:192.168.1.145:5090"><sip:192.168.1.145:5090></a>.
.
On Dec 07, 2011, at 05:18 PM, Ovidiu Sas <a class="moz-txt-link-rfc2396E" href="mailto:osas@voipembedded.com"><osas@voipembedded.com></a> wrote:
Add a log and print out what are you adding before adding it and you
will see if it's good or not.
On Wed, Dec 7, 2011 at 5:13 PM, Logan <a class="moz-txt-link-rfc2396E" href="mailto:voipmaster@me.com"><voipmaster@me.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">This is the extent of my local route. If the $var is not present, I do not
add it. Do you see any issue with what I'm doing here?
local_route {
? ? ? ? #xlog("L_INFO","***** IN LOCAL ROUTE ********\n");
? ? ? ? if (is_method("INVITE")) {
? ? ? ? ? ? ? ? if($var(pai_userpart)) {
? ? ? ? ? ? ? ? ? ? ? ? append_hf("P-Asserted-Identity:
\"$var(pai_display)\" <a class="moz-txt-link-rfc2396E" href="sip:$var(pai_userpart)@$Ri"><sip:$var(pai_userpart)@$Ri></a>\r\n");
? ? ? ? ? ? ? ? }else{
? ? ? ? ? ? ? ? ? ? ? ? xlog("L_INFO","PAI is not present, not adding\n");
? ? ? ? ? ? ? ? }
? ? ? ? }
}
On Dec 07, 2011, at 04:57 PM, Ovidiu Sas <a class="moz-txt-link-rfc2396E" href="mailto:osas@voipembedded.com"><osas@voipembedded.com></a> wrote:
You need to be careful when you alter requests in B2B mode (the
received INVITE and the sent INVITE belong to different transactions).
Make sure that you have something valid in those vars before applying
any changes to the outgoing message.
Regards,
Ovidiu Sas
On Wed, Dec 7, 2011 at 4:49 PM, Logan <a class="moz-txt-link-rfc2396E" href="mailto:voipmaster@me.com"><voipmaster@me.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I'm storing some $vars in route[0] prior to calling b2b_init_request("top
hiding");
Then in my local route Im appending a P-Asserted-Identity header.
I can't use the custom_headers modparam because it's going to preserve
the
PAI as it comes in. Most of the time it's not present, or is in the wrong
format so I'm adding it in local route.
On Dec 07, 2011, at 04:31 PM, Ovidiu Sas <a class="moz-txt-link-rfc2396E" href="mailto:osas@voipembedded.com"><osas@voipembedded.com></a> wrote:
Are you trying to perform any msg manipulations during b2b scenarios?
Also, keep in mind that the b2b server functionality must be kept
isolated from the proxy server functionality (proxy mode is not
compatible with b2b mode).
Regards,
Ovidiu Sas
--?VoIP Embedded, Inc.http://www.voipembedded.com
On Wed, Dec 7, 2011 at 3:41 PM, Logan <a class="moz-txt-link-rfc2396E" href="mailto:voipmaster@me.com"><voipmaster@me.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hello list this is the second odd thing I've seen with b2bua in opensips
1.7.1 It looks like the b2bua module is mangling the cancel message and
is
ripping out the callid when sending upstream:
U 2011/12/07 20:15:05.895915 192.168.1.143:5060 -> 192.168.1.145:5090
CANCEL <a class="moz-txt-link-freetext" href="sip:9993518045551212@192.168.1.145:5090">sip:9993518045551212@192.168.1.145:5090</a> SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.143;branch=z9hG4bKac0e.5a3d2bf1.0.
From: "8669800222" <a class="moz-txt-link-rfc2396E" href="sip:8669800222@192.168.1.1"><sip:8669800222@192.168.1.1></a>;tag=3532277698-944952.
Call-ID: <a class="moz-txt-link-abbreviated" href="mailto:494823-3532277698-944947@192.168.1.1">494823-3532277698-944947@192.168.1.1</a>.
To: "18045551212" <a class="moz-txt-link-rfc2396E" href="sip:18045551212@192.168.1.143"><sip:18045551212@192.168.1.143></a>.
CSeq: 1 CANCEL.
Max-Forwards: 70.
User-Agent: Opensips.
Content-Length: 0.
.
U 2011/12/07 20:15:05.896027 192.168.1.145:5090 -> 192.168.1.143:5060
SIP/2.0 200 canceling.
Via: SIP/2.0/UDP 192.168.1.143;branch=z9hG4bKac0e.5a3d2bf1.0.
From: "8669800222" <a class="moz-txt-link-rfc2396E" href="sip:8669800222@192.168.1.1"><sip:8669800222@192.168.1.1></a>;tag=3532277698-944952.
Call-ID: <a class="moz-txt-link-abbreviated" href="mailto:494823-3532277698-944947@192.168.1.1">494823-3532277698-944947@192.168.1.1</a>.
To: "18045551212"
<a class="moz-txt-link-rfc2396E" href="sip:18045551212@192.168.1.143"><sip:18045551212@192.168.1.143></a>;tag=3330ae74b9cf9aed85afbc9203dd6238-e6b7.
CSeq: 1 CANCEL.
Server: Opensips.
Content-Length: 0.
.
U 2011/12/07 20:15:05.896097 192.168.1.145:5090 -> 10.2.3.210:5060
CANCEL <a class="moz-txt-link-freetext" href="sip:+18045551212@65.211.120.23">sip:+18045551212@65.211.120.23</a> SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.145:5090;branch=z9hG4bK0299.252f8e61.0.
.
From: <a class="moz-txt-link-rfc2396E" href="sip:7324812444@66.29.74.37"><sip:7324812444@66.29.74.37></a>;tag=418802140f6308e008db76a1e1de765b.
CSeq: 2 INVITE54.7172739.
Content-Lengt
To: <a class="moz-txt-link-freetext" href="sip:+18045551212@65.211.120.237">sip:+18045551212@65.211.120.237</a>.
Call- CANCEL.
User-Agent: OpenSIPS (1.7.1-notls (x86_64/linux)).
Max-Forwards: 70.
Init-CallID: <a class="moz-txt-link-abbreviated" href="mailto:494823-3532277698-944947@192.168.1.1">494823-3532277698-944947@192.168.1.1</a>.
Contact: <a class="moz-txt-link-rfc2396E" href="sip:192.168.1.145:5090"><sip:192.168.1.145:5090></a>.
.
U 2011/12/07 20:15:05.910842 10.2.3.210:5060 -> 192.168.1.145:5090
SIP/2.0 400 Missing Mandatory Header Call-Id.
v: SIP/2.0/UDP
192.168.1.145:5090;branch=z9hG4bK0299.252f8e61.0;received=192.168.1.145.
l: 0.
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""><!---->
_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <a class="moz-txt-link-rfc2396E" href="http://lists.opensips.org/pipermail/users/attachments/20111215/e0f3662d/attachment.htm"><http://lists.opensips.org/pipermail/users/attachments/20111215/e0f3662d/attachment.htm></a>
------------------------------
_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
End of Users Digest, Vol 41, Issue 52
*************************************
__________ Información de ESET Smart Security, versión de la base de firmas de virus 6715 (20111215) __________
ESET Smart Security ha comprobado este mensaje.
<a class="moz-txt-link-freetext" href="http://www.eset.com">http://www.eset.com</a>
</pre>
</blockquote>
<br>
<BR>
<BR>
__________ Información de ESET Smart Security, versión de la base de firmas de virus 6715 (20111215) __________<BR>
<BR>
ESET Smart Security ha comprobado este mensaje.<BR>
<BR>
<A HREF="http://www.eset.com">http://www.eset.com</A><BR>
</body>
</html>