Kamailio xhttp module (Websocket) header on SIP logic
up vote
0
down vote
favorite
I have a Kamailio behind a nginx for websockets secure. nginx setup some headers like X-Forwarded-For and I want to handle this values on main routing logic.
http nginx websocket http-headers kamailio
asked Nov 9 at 17:10
Javier Valencia
502319
add a comment |
up vote
0
down vote
favorite
I have a Kamailio behind a nginx for websockets secure. nginx setup some headers like X-Forwarded-For and I want to handle this values on main routing logic.
http nginx websocket http-headers kamailio
asked Nov 9 at 17:10
Javier Valencia
502319
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have a Kamailio behind a nginx for websockets secure. nginx setup some headers like X-Forwarded-For and I want to handle this values on main routing logic.
http nginx websocket http-headers kamailio
asked Nov 9 at 17:10
Javier Valencia
502319
I have a Kamailio behind a nginx for websockets secure. nginx setup some headers like X-Forwarded-For and I want to handle this values on main routing logic.
http nginx websocket http-headers kamailio
http nginx websocket http-headers kamailio
asked Nov 9 at 17:10
Javier Valencia
502319
asked Nov 9 at 17:10
Javier Valencia
502319
asked Nov 9 at 17:10
Javier Valencia
502319
asked Nov 9 at 17:10
Javier Valencia
502319
asked Nov 9 at 17:10
Javier Valencia
502319
502319
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
The value of the header should be available inside event_route for xhttp module via $hdr(X-Forwarded-For).
answered Nov 10 at 19:09
miconda
1,08677
I'm asking how to pass this values to main route. There are a way to do?
– Javier Valencia
Nov 11 at 8:30
Hi @miconda, I have a pair of tools to do this,$shvand$shtvariable types. I can get header value fromevent_route[xttp:request]when uprade to WS, and make it available inrequest_routethru $conid.
– Javier Valencia
Nov 12 at 16:30
But, which of both methods have a better performance?
– Javier Valencia
Nov 12 at 16:31
In request_route you get the SIP messages sent over the websocket, not the http requests. So you need to store the HTTP header with operations inside event route, and you pointed, using a hash table with connection id is a good solution. The $shv(...) is a single value variable and its name is static, it doesn't work if you have more than one websocket connection. Use $sht(...).
– miconda
Nov 12 at 21:55
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
The value of the header should be available inside event_route for xhttp module via $hdr(X-Forwarded-For).
answered Nov 10 at 19:09
miconda
1,08677
I'm asking how to pass this values to main route. There are a way to do?
– Javier Valencia
Nov 11 at 8:30
Hi @miconda, I have a pair of tools to do this,$shvand$shtvariable types. I can get header value fromevent_route[xttp:request]when uprade to WS, and make it available inrequest_routethru $conid.
– Javier Valencia
Nov 12 at 16:30
But, which of both methods have a better performance?
– Javier Valencia
Nov 12 at 16:31
In request_route you get the SIP messages sent over the websocket, not the http requests. So you need to store the HTTP header with operations inside event route, and you pointed, using a hash table with connection id is a good solution. The $shv(...) is a single value variable and its name is static, it doesn't work if you have more than one websocket connection. Use $sht(...).
– miconda
Nov 12 at 21:55
add a comment |
up vote
0
down vote
The value of the header should be available inside event_route for xhttp module via $hdr(X-Forwarded-For).
answered Nov 10 at 19:09
miconda
1,08677
I'm asking how to pass this values to main route. There are a way to do?
– Javier Valencia
Nov 11 at 8:30
Hi @miconda, I have a pair of tools to do this,$shvand$shtvariable types. I can get header value fromevent_route[xttp:request]when uprade to WS, and make it available inrequest_routethru $conid.
– Javier Valencia
Nov 12 at 16:30
But, which of both methods have a better performance?
– Javier Valencia
Nov 12 at 16:31
In request_route you get the SIP messages sent over the websocket, not the http requests. So you need to store the HTTP header with operations inside event route, and you pointed, using a hash table with connection id is a good solution. The $shv(...) is a single value variable and its name is static, it doesn't work if you have more than one websocket connection. Use $sht(...).
– miconda
Nov 12 at 21:55
add a comment |
up vote
0
down vote
up vote
0
down vote
The value of the header should be available inside event_route for xhttp module via $hdr(X-Forwarded-For).
answered Nov 10 at 19:09
miconda
1,08677
The value of the header should be available inside event_route for xhttp module via $hdr(X-Forwarded-For).
answered Nov 10 at 19:09
miconda
1,08677
answered Nov 10 at 19:09
miconda
1,08677
answered Nov 10 at 19:09
miconda
1,08677
answered Nov 10 at 19:09
miconda
1,08677
1,08677
I'm asking how to pass this values to main route. There are a way to do?
– Javier Valencia
Nov 11 at 8:30
Hi @miconda, I have a pair of tools to do this,$shvand$shtvariable types. I can get header value fromevent_route[xttp:request]when uprade to WS, and make it available inrequest_routethru $conid.
– Javier Valencia
Nov 12 at 16:30
But, which of both methods have a better performance?
– Javier Valencia
Nov 12 at 16:31
In request_route you get the SIP messages sent over the websocket, not the http requests. So you need to store the HTTP header with operations inside event route, and you pointed, using a hash table with connection id is a good solution. The $shv(...) is a single value variable and its name is static, it doesn't work if you have more than one websocket connection. Use $sht(...).
– miconda
Nov 12 at 21:55
add a comment |
I'm asking how to pass this values to main route. There are a way to do?
– Javier Valencia
Nov 11 at 8:30
Hi @miconda, I have a pair of tools to do this,$shvand$shtvariable types. I can get header value fromevent_route[xttp:request]when uprade to WS, and make it available inrequest_routethru $conid.
– Javier Valencia
Nov 12 at 16:30
But, which of both methods have a better performance?
– Javier Valencia
Nov 12 at 16:31
In request_route you get the SIP messages sent over the websocket, not the http requests. So you need to store the HTTP header with operations inside event route, and you pointed, using a hash table with connection id is a good solution. The $shv(...) is a single value variable and its name is static, it doesn't work if you have more than one websocket connection. Use $sht(...).
– miconda
Nov 12 at 21:55
I'm asking how to pass this values to main route. There are a way to do?
– Javier Valencia
Nov 11 at 8:30
I'm asking how to pass this values to main route. There are a way to do?
– Javier Valencia
Nov 11 at 8:30
Hi @miconda, I have a pair of tools to do this,
$shv and $sht variable types. I can get header value from event_route[xttp:request] when uprade to WS, and make it available in request_route thru $conid.– Javier Valencia
Nov 12 at 16:30
Hi @miconda, I have a pair of tools to do this,
$shv and $sht variable types. I can get header value from event_route[xttp:request] when uprade to WS, and make it available in request_route thru $conid.– Javier Valencia
Nov 12 at 16:30
But, which of both methods have a better performance?
– Javier Valencia
Nov 12 at 16:31
But, which of both methods have a better performance?
– Javier Valencia
Nov 12 at 16:31
In request_route you get the SIP messages sent over the websocket, not the http requests. So you need to store the HTTP header with operations inside event route, and you pointed, using a hash table with connection id is a good solution. The $shv(...) is a single value variable and its name is static, it doesn't work if you have more than one websocket connection. Use $sht(...).
– miconda
Nov 12 at 21:55
In request_route you get the SIP messages sent over the websocket, not the http requests. So you need to store the HTTP header with operations inside event route, and you pointed, using a hash table with connection id is a good solution. The $shv(...) is a single value variable and its name is static, it doesn't work if you have more than one websocket connection. Use $sht(...).
– miconda
Nov 12 at 21:55
add a comment |
draft saved
draft discarded
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53230377%2fkamailio-xhttp-module-websocket-header-on-sip-logic%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
