Hi all,
There are modules that are using default values for AVPs. What will happen if another module is reusing the same AVP? Or if the AVP is redefined inside the script? Is this completely orthogonal? Should I worry about this while using AVPs?
Regards, Ovidiu Sas
Hello,
Am I correct in my assumption that I can't directly connect Openser to a ITSP due to Openser not providing registration to the ITSP? This seems to be what I read in the Openser documentation. This being the case, I have a Linksys SPA9000 pbx that I can use as a gateway to the ITSP, but attempts to route 10-digit numbers to the pbx get a response of 403 Forbidden from the pbx (the pbx has registered to the Openser OK). I see that many use an asterisk for a gateway, how do they get around this problem with the asterisk?
Thanks, Scott Yagel PacketCall, Inc. syagel@packetcall.net
I have trunking in place with two ITSPs using openser. We don't register as we are not doing a hosted IP centrex type of thing. We are doing trunking. /a
Scott Yagel wrote:
Hello,
Am I correct in my assumption that I can't directly connect Openser to a ITSP due to Openser not providing registration to the ITSP? This seems to be what I read in the Openser documentation. This being the case, I have a Linksys SPA9000 pbx that I can use as a gateway to the ITSP, but attempts to route 10-digit numbers to the pbx get a response of 403 Forbidden from the pbx (the pbx has registered to the Openser OK). I see that many use an asterisk for a gateway, how do they get around this problem with the asterisk?
Thanks, Scott Yagel PacketCall, Inc. syagel@packetcall.net
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Hello Ovidiu,
On 03/06/07 20:54, Ovidiu Sas wrote:
Hi all,
There are modules that are using default values for AVPs. What will happen if another module is reusing the same AVP? Or if the AVP is redefined inside the script? Is this completely orthogonal? Should I worry about this while using AVPs?
we are on the way to remove those hidden stuff. Not sure all will be done for this release. Modules like TM, registrar, auth, dispatcher, siptrace, nathelper were cleaned. Still lot of others use the avps. So far only auth/auth_db use $avp(s:rpid) for rpid management. Being there for long time, should be left at least for this release and prepare users for the next release. For the other modules, the avp names were set to NULL, so if they are to be used, the name has to be set for them. Also, the AVP names for these modules must be now in full format $avp(xyz).
Cheers, Daniel
Regards, Ovidiu Sas
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Hi Daniel,
The lcr module is still not aligned and it is still using custom avps. If I modify that particular avp in my script I will break lcr routing. Is that right?
We should document in the wiki all the "reserved" avps.
Regards, Ovidiu Sas
On 3/7/07, Daniel-Constantin Mierla daniel@voice-system.ro wrote:
Hello Ovidiu,
On 03/06/07 20:54, Ovidiu Sas wrote:
Hi all,
There are modules that are using default values for AVPs. What will happen if another module is reusing the same AVP? Or if the AVP is redefined inside the script? Is this completely orthogonal? Should I worry about this while using AVPs?
we are on the way to remove those hidden stuff. Not sure all will be done for this release. Modules like TM, registrar, auth, dispatcher, siptrace, nathelper were cleaned. Still lot of others use the avps. So far only auth/auth_db use $avp(s:rpid) for rpid management. Being there for long time, should be left at least for this release and prepare users for the next release. For the other modules, the avp names were set to NULL, so if they are to be used, the name has to be set for them. Also, the AVP names for these modules must be now in full format $avp(xyz).
Cheers, Daniel
Regards, Ovidiu Sas
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Hi Daniel,
The gap between 1.1 and 1.2 is pretty big, so forcing users to force the the auth rpid_avp to $avp(s:rpid) shouldn't be a big deal (just needs to be documented on the 1.1 to 1.2 migration path). I would rather have a clean code and just by checking my config file I should be able to track down all the avp that are used.
The "rpid" impact would be: - user must define the rpid_avp for the auth module - user must explicitly load the rpid_avp during load_credentials
Regards, Ovidiu Sas
On 3/7/07, Ovidiu Sas sip.nslu@gmail.com wrote:
Hi Daniel,
The lcr module is still not aligned and it is still using custom avps. If I modify that particular avp in my script I will break lcr routing. Is that right?
We should document in the wiki all the "reserved" avps.
Regards, Ovidiu Sas
On 3/7/07, Daniel-Constantin Mierla daniel@voice-system.ro wrote:
Hello Ovidiu,
On 03/06/07 20:54, Ovidiu Sas wrote:
Hi all,
There are modules that are using default values for AVPs. What will happen if another module is reusing the same AVP? Or if the AVP is redefined inside the script? Is this completely orthogonal? Should I worry about this while using AVPs?
we are on the way to remove those hidden stuff. Not sure all will be done for this release. Modules like TM, registrar, auth, dispatcher, siptrace, nathelper were cleaned. Still lot of others use the avps. So far only auth/auth_db use $avp(s:rpid) for rpid management. Being there for long time, should be left at least for this release and prepare users for the next release. For the other modules, the avp names were set to NULL, so if they are to be used, the name has to be set for them. Also, the AVP names for these modules must be now in full format $avp(xyz).
Cheers, Daniel
Regards, Ovidiu Sas
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Hi Daniel,
What are the plans for rpid for the 1.3 release? I think it's the only "hidden" avp left.
Regards, Ovidiu Sas
On 3/7/07, Daniel-Constantin Mierla daniel@voice-system.ro wrote:
Hello Ovidiu,
On 03/06/07 20:54, Ovidiu Sas wrote:
Hi all,
There are modules that are using default values for AVPs. What will happen if another module is reusing the same AVP? Or if the AVP is redefined inside the script? Is this completely orthogonal? Should I worry about this while using AVPs?
we are on the way to remove those hidden stuff. Not sure all will be done for this release. Modules like TM, registrar, auth, dispatcher, siptrace, nathelper were cleaned. Still lot of others use the avps. So far only auth/auth_db use $avp(s:rpid) for rpid management. Being there for long time, should be left at least for this release and prepare users for the next release. For the other modules, the avp names were set to NULL, so if they are to be used, the name has to be set for them. Also, the AVP names for these modules must be now in full format $avp(xyz).
Cheers, Daniel
Regards, Ovidiu Sas
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
-
Alan Crosswell -
Daniel-Constantin Mierla -
Ovidiu Sas -
Scott Yagel