BTW, very nice email domain -- magrathea-telecom ;-), I am sure you will
like the Call-ID and CSeq we put into aliases table, see
http://lists.iptel.org/pipermail/serdev/2004-July/002465.html
Grin - I've already noticed that!
for more details.
a) Incoming call has no remote-party-id, but does
have a numeric from
address. Create a remote-party-id based on the from address.
Stock ser makes it possible to create the remote-party-id based on the
digest credentials username. When you perform digest authentication,
it will retrieve the rpid value either from the database (subscriber
table) or from radius server and create a new remote-party-id header
field.
Yes, we are already using that for our basic features.
b) Either we
have a remote-party-id passed with the initial call, or
the one we constructed in (a). Now prepend a digit string pulled from
the database to the user part of the remote-party-id uri.
If you prepend the same string to all numbers then you can configure
it in the configuration file of ser using rpid_prefix and rpid_suffix
parameters.
If you need it on per-subscriber basis then you can include the prefix
directly in rpid column in subscriber table.
We want to prefix on a per-subscriber basis to whatever has been passed with
the incoming INVITE.
Many thanks for the replies - I think that I am actually going to have to
write a module to do this, but I don't think that it should be too
complicated!
LInus