I have just committed a new module "uac" that implements basic SIP UAC functionalities like: - manipulation of From header URI (caller id blocking, anonymization) - client-side authentication (SER should be able to authenticate itself as response to a challenge reply) - hopefully more in the future :-) .
This first version has a known limitation in authentication part - qop is not supported. Any feedback regarding the functionality or possible errors is highly appreciated.
Ramona
Ramona,
Any chance of commiting an example ser.cfg to CVS that shows how to implement caller ID blocking?
Regards, Paul
On Sun, 27 Feb 2005 18:36:41 +0100, Elena Ramona Modroiu ramona@voice-system.ro wrote:
I have just committed a new module "uac" that implements basic SIP UAC functionalities like:
- manipulation of From header URI (caller id blocking, anonymization)
- client-side authentication (SER should be able to authenticate itself as response to a challenge reply)
- hopefully more in the future :-) .
This first version has a known limitation in authentication part - qop is not supported. Any feedback regarding the functionality or possible errors is highly appreciated.
Ramona
Serdev mailing list serdev@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serdev
For implementing Caller ID blocking you just have to do : uac_replace_from("Anonymous","sip:anonymous@mydomain.com"); and to relay the request.
If you have phones which perform transaction matching based only on FROM TAG without using the FROM URI, you can safely use the from_restore_mode = 0 (none).
Otherwise, apply the patch from modules/uac/doc/replace_from.patch and switch to from_restore_mode = 1 (full from replacement and auto restoring).
I will try to build more comprehensive documentation, but I have too short time to spare right now.
Ramona
On Sun, Feb 27, 2005 at 12:50:53PM -0500, Java Rockx wrote:
Ramona,
Any chance of commiting an example ser.cfg to CVS that shows how to implement caller ID blocking?
Regards, Paul
On Sun, 27 Feb 2005 18:36:41 +0100, Elena Ramona Modroiu ramona@voice-system.ro wrote:
I have just committed a new module "uac" that implements basic SIP UAC functionalities like:
- manipulation of From header URI (caller id blocking, anonymization)
- client-side authentication (SER should be able to authenticate itself as response to a challenge reply)
- hopefully more in the future :-) .
This first version has a known limitation in authentication part - qop is not supported. Any feedback regarding the functionality or possible errors is highly appreciated.
Ramona
Serdev mailing list serdev@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serdev
Hi Elena!
How works the uac internally if I rewrite the from URI and forward it. Will it be a second transaction or do you re-write the existing dialog. I wonder how you will handle authentication which also should increase CSeq - so the CSeq between the SIP client and ser, and the CSeq between ser and the remote SIP entity will differ.
regards, klaus
Elena Ramona Modroiu wrote:
I have just committed a new module "uac" that implements basic SIP UAC functionalities like:
- manipulation of From header URI (caller id blocking, anonymization)
- client-side authentication (SER should be able to authenticate itself as response to a challenge reply)
- hopefully more in the future :-) .
This first version has a known limitation in authentication part - qop is not supported. Any feedback regarding the functionality or possible errors is highly appreciated.
Ramona
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-
Elena Ramona Modroiu -
Java Rockx -
Klaus Darilion