2 Sep
2010
2 Sep
'10
8:05 p.m.
Hello all,
I am having little trouble routing registrations based on
route header in following configuration. UA sends registration to P1 and P1 is
ignoring “route header” and forwards registration request to Registrar.
I am using default kamailio configuration. Is there any thing I need to add to default
config to enable route headers?
UA----------------->proxy1(kamailio)------------------->proxy2------------------>Registrar
REGISTER sip:Registrar.com
SIP/2.0
Via: SIP/2.0/UDP
10.18.0.67:5060;branch=z9hG4bKd209323e;rport
Route: <sip:proxy2.com;lr>
Max-Forwards: 70
From: <sip:xxxxxx@registrar.com>;tag=a85f9424
To: <sip:xxxxx@registrar.com>
Contact: <sip:xxxxxxx@10.18.0.67>
Call-ID: 431368ae25a3e232
CSeq: 100 REGISTER
Expires: 840
Allow:
INVITE,ACK,BYE,CANCEL,OPTIONS,UPDATE,SUBSCRIBE,NOTIFY
Supported:
User-Agent: xg-tx60 3.1.17 (VeriCall Edge)
Content-Length: 0
ThanksSid
"May the light be with you." ______________________________________________
Siddhardha Garige
www.luminepixels.com
6 Sep
6 Sep
1:34 p.m.
The REGISTER request contains the "pre-loaded route set". Pre-loaded
route sets are for security reasons disabled in the default config
(to-tag check):
if (has_totag()) {
# sequential request withing a dialog should
# take the path determined by record-routing
if (loose_route()) {
...
route(RELAY);
} else {
...
Either remove the totag check or add an explicit entry (eg. before the
above block):
if (is_method("REGISTER") {
# allow pre-loaded route set for REGISTER
if (loose_route()) {
...
route(RELAY);
}
}
regards
Klaus
Am 02.09.2010 17:05, schrieb Siddhardha Garige:
Hello all,
I am having little trouble routing registrations based on route header
in following configuration. UA sends registration to P1 and P1 is
ignoring “route header” and forwards registration request to Registrar.
I am using default kamailio configuration. Is there any thing I need to
add to default config to enable route headers?
UA----------------->proxy1(kamailio)------------------->proxy2------------------>Registrar
REGISTER sip:Registrar.com SIP/2.0
Via: SIP/2.0/UDP 10.18.0.67:5060;branch=z9hG4bKd209323e;rport
Route: <sip:proxy2.com;lr>
Max-Forwards: 70
From: <sip:xxxxxx@registrar.com>;tag=a85f9424
To: <sip:xxxxx@registrar.com>
Contact: <sip:xxxxxxx@10.18.0.67>
Call-ID: 431368ae25a3e232
CSeq: 100 REGISTER
Expires: 840
Allow: INVITE,ACK,BYE,CANCEL,OPTIONS,UPDATE,SUBSCRIBE,NOTIFY
Supported:
User-Agent: xg-tx60 3.1.17 (VeriCall Edge)
Content-Length: 0
Thanks
Sid
"May the light be with you."
______________________________________________
Siddhardha Garige
www.luminepixels.com <http://www.luminepixels.com/>
_______________________________________________
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
2 p.m.
Route sets and REGISTER doesn't work well together. From RFC3261 section 10.3:
"Registrars MUST ignore the Record-Route header field if it is included in a REGISTER
request. Registrars
MUST NOT include a Record-Route header field in any response to a REGISTER request.
A registrar might receive a request that traversed a proxy which treats REGISTER as an
unknown request and
which added a Record-Route header field value."
Doesn't say much about pre-loaded route sets. What would be the case here?
/O
6 sep 2010 kl. 10.34 skrev Klaus Darilion:
The REGISTER request contains the "pre-loaded
route set". Pre-loaded route sets are for security reasons disabled in the default
config (to-tag check):
if (has_totag()) {
# sequential request withing a dialog should
# take the path determined by record-routing
if (loose_route()) {
...
route(RELAY);
} else {
...
Either remove the totag check or add an explicit entry (eg. before the above block):
if (is_method("REGISTER") {
# allow pre-loaded route set for REGISTER
if (loose_route()) {
...
route(RELAY);
}
}
regards
Klaus
Am 02.09.2010 17:05, schrieb Siddhardha Garige:
---
* Olle E Johansson - oej(a)edvina.net
* Cell phone +46 70 593 68 51, Office +46 8 96 40 20, Sweden
Hello all,
I am having little trouble routing registrations based on route header
in following configuration. UA sends registration to P1 and P1 is
ignoring “route header” and forwards registration request to Registrar.
I am using default kamailio configuration. Is there any thing I need to
add to default config to enable route headers?
UA----------------->proxy1(kamailio)------------------->proxy2------------------>Registrar
REGISTER sip:Registrar.com SIP/2.0
Via: SIP/2.0/UDP 10.18.0.67:5060;branch=z9hG4bKd209323e;rport
Route: <sip:proxy2.com;lr>
Max-Forwards: 70
From: <sip:xxxxxx@registrar.com>;tag=a85f9424
To: <sip:xxxxx@registrar.com>
Contact: <sip:xxxxxxx@10.18.0.67>
Call-ID: 431368ae25a3e232
CSeq: 100 REGISTER
Expires: 840
Allow: INVITE,ACK,BYE,CANCEL,OPTIONS,UPDATE,SUBSCRIBE,NOTIFY
Supported:
User-Agent: xg-tx60 3.1.17 (VeriCall Edge)
Content-Length: 0
Thanks
Sid
"May the light be with you."
______________________________________________
Siddhardha Garige
www.luminepixels.com <http://www.luminepixels.com/>
_______________________________________________
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
_______________________________________________
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
5:31 p.m.
Am 06.09.2010 11:00, schrieb Olle E. Johansson:
Route sets and REGISTER doesn't work well
together. From RFC3261 section 10.3:
"Registrars MUST ignore the Record-Route header field if it is included in a
REGISTER request. Registrars
MUST NOT include a Record-Route header field in any response to a REGISTER request.
A registrar might receive a request that traversed a proxy which treats REGISTER as an
unknown request and
which added a Record-Route header field value."
Doesn't say much about pre-loaded route sets. What would be the case here?
AFAIK pre-loaded route sets are fine with REGISTER. It is just the "bug"
that Record-Route is not allowed. Therefore they invented the Path
header the fix this "bug".
regards
Klaus
7 Sep
7 Sep
6:18 p.m.
Klaus,
Thanks. I removed to tag check from config file.
Thanks
Sid
"May the light be with you." ______________________________________________
Siddhardha Garige
www.luminepixels.com
--- On Mon, 9/6/10, Klaus Darilion <klaus.mailinglists(a)pernau.at> wrote:
From: Klaus Darilion <klaus.mailinglists(a)pernau.at>
Subject: Re: [SR-Users] Routing issues with SIP Route headers.
To: "Siddhardha Garige" <siddu999(a)yahoo.com>
Cc: "SR-Users" <sr-users(a)lists.sip-router.org>
Date: Monday, September 6, 2010, 4:34 AM
The REGISTER request contains the "pre-loaded route set". Pre-loaded
route sets are for security reasons disabled in the default config
(to-tag check):
if (has_totag()) {
# sequential request withing a dialog should
# take the path determined by record-routing
if (loose_route()) {
...
route(RELAY);
} else {
...
Either remove the totag check or add an explicit entry (eg. before the
above block):
if (is_method("REGISTER") {
# allow pre-loaded route set for REGISTER
if (loose_route()) {
...
route(RELAY);
}
}
regards
Klaus
Am 02.09.2010 17:05, schrieb Siddhardha Garige:
Hello all,
I am having little trouble routing registrations based on route header
in following configuration. UA sends registration to P1 and P1 is
ignoring “route header” and forwards registration request to Registrar.
I am using default kamailio configuration. Is there any thing I need to
add to default config to enable route headers?
UA----------------->proxy1(kamailio)------------------->proxy2------------------>Registrar
REGISTER sip:Registrar.com SIP/2.0
Via: SIP/2.0/UDP 10.18.0.67:5060;branch=z9hG4bKd209323e;rport
Route: <sip:proxy2.com;lr>
Max-Forwards: 70
From: <sip:xxxxxx@registrar.com>;tag=a85f9424
To: <sip:xxxxx@registrar.com>
Contact: <sip:xxxxxxx@10.18.0.67>
Call-ID: 431368ae25a3e232
CSeq: 100 REGISTER
Expires: 840
Allow: INVITE,ACK,BYE,CANCEL,OPTIONS,UPDATE,SUBSCRIBE,NOTIFY
Supported:
User-Agent: xg-tx60 3.1.17 (VeriCall Edge)
Content-Length: 0
Thanks
Sid
"May the light be with you."
______________________________________________
Siddhardha Garige
www.luminepixels.com <http://www.luminepixels.com/>
_______________________________________________
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
4981
days inactive
4986
days old
4 comments
3 participants
participants (3)
-
Klaus Darilion -
Olle E. Johansson -
Siddhardha Garige