Hi Chris,

You will only need to call rtpproxy_offer() for the authenticated INVITE and register the onreply route that calls rtpproxy_answer() only for these INVITEs.

Regards,

Razvan Crainea
OpenSIPS Developer


On 20.06.2011 12:04, Chris Martineau wrote:
Hi,

This all works fine when not using the invite auth with everything
routing through the correct reply route for 183/200 responses (which
contain the correct rtpproxy_answer setups).

Regards

Chris



-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Razvan Crainea
Sent: 20 June 2011 08:39
To: [email protected]
Subject: Re: [OpenSIPS-Users] Registrant module invite auth

Hi Chris,

Please make sure that on your reply route "x" you call rtpproxy_answer()

method.

Regards,

Razvan Crainea
OpenSIPS Developer


On 17.06.2011 20:18, Chris Martineau wrote:
Hi,

On further investigation it would seem that the 183 and 200oks are not
being updated by rtpproxy with the new sdp parameters. I have added
another t_on_reply("x") in the failure route where the 407s are picked
up to point at the 183/200 pickup but replies seem to be bypassing this.
Any ideas on where to go with this would be greatly appreciated.

Regards

Chris


Hi,

Yes, changed to the realm and auth works ok.

However I now have a one way speech issue which may be due to rtpproxy
having a problem.
Do I need to do anything for rtpproxy when I send the auth'd invite?
All the original sdp changes are maintained but not sure if something is
being lost as I get no speech from the far end.
I assume drouting does a similar thing when trying different routes
and that works ok so not sure where the problem is.
Many thanks


Chris
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Ovidiu Sas
Sent: 17 June 2011 14:42
To: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] Registrant module invite auth

The credential params must have the realm, not the domain.  If the
realm is the same as your domain than you should be fine.
The script looks ok, make sure that you are going through it (add an
xlog before invoking uac_auth() and make sure that your credentials
are ok.


Regards,
Ovidiu Sas

On Fri, Jun 17, 2011 at 4:20 AM, Chris
Martineau<[email protected]>   wrote:
Hi,

Thanks for that.

I have applied this as I think it should work and I get it resend the
INVITE but does not insert the auth header?
Here is a snapshot of the config file...

Modparam("uac","credential",<username>:<domain>:<password>")

failure_route[1]{

         if (t_check_status("407")){
                 uac_auth();
                 t_relay();
                 exit();
         }


Are there any other parameters I need to set? Is this process
correct?
Many thanks


Regards

Chris

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Ovidiu Sas
Sent: 16 June 2011 17:45
To: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] Registrant module invite auth

Use the uac module to authenticate INVITEs:
http://www.opensips.org/html/docs/modules/devel/uac.html#id292889

Because the CSeq will be the same, the end point may or may not like
it.
Your mileage may vary.


Regards,
Ovidiu Sas

On Thu, Jun 16, 2011 at 12:37 PM, Chris Martineau
<[email protected]>   wrote:
Hi,

Registrant module working however the destination is also requiring
authentication on invites is this possible?
Regards

Chris

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Chris Martineau
Sent: 16 June 2011 14:56
To: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] Bye_on timeout_flag missing in 1.7

Ok thanks,

How stable is 1.7 as I will need to put this into a live high
traffic environment.
Regards

Chris

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Ovidiu Sas
Sent: 16 June 2011 14:25
To: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] Bye_on timeout_flag missing in 1.7

Actually, there are some dependencies on new development on trunk
and
therefor it will not work on the 1.6 branch.
Sorry for the false lead.
You will need to perform a full trunk install in order to get the
registrant functionality.

Regards,
Ovidiu Sas

On Thu, Jun 16, 2011 at 9:15 AM, Chris
Martineau<[email protected]>   wrote:
Hi,

Tried this but the the make install stops with Error 2 when it
tries to compile this module. All permissions are fine on the files.
Anything I need to change for it to compile this correctly?

Many thanks

Chris

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Ovidiu Sas
Sent: 16 June 2011 13:06
To: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] Bye_on timeout_flag missing in 1.7

Add the registrant directory to your 1.6 source code and
install/upgrade from there along with all the other modules in
order
to maintain compatibility between modules and core.

Regards,
Ovidiu Sas

On Thu, Jun 16, 2011 at 7:51 AM, Chris
Martineau<[email protected]>   wrote:
Hi Vlad,

Thanks for your help on this.

Just a quick question. I only need the registrant module from 1.7
can I
just compile this and copy the .so files over to my 1.6
installation?
Many thanks again

Chris

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Vlad Paiu
Sent: 16 June 2011 10:57
To: [email protected]
Subject: Re: [OpenSIPS-Users] Bye_on timeout_flag missing in 1.7

Hello,

OpenSIPS 1.7 has not been officially released yet :)
If you mean you have upgraded everything from trunk, please check
[1].
Briefly, the flag was removed, and to maintain functionality you
have to
call create_dialog() with a "B" parameter, like this :
      create_dialog("B");

[1]
http://www.opensips.org/html/docs/modules/devel/dialog.html#id298503

Regards,

--
Vlad Paiu
OpenSIPS Developer




On 06/16/2011 12:13 PM, Chris Martineau wrote:
Hi,

I have just upgraded to 1.7 and notice that the bye on timeout
flag is
no longer present in the dialog module even though the revision
and
date
seems to be the same?

Also I notice a number of functions in the nathelper module have
been
moved to a new rtpproxy module. Are there any allowances I need
to
make
in my existing config file apart from adding the new module?

Many thanks

Chris


-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Ovidiu Sas
Sent: 15 June 2011 13:04
To: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] opensips registering with gateway

Check out the new registrant module:
http://www.opensips.org/html/docs/modules/devel/registrant.html


Regards,
Ovidiu Sas

On Wed, Jun 15, 2011 at 7:31 AM, Chris Martineau
<[email protected]>     wrote:

Hi,



I have seen some trails indicating that you can use sipsak to
generate
registers for opensips but if I need to generate theses
registers
from
the

same port for it to be valid how can I prevent opensips
responding to
the

returned messages?



Is there another way of doing this? Thought I read somewhere
that
this
was

now incorporated into opensips as a module but can't find the
blog
trail

again.



The problem I have is the gateway provider can do ip
authentication
but only

for 1 account. I have multiple accounts so the only way is for

opensips to

register or for it to send/forward all traffic for that account
from
a
specific ip address different than the main one. Can this be
done?


Many thanks





Chris



_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users



_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to