We are needing to modify the configure of a currently operating OpenSER to properly relay the SUBSCRIBE and SIP-NOTIFY messages that are sent between Asterisk and a phone that supports BLF (like the Snom 300 or Yealink T26). Our setup includes an OpenSER 1.2 & Asterisk 1.4.17 in the same box. OpenSER performs all registration, authentication and NAT. Asterisk handles the media and the accounting.
In a pure Asterisk environment a "hint" would be setup in the Asterisk extensions.conf file and the phone (UA) would SUBSCRIBE to that HINT. Once Asterisk has registered that UA to the HINT then it sends SIP-NOTIFY messages to the UA as the status of the channel changes (available, ringing, busy).
Our current openser.cfg file makes no mention of either SUBSCRIBE or NOTIFY which is an obvious reason that my Asterisk installation never registers the UA to the HINT.
Is anyone interested in getting paid to fix this for us (we're too stupid to do it ourselves) or to offer another solution for controlling BLF in this setup.
Thanks, Mark
Hello,
On 03/07/2010 01:23 AM, Mark Sayer wrote:
We are needing to modify the configure of a currently operating OpenSER to properly relay the SUBSCRIBE and SIP-NOTIFY messages that are sent between Asterisk and a phone that supports BLF (like the Snom 300 or Yealink T26). Our setup includes an OpenSER 1.2 & Asterisk 1.4.17 in the same box. OpenSER performs all registration, authentication and NAT. Asterisk handles the media and the accounting.
openser 1.2.x is too old and does not have the blf features. You need at least kamailio (openser) 1.5.x, better 3.0.0.
It might work with latest Asterisk to send the subscribe to it and get NOTIFYs even phone is not registered to Asterisk, never tried though.
In a pure Asterisk environment a "hint" would be setup in the Asterisk extensions.conf file and the phone (UA) would SUBSCRIBE to that HINT. Once Asterisk has registered that UA to the HINT then it sends SIP-NOTIFY messages to the UA as the status of the channel changes (available, ringing, busy).
Our current openser.cfg file makes no mention of either SUBSCRIBE or NOTIFY which is an obvious reason that my Asterisk installation never registers the UA to the HINT.
Is anyone interested in getting paid to fix this for us (we're too stupid to do it ourselves) or to offer another solution for controlling BLF in this setup.
Can help only with 1.5.x/3.0.0.
Cheers, Daniel
On 03/07/2010 05:00 PM, Daniel-Constantin Mierla wrote:
Can help only with 1.5.x/3.0.0.
Yep, I think that's the defining attribute of this conversation.
problem found is 1.5.x nor 3.0.0 are able to compile in solaris with no errors, are really too many errors, should be able to compile or is not designed to uspport Sparc anymore.?
Here are some tests i did.
just basic mosdules like mysql lcr or carrierroute, i found carrierroute in 1.4.3 works really erratic not even close to a "probability" when you use prob different than 1, then i try to jump over 3.0.0 added modules etc and was unable to compile after several errors. using GCC from sun 1.4.0 and 1.4.1
i did go back to 1.5.4 and it compiles but when i try to run it it throws errors with the message "no socket to fork", if i run in debug mode with fork disable it runs. then i have had to go back to the 1.4.3 STABLE even with the erratic behave at least runs.
__________________________ Omar
On Mar 7, 2010, at 5:04 PM, Alex Balashov wrote:
On 03/07/2010 05:00 PM, Daniel-Constantin Mierla wrote:
Can help only with 1.5.x/3.0.0.
Yep, I think that's the defining attribute of this conversation.
-- Alex Balashov - Principal Evariste Systems LLC
Tel : +1 678-954-0670 Direct : +1 678-954-0671 Web : http://www.evaristesys.com/
Kamailio (OpenSER) - Users mailing list Users@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
On Monday 08 March 2010, Omar wrote:
problem found is 1.5.x nor 3.0.0 are able to compile in solaris with no errors, are really too many errors, should be able to compile or is not designed to uspport Sparc anymore.?
Hello Omar,
normally you should be able to compile this version on solaris as well. If there are errors they are probably caused from some small incompatibilities. We've fixed a buch of this problems in the past.
Here are some tests i did.
just basic mosdules like mysql lcr or carrierroute, i found carrierroute in 1.4.3 works really erratic not even close to a "probability" when you use prob different than 1,
I'm not aware of an error like this in carrierroute, can you add more details?
then i try to jump over 3.0.0 added modules etc and was unable to compile after several errors. using GCC from sun 1.4.0 and 1.4.1
i did go back to 1.5.4 and it compiles but when i try to run it it throws errors with the message "no socket to fork", if i run in debug mode with fork disable it runs. then i have had to go back to the 1.4.3 STABLE even with the erratic behave at least runs.
Here we also would need a bit more details about the problem, like the exact log message you observe.
Regards,
Henning
-
Alex Balashov -
Daniel-Constantin Mierla -
Henning Westerholt -
Mark Sayer -
Omar