Hi,
Can anyone help clarify the following: According to LCR module docs for version 1.0.0, "gateway selection is based on caller's RPID URI (if available in caller's RPID AVP after authentication) or From URI and user part of Request-URI (telephone number)." What is the RPID AVP and how is it set?
The docs also say "a gateway matches a request if user part of Request-URI and "From" URI match the prefix and From pattern of the gateway". But in gw table, there is no From pattern column, just prefix: gw_name | grp_id | ip_addr | port | uri_scheme | transport | prefix
Also, it would be nice if gw matching could be based also on request method, request headers, or even arbitrary AVPs which would be set somewhere else. What do folks think about this?
Thanks,
JF
RPId is the remote party id (a draft from Cisco which never became an RFC, but it is widely used).
The remote party id AVP will be loaded during authentication (DB or radius) and can be added to the SIP message with: http://openser.org/docs/modules/1.0.x/auth.html#APPEND-RPID-HF-NO-PARAMS
klaus
JF wrote:
Hi,
Can anyone help clarify the following: According to LCR module docs for version 1.0.0, "gateway selection is based on caller's RPID URI (if available in caller's RPID AVP after authentication) or From URI and user part of Request-URI (telephone number)." What is the RPID AVP and how is it set?
The docs also say "a gateway matches a request if user part of Request-URI and "From" URI match the prefix and From pattern of the gateway". But in gw table, there is no From pattern column, just prefix: gw_name | grp_id | ip_addr | port | uri_scheme | transport | prefix
Also, it would be nice if gw matching could be based also on request method, request headers, or even arbitrary AVPs which would be set somewhere else. What do folks think about this?
Thanks,
JF
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
-
JF -
Klaus Darilion