<p>In english please :-)</p>
<div class="gmail_quote">Le 4 juil. 2011 15:00, <<a href="mailto:users-request@lists.opensips.org">users-request@lists.opensips.org</a>> a écrit :<br type="attribution">> Send Users mailing list submissions to<br>
> <a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a><br>> <br>> To subscribe or unsubscribe via the World Wide Web, visit<br>> <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
> or, via email, send a message with subject or body 'help' to<br>> <a href="mailto:users-request@lists.opensips.org">users-request@lists.opensips.org</a><br>> <br>> You can reach the person managing the list at<br>
> <a href="mailto:users-owner@lists.opensips.org">users-owner@lists.opensips.org</a><br>> <br>> When replying, please edit your Subject line so it is more specific<br>> than "Re: Contents of Users digest..."<br>
> <br>> <br>> Today's Topics:<br>> <br>> 1. 1.7 CRITICAL tm Error (Chris Martineau)<br>> 2. Re: Users Digest, Vol 36, Issue 6 (Jayesh Nambiar)<br>> 3. Re: 1.7 CRITICAL tm Error (Vlad Paiu)<br>
> 4. passing auth credentials using opensips B2B modules<br>> (Jayesh Nambiar)<br>> 5. Re: SIP Registration Failure - 484 Address Incomplete<br>> (Bogdan-Andrei Iancu)<br>> <br>> <br>> ----------------------------------------------------------------------<br>
> <br>> Message: 1<br>> Date: Mon, 4 Jul 2011 11:51:33 +0100<br>> From: "Chris Martineau" <<a href="mailto:chris@ghosttelecom.com">chris@ghosttelecom.com</a>><br>> Subject: [OpenSIPS-Users] 1.7 CRITICAL tm Error<br>
> To: <<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>><br>> Message-ID:<br>> <1D10AB188D6CCA46BB4369E3268E36EF2D1B87@SVR01.ghosttelecom.local><br>> Content-Type: text/plain; charset="us-ascii"<br>
> <br>> Hi,<br>> <br>> <br>> <br>> Getting the following error upon connecting a call. Didn't get it with<br>> the last head version but have just downloaded the 1.7 trunk and I am<br>> now getting this.<br>
> <br>> <br>> <br>> CRITICAL:tm:run_trans_callbacks: callback type 128, id 1 entered<br>> <br>> <br>> <br>> Probably something to do with my config but getting no other errors so<br>> not sure where to look.<br>
> <br>> <br>> <br>> Regards<br>> <br>> <br>> <br>> Chris<br>> <br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL: <<a href="http://lists.opensips.org/pipermail/users/attachments/20110704/372f6dfb/attachment-0001.htm">http://lists.opensips.org/pipermail/users/attachments/20110704/372f6dfb/attachment-0001.htm</a>><br>
> <br>> ------------------------------<br>> <br>> Message: 2<br>> Date: Mon, 4 Jul 2011 16:23:55 +0530<br>> From: Jayesh Nambiar <<a href="mailto:jayesh.voip@gmail.com">jayesh.voip@gmail.com</a>><br>
> Subject: Re: [OpenSIPS-Users] Users Digest, Vol 36, Issue 6<br>> To: <a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a><br>> Message-ID:<br>> <CALvF6vAu343MMRKJJqhQ9APCAbOHXLgWt=_=<a href="mailto:KZhoGZ23b4Na3g@mail.gmail.com">KZhoGZ23b4Na3g@mail.gmail.com</a>><br>
> Content-Type: text/plain; charset="iso-8859-1"<br>> <br>> Thank you Ovidiu. I had assumed that the Custom-Headers parameters works<br>> only for the initial INVITE request. It works as expected. I have another<br>
> concern here:<br>> I dont want the "100 Trying" response going out to the call initiator<br>> because I know that "407" is will obviously come from the "Proxy Opensips".<br>> While using t_relay I could have done that using the flags inside the<br>
> t_relay function. Is it possible to avoid the "100 Trying" somehow when<br>> relaying the call in B2B mode?<br>> To be honest, I have a web application which initiates the call and expects<br>> a "407" response and then will send the INVITE again with digest<br>
> credentials. When that application gets the "100 Trying" response, the<br>> application gets confused :)<br>> Either I will have to tweak the application to just ignore the 100 response<br>> which is little difficult or else find a way to avoid sending 100 response<br>
> from opensips. Please Help !!<br>> <br>> Thanks in advance.<br>> <br>> --- Jayesh<br>> <br>> <br>>> Try adding your extra headers to the "cusotm_headers" parameter:<br>>> <a href="http://www.opensips.org/html/docs/modules/devel/b2b_logic.html#id250014">http://www.opensips.org/html/docs/modules/devel/b2b_logic.html#id250014</a><br>
>><br>>> Regards,<br>>> Ovidiu Sas<br>>><br>>> On Sat, Jul 2, 2011 at 5:46 AM, Jayesh Nambiar <<a href="mailto:jayesh.voip@gmail.com">jayesh.voip@gmail.com</a>><br>>> wrote:<br>>> > Hi All,<br>
>> > I have a following situtation:<br>>> > Sip-Endpoint --> Opensips B2B (with REFER scenario) --> Opensips<br>>> Proxy(Using<br>>> > Proxy Authorize for Authentication) --> PSTN Gateway<br>
>> > I need the "B2B Opensips" in between so that it can handle the REFER<br>>> > requests properly. The problem is that the "Proxy Opensips" responds back<br>>> as<br>>> > 407 with Proxy-Authenticate header along with the realm and nonce value;<br>
>> but<br>>> > the "B2B Opensips" would only send the 407 response to the Endpoint<br>>> without<br>>> > any Proxy-Authenticate header. Thus the call fails. I cannot authorize<br>>> the<br>
>> > Sip-Endpoint on the "B2B Opensips" because of the limitations of my<br>>> > architecture.<br>>> > What I need is, the 407 response gets back to the Sip-Endpoint<br>>> transparently<br>
>> > and the response to the same also reaches the "Proxy Opensips" properly,<br>>> so<br>>> > that the proxy authorization becomes successful and the call can go<br>>> through<br>>> > properly.<br>
>> > Is there something that can be done on the b2b_response route? Any<br>>> pointers<br>>> > or directions in achieving this will be very helpful !!<br>>> > Thanks in advance.<br>>> > --- Jayesh<br>
>> ><br>>><br>>><br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL: <<a href="http://lists.opensips.org/pipermail/users/attachments/20110704/7c812a94/attachment-0001.htm">http://lists.opensips.org/pipermail/users/attachments/20110704/7c812a94/attachment-0001.htm</a>><br>
> <br>> ------------------------------<br>> <br>> Message: 3<br>> Date: Mon, 04 Jul 2011 14:03:00 +0300<br>> From: Vlad Paiu <<a href="mailto:vladpaiu@opensips.org">vladpaiu@opensips.org</a>><br>> Subject: Re: [OpenSIPS-Users] 1.7 CRITICAL tm Error<br>
> To: <a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a><br>> Message-ID: <<a href="mailto:4E119DE4.9090701@opensips.org">4E119DE4.9090701@opensips.org</a>><br>> Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"<br>
> <br>> Hello Chris,<br>> <br>> That CRITICAL message is there to help us track down a bug that <br>> sometimes causes OpenSIPS to crash. We are currently in the testing <br>> phase, before the release, and we are still working on that bug.<br>
> <br>> Regards,<br>> <br>> -- <br>> Vlad Paiu<br>> OpenSIPS Developer<br>> <br>> <br>> <br>> On 07/04/2011 01:51 PM, Chris Martineau wrote:<br>>><br>>> Hi,<br>>><br>>> Getting the following error upon connecting a call. Didn't get it with <br>
>> the last head version but have just downloaded the 1.7 trunk and I am <br>>> now getting this.<br>>><br>>> CRITICAL:tm:run_trans_callbacks: callback type 128, id 1 entered<br>>><br>>> Probably something to do with my config but getting no other errors so <br>
>> not sure where to look.<br>>><br>>> Regards<br>>><br>>> Chris<br>>><br>>><br>>> _______________________________________________<br>>> Users mailing list<br>>> <a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
>> <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>> <br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>
> URL: <<a href="http://lists.opensips.org/pipermail/users/attachments/20110704/ae98fa07/attachment-0001.htm">http://lists.opensips.org/pipermail/users/attachments/20110704/ae98fa07/attachment-0001.htm</a>><br>> <br>
> ------------------------------<br>> <br>> Message: 4<br>> Date: Mon, 4 Jul 2011 16:38:20 +0530<br>> From: Jayesh Nambiar <<a href="mailto:jayesh.voip@gmail.com">jayesh.voip@gmail.com</a>><br>> Subject: [OpenSIPS-Users] passing auth credentials using opensips B2B<br>
> modules<br>> To: <a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a><br>> Message-ID:<br>> <CALvF6vDNdTnrWq8ySk6G9ppZCurqxZp5DeFY+x0VkK0wFz5M=<a href="mailto:g@mail.gmail.com">g@mail.gmail.com</a>><br>
> Content-Type: text/plain; charset="iso-8859-1"<br>> <br>> Thank you Ovidiu. I had assumed that the Custom-Headers parameters works<br>> only for the initial INVITE request. It works as expected. I have another<br>
> concern here:<br>> I dont want the "100 Trying" response going out to the call initiator<br>> because I know that "407" is will obviously come from the "Proxy Opensips".<br>> While using t_relay I could have done that using the flags inside the<br>
> t_relay function. Is it possible to avoid the "100 Trying" somehow when<br>> relaying the call in B2B mode?<br>> To be honest, I have a web application which initiates the call and expects<br>> a "407" response and then will send the INVITE again with digest<br>
> credentials. When that application gets the "100 Trying" response, the<br>> application gets confused :)<br>> Either I will have to tweak the application to just ignore the 100 response<br>> which is little difficult or else find a way to avoid sending 100 response<br>
> from opensips. Please Help !!<br>> <br>> Thanks in advance.<br>> <br>> --- Jayesh<br>> <br>> <br>> <br>>> Try adding your extra headers to the "cusotm_headers" parameter:<br>>> <a href="http://www.opensips.org/html/docs/modules/devel/b2b_logic.html#id250014">http://www.opensips.org/html/docs/modules/devel/b2b_logic.html#id250014</a><br>
>><br>>> Regards,<br>>> Ovidiu Sas<br>>><br>>> On Sat, Jul 2, 2011 at 5:46 AM, Jayesh Nambiar <<a href="mailto:jayesh.voip@gmail.com">jayesh.voip@gmail.com</a>><br>>> wrote:<br>>> > Hi All,<br>
>> > I have a following situtation:<br>>> > Sip-Endpoint --> Opensips B2B (with REFER scenario) --> Opensips<br>>> Proxy(Using<br>>> > Proxy Authorize for Authentication) --> PSTN Gateway<br>
>> > I need the "B2B Opensips" in between so that it can handle the REFER<br>>> > requests properly. The problem is that the "Proxy Opensips" responds back<br>>> as<br>>> > 407 with Proxy-Authenticate header along with the realm and nonce value;<br>
>> but<br>>> > the "B2B Opensips" would only send the 407 response to the Endpoint<br>>> without<br>>> > any Proxy-Authenticate header. Thus the call fails. I cannot authorize<br>>> the<br>
>> > Sip-Endpoint on the "B2B Opensips" because of the limitations of my<br>>> > architecture.<br>>> > What I need is, the 407 response gets back to the Sip-Endpoint<br>>> transparently<br>
>> > and the response to the same also reaches the "Proxy Opensips" properly,<br>>> so<br>>> > that the proxy authorization becomes successful and the call can go<br>>> through<br>>> > properly.<br>
>> > Is there something that can be done on the b2b_response route? Any<br>>> pointers<br>>> > or directions in achieving this will be very helpful !!<br>>> > Thanks in advance.<br>>> > --- Jayesh<br>
>> ><br>>><br>>><br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL: <<a href="http://lists.opensips.org/pipermail/users/attachments/20110704/066e9096/attachment-0001.htm">http://lists.opensips.org/pipermail/users/attachments/20110704/066e9096/attachment-0001.htm</a>><br>
> <br>> ------------------------------<br>> <br>> Message: 5<br>> Date: Mon, 04 Jul 2011 15:59:34 +0300<br>> From: Bogdan-Andrei Iancu <<a href="mailto:bogdan@opensips.org">bogdan@opensips.org</a>><br>
> Subject: Re: [OpenSIPS-Users] SIP Registration Failure - 484 Address<br>> Incomplete<br>> To: OpenSIPS users mailling list <<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>><br>> Message-ID: <<a href="mailto:4E11B936.10309@opensips.org">4E11B936.10309@opensips.org</a>><br>
> Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"<br>> <br>> Hi Mark,<br>> <br>> Probably you miss an "exit" after the save(location) block:<br>> <br>> if (!save("location"))<br>
> sl_reply_error();<br>> exit;<br>> }<br>> exit;<br>> <br>> <br>> Regards,<br>> Bogdan<br>> <br>> On 07/04/2011 06:23 AM, Mark Holloway wrote:<br>>> Odd, even though I now get 200 OK from OpenSIPS after registering I <br>
>> still receive 484 Address Incomplete after the 200 OK even though the <br>>> endpoint is registered.<br>>><br>>><br>>> On Jul 3, 2011, at 11:35 AM, Mark Holloway wrote:<br>>><br>>>> I resolved it. Forgot to uncomment one very important part of the <br>
>>> cfg file.<br>>>><br>>>> if (!save("location"))<br>>>> sl_reply_error();<br>>>><br>>>> exit;<br>>>> }<br>>>><br>>>><br>>>> On Jul 3, 2011, at 11:31 AM, Mark Holloway wrote:<br>
>>><br>>>>> I have OpenSIPS 1.6.4 configured as a SIP Registrar with mysql. It <br>>>>> is configured to challenge SIP registrations with authentication. <br>>>>> Keeping it simple, I've used opensipsctl to add user 1000 with <br>
>>>> password 1000 and set the IP/SIP Domain of OpenSIPS is 192.168.1.20. <br>>>>> I am attempting to register using Counterpath Bria 3.1 (Mac). Bria <br>>>>> sends the initial registration to OpenSIPS and it properly responds <br>
>>>> with a 401 Unauthorized, but after Bria responds to the 401 <br>>>>> challenge OpenSIPS responds with 484 Address Incomplete.<br>>>>><br>>>>> Looking at the docs I noticed OpenSIPS will send 484 if the username <br>
>>>> is not in the Request-Line. For example, OpenSIPS wants <br>>>>> <a href="mailto:1000@192.168.1.20">1000@192.168.1.20</a> but Bria sends 192.168.1.20. The way Bria <br>>>>> registers, the username portion (1000 in this case) is only in the <br>
>>>> Contact, To, and From headers. The R-URI line does not include the <br>>>>> username portion. Has anyone else encountered this?<br>>>>><br>>>>><br>>>>> ==<br>
>>>> Bria's response to 401 challenge<br>>>>> ==<br>>>>><br>>>>> Session Initiation Protocol<br>>>>> * Request-Line: REGISTER sip:192.168.1.20 SIP/2.0*<br>>>>> Method: REGISTER<br>
>>>> [Resent Packet: False]<br>>>>><br>>>>><br>>>>> Contact: <br>>>>> <sip:1000@192.168.1.116:62018;rinstance=3b31a8f560e5c3bc;transport=udp><br>
>>>> Contact Binding: <br>>>>> <sip:1000@192.168.1.116:62018;rinstance=3b31a8f560e5c3bc;transport=udp><br>>>>> To: "Mark"<<a href="mailto:sip%3A1000@192.168.1.20">sip:1000@192.168.1.20</a>><br>
>>>> SIP Display info: "Mark"<br>>>>> SIP to address: <a href="mailto:sip%3A1000@192.168.1.20">sip:1000@192.168.1.20</a><br>>>>> From: "Mark"<<a href="mailto:sip%3A1000@192.168.1.20">sip:1000@192.168.1.20</a>>;tag=fbaf644d<br>
>>>> SIP Display info: "Mark"<br>>>>> SIP from address: <a href="mailto:sip%3A1000@192.168.1.20">sip:1000@192.168.1.20</a><br>>>>> SIP tag: fbaf644d<br>
>>>><br>>>>><br>> <br>> -- <br>> Bogdan-Andrei Iancu<br>> OpenSIPS solutions and "know-how"<br>> <br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>
> URL: <<a href="http://lists.opensips.org/pipermail/users/attachments/20110704/c2ac85ac/attachment.htm">http://lists.opensips.org/pipermail/users/attachments/20110704/c2ac85ac/attachment.htm</a>><br>> <br>> ------------------------------<br>
> <br>> _______________________________________________<br>> Users mailing list<br>> <a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>> <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
> <br>> <br>> End of Users Digest, Vol 36, Issue 8<br>> ************************************<br></div>