9 Mar
2011
9 Mar
'11
5:38 p.m.
Dear All,
I wonder if Kamailio supports RFC5626 as edge proxy or outbound proxy.
That is,
Edge Proxy adds a Path header with a flow token
and includes the "ob" parameter when Processing Register Requests.
Eg:
Path: <sip:VskztcQ/S8p4WPbOnHbuyh5iJvJIW3ib@ep1.example.com;lr;ob>
If does, how can I config it in kamailio.cfg. At present, Kamailio can
only forward register msg to sip server and reply 200 OK to SIP UA with
"require: outbound" when register accepted. No "Path" and
"ob" added in
the msg forwarded to SIP server.
You answer is appreciated!!
Sincerely,
Derrick
9 Mar
9 Mar
6:24 p.m.
New subject: Does Kamailio support RFC5626 as Edge Proxy(or outbound proxy)
The nat_traversal module has a keep-alive mechanism that can be used
to keep connections active on proxy servers.
Also, using the textops module, new headers can be added an existing
headers can be modified.
I haven't read the whole rfc to give you definite answer, but it may
be possible to emulate an edge server with a well crafted config.
Regards,
Ovidiu Sas
On Wed, Mar 9, 2011 at 11:38 AM, Derrick Ding <dding(a)aastra.com> wrote:
Dear All,
I wonder if Kamailio supports RFC5626 as edge proxy or outbound proxy.
That is,
Edge Proxy adds a Path header with a flow token
and includes the "ob" parameter when Processing Register Requests.
Eg:
Path: <sip:VskztcQ/S8p4WPbOnHbuyh5iJvJIW3ib@ep1.example.com;lr;ob>
If does, how can I config it in kamailio.cfg. At present, Kamailio can only
forward register msg to sip server and reply 200 OK to SIP UA with “require:
outbound” when register accepted. No “Path” and “ob” added in the msg
forwarded to SIP server.
You answer is appreciated!!
Sincerely,
Derrick
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
7:59 p.m.
New subject: Does Kamailio support RFC5626 as Edge Proxy(or outbound proxy)
Hi Derrick,
Edge Proxy adds a Path header with a flow token
and includes the "ob" parameter when Processing Register Requests.
Eg:
Path: <sip:VskztcQ/S8p4WPbOnHbuyh5iJvJIW3ib@ep1.example.com;lr;ob>
http://kamailio.org/docs/modules/stable/modules_k/path.html and
http://kamailio.org/docs/modules/stable/modules_k/registrar.html#id2954403
(and the two following params) might be sufficient if you're just
interested in traversing NAT via kamailio acting as a load-balancer.
It's an implementation of RFC3327, see
http://openser.org/pipermail/devel/2006-March/002142.html for a
real-world example.
It won't handle the "ob" header and various keep-alive mechanisms
proposed in RFC5626 though, but probably you can solve this with the
nat-ping features of nathelper or nat_traversal modules anyways?
Andreas
8:56 p.m.
New subject: Does Kamailio support RFC5626 as Edge Proxy(or outbound proxy)
Hi Andreas and Ovidiu
Thanks for your reply, I will learn it.
I am the beginner of Kamalio from this week. Now I can make kamalio work
as an proxy between UA and Asterisk Sip server. I have some basic
problem for outgoing call. I will create another topic for that. And
hope you will help. :-)
Thanks a again!!!!
Derrick
-----Original Message-----
From: sr-users-bounces(a)lists.sip-router.org
[mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Andreas
Granig
Sent: Wednesday, March 09, 2011 2:00 PM
To: sr-users(a)lists.sip-router.org
Subject: Re: [SR-Users] Does Kamailio support RFC5626 as Edge Proxy(or
outbound proxy)
Hi Derrick,
Edge Proxy adds a Path header with a flow token
and includes the "ob" parameter when Processing Register Requests.
Eg:
Path: <sip:VskztcQ/S8p4WPbOnHbuyh5iJvJIW3ib@ep1.example.com;lr;ob>
http://kamailio.org/docs/modules/stable/modules_k/path.html and
http://kamailio.org/docs/modules/stable/modules_k/registrar.html#id29544
03
(and the two following params) might be sufficient if you're just
interested in traversing NAT via kamailio acting as a load-balancer.
It's an implementation of RFC3327, see
http://openser.org/pipermail/devel/2006-March/002142.html for a
real-world example.
It won't handle the "ob" header and various keep-alive mechanisms
proposed in RFC5626 though, but probably you can solve this with the
nat-ping features of nathelper or nat_traversal modules anyways?
Andreas
4805
days inactive
4805
days old
3 comments
3 participants
participants (3)
-
Andreas Granig -
Derrick Ding -
Ovidiu Sas