Hi everybody,
I'm glad to make public the follow up of the OpenSER related events. I'm
sorry I was not able to do it sooner, but making all the arrangements
took more than estimated ;).
The second OpenSER Summit will take place in San Jose, USA , on the 17th
of March, 2008. This is the first US edition of the OpenSER Summit -
following the European edition, a large segment of the OpenSER community
have continuously asked for an edition to address also the American
community. The summit is again hosted inside the VoN Spring 2008
Exhibition, as a pre-conference event.
All participants to register via OpenSER site before Friday, March 7th,
will get free access to the OpenSER event.
More details about the OpenSER Summit, agenda and registration process,
are to be found on the project web page:
http://www.openser.org/mos/view/OpenSER-Summit-2008/
This OpenSER Summit edition is sponsored by a parallel OpenSER related
event, the OpenSER Pavilion . The pavilion is a common exhibiting area -
booth 1027, inside VoN expo, gathering, under the OpenSER name, six
different companies working or using the project. Their direct statement
to the visitor is: "Yes, we do open source in our business and OpenSER
is a success recipe and we want to share this with you"
More details about the OpenSER Pavilion, location and participants, are
to be found on the project web page:
http://www.openser.org/mos/view/OpenSER-Pavilion-2008/
The dual event, OpenSER Summit & Pavilion is new concept of a more
complex event, aiming to create a larger diversity and to give more
power to the understanding of the OpenSER project.
Again, I'm very happy we were able to continue the path opened with the
OpenSER Summit in Berlin and show the continuity in the OpenSER project
development.
Also, thanks to the industry support for the project, we were able again
to offer a free participation to the OpenSER Summit and allow a good
community convergence.
For any questions about the OpenSER Summit & Pavilion do not hesitate to
contact me.
Best regards,
Bogdan
My testbed is combination of openser and openxcap. openser.cfg file is similar with the example on
the website of OpenXCAP. After updating published information by sending PUBLISH, no NOTIFY
message is sent to client-side. I got the following errors(debug=3) in syslog file. Any ideas anyone?
---------------------------------------------------------------------------------------
ERROR:presence_xml:get_final_notify_body: while extracting the transformation node
ERROR:presence_xml:pres_apply_auth: in function get_final_notify_body
ERROR:presence:send_notify_request: in function apply_auth_nbody
ERROR:presence:notify: sending Notify not successful
ERROR:presence:publ_notify: Could not send notify for presence
---------------------------------------------------------------------------------------
Regards,
Kevin
_________________________________________________________________
手机也能上 MSN 聊天了，快来试试吧！
http://mobile.msn.com.cn/
Hi,
I want to get some feedback from the users regarding one of the TM
parameters: "noisy_ctimer" .
This parameter, is disabled, would try to let a call to ring for ever
(openser will never give internal timeout). But, the parameter is
automatically turned on (disregarding the script setting) in certain
conditions:
- parallel forking is done
- a failure route is set
- a failure callback is set by other module (like acc, cpl, dialog, etc)
- a fr_invite timeout was configured via AVP
- some reply was already received
- no other module explicitly asked for this (like siptrace, acc,osp)
Following some discussion on the tracker, there is large support for
removing this parameter as:
1) it is difficult to anticipate the final behaviour due complicated
logic
2) due all dependencies, in 99% of the case, the param will be
automatically turned on
3)it breaks the RFC3261, which make mandatory to have a final reply
form a stateful proxy
My question is:
Is anybody having a good point in not removing this parameter (and
having noisy_ctimer behaviour all the time)?
I'm pushing this question only on users list, as between the developers,
there is an consent in removing it ;)
Regards,
Bogdan
Hello everybody.
I have written to list these days, I am still having the same symptom, so I
apologize for writting again.
My OpenSER 1.3 installation running on Solaris Sparc is facing random and
unexpected crashes, in appearance related to timer process.
The last core presents the following backtrace
#0 0xfe977a04 in get_expired_dlgs (time=4233810208) at dlg_timer.c:194
#1 0xfe977540 in dlg_timer_routine (ticks=7980, attr=0x0) at
dlg_timer.c:210
#2 0x000a839c in timer_ticker (timer_list=0x15ec00) at timer.c:275
#3 0x000a80ec in run_timer_process (tpl=0x1b8088, do_jiffies=1) at timer.c
:357
#4 0x000a8668 in start_timer_processes () at timer.c:386
#5 0x00035ea8 in main_loop () at main.c:873
#6 0x000397c4 in main (argc=-4195024, argv=0x150e9c) at main.c:1372
Thanks in advance for any hint you can give me.
Best regards.
Sergio Gutierrez
Hi people...
I am using the module dialog to finish a call.
http://www.openser.org/docs/modules/1.3 ... tml#AEN461
It is working...
I need that the openser send a BYE to CALLE, to CALLER and to itself...
The BYE to endpoints(CALLE and CALLER) is ok, but it not sending BYE to itself...
Somebody can help?
Thanks in advance...
---------------------------------
Abra sua conta no Yahoo! Mail, o único sem limite de espaço para armazenamento!
Okay, It's time to get things going on the SIP Express Bundle. I'm
stepping in to take the reins as project manager on this one so we can
get things rolling.
First please take a look at the project page:
http://www.iptel.org/bundle/project
Step 1 here, I'd like to verify a headcount of people working on this
project as of now. This doesn't mean people can't join up later, and it
certainly doesn't mean that I'm going to expect you to put more time
into this than you can commit, but we need to know where we stand.
Currently, on the project list, we have:
*
Jai: testing and installation work
*
ram: testing
*
SIP: testing (and now project management)
*
Jiri: debian, oob
*
Mike: testing and documentation
*
Stefan: SEMS
Are the people listed here still available to do these particular tasks?
Has anyone else volunteered time/resources on this project that hasn't
been listed here? If so, shoot me an email, and I'll add you to the
list. We need a people inventory so we know what roles we're missing.
For instance, I've heard a few people mention that they'd be willing to
donate a server to the cause so we have somewhere to test things upon. I
don't have those people listed, but that's certainly an area we're going
to need. Also, we've had varying reports of which direction we're going
-- ISO or Virtual Machine. For now, I think we should concentrate on an
ISO as that's going to be the most attractive to people for building a
ready-to-go hardware appliance, and it will probably be a little less of
a headache for creating a drop-in installation. However, I also think a
virtual machine should be on the list in the future, and once we get an
ISO ready, creating a virtual machine from that configuration should be
relatively straightforward.
However, on the list of people, I don't see anyone down for scripting an
install -- a kickstart disc or what have you. That's another area we're
lacking. If anyone has experience in that area, shoot me an email and
I'll add you to the list.
We need to focus. For this reason, we'll start small and work from
there. Do NOT expect this first SER bundle to have every feature you
could imagine in it, and don't get discouraged if your favourite feature
is missing. As the project grows, we'll most certainly be adding
capabilities and allowing a tailored install. But for now, the goal
should be to get things running and working first in a simple format and
then add on from there.
Having a bundle like this is perhaps the biggest step we can take toward
bringing SER to the masses and finally breaking down some of those
barriers that have kept people out of the project.
I'm looking forward to working with all of you on this project!
Neil
Hello,
I am using openser-1.2.2-notls. I want to send a sms thanks to a IM (I am using
Eyebeam, but i don't know if it's possible to make that with this software).
Thats why, i need your help to explain me how send a sms thanks to the sms
module in openser.
I put in my openser.cfg, following "if(!method==MESSAGE)" the function which is
on the documentation :
if (sms_send_msg_to_net("Orange"))
{
if (!t_reply("202", "yes sir, SMS sent over"))
{
# if replying failed, retry statelessly
sl_reply_error();
};
} else {
if (!t_reply("502", "Bad gateway - SMS error"))
{
# if replying failed, retry statelessly
sl_reply_error();
};
exit;
};
Openser is running good, my problem is thats I don't know how to formulate my
message in Eyebeam to send correctly my sms.
Thanks.
Hi,
I am working on project involving SER, SEMS and MediaProxy. Things works OK as configured. I am curious to know how I can generate RTCP message towards caller if the called UA is not generating one.
I appreciate your response.
Thanks,
Keyur Parikh
