Hi all,
I am working on the following scenario:
Our carrier sends all calls (SIP protocol) to my openser, which forwards
the calls depending on their destination number to four asterisk servers
(for load sharing reason - we're speaking of a roof of 300 concurrent
calls).
I have one number which leads to a conferencence (one speaker, multiple
listeners),
whoose number of callers will exceed the number of calls a single asterisk
will
hold. Therefore I want the openser to distribute the calls to this number to
all
four asterisk servers (to share the load).
My question is: how do I configure this on openser, as I have to send all
requests
from the same SIP session to the same asterisk?
Can anyone give me a hint on this?
Thanks in advance.
Andreas
Hi all,
I am having some problem with the configuration file buildsystem.
Whatever changes I make, it always creates only the basic hello world
configuration file only. I am using the latest package.
It also gives the following message
**** WARNING! Only helloworld is implemented!!!!
How do I include other feature packages like NAT and authentication.
Here's what i've done
This configure script will generate a new local configuration to
./local/default/config.m4.
======================
Press ENTER to accept default values.
SER Server IP address:
IP address to listen on (202.52.247.221): 192.168.2.2
Port to listen on (5060):
Public IP address of server (ENTER if same as listen IP):
Domain name for this SER installation (i.e. mydomain.com, def.
mytestser.org) : MYDOMAIN
SER installation path (/usr/local, i.e. modules in /usr/local/lib/ser/modules):
Usage: dbtype://readwriteuser:password@host/databasename
Database URL (mysql://ser:heslo@localhost/ser):
You may choose to turn on logging as found in the SER - Getting Started guide.
This logging can be turned on and off in a live environment, and we recommend
everybody to include the logging except in high-load environments.
(You can also later disable it from your config.m4)
Turn on logging (yes):
How much log possibilities to include (low/medium/high, default high):
You can base your configuration file on one of the feature packages available.
Currently, the supported packages are (gettingstarted sems)
gettingstarted : A set of basic configurations found in most setups
sems : A configuration file that enables SER as a
front-end for SEMS
You can also choose to include specific components within a feature
package (components).
And finally, you can choose to include no prepared features, just use
your own code in ./local.
Your choice of feature, choose only one,
default is gettingstarted (none, components or gettingstarted sems) ?
You have chosen the SER - Getting Started feature package. (See SER -
Getting Started document)
Which feature set do you want to base your configuration on:
helloworld : basic configuration
auth : authentication using mysql database
nat : NAT traversal handling
pstn : Functionality for PSTN integration
callfwd : basic call features like call forwarding
**** WARNING! Only helloworld is implemented!!!!
Your choice (default helloworld, auth, nat, pstn, callfwd): nat
You have chosen NAT traversal, do you want to use rtpproxy (iptel.org)
or mediaproxy (ag-projects)?
Your choice (default rtpproxy, mediaproxy): rtpproxy
Copying site templates to ./local/default...
The resulting ser.config doesn't include anything except the helloworld.
Thank you in advance.
Kumar
Hello,
The proper way to send Publish messages is described in RFC 3903 (see
section 4.1 for event refreshing event state publication).
If you don't include a Sip-If-Match header it is not considered a
refresh of the previous state and thus it does not rewrite the open
state previously published.
regards,
Anca
Hildebrando Trannin wrote:
>Hi Anca,
>
>Thanks for your answer. When I say that OFFLINE doesn't works is that I send
>a PUBLISH with the basic status CLOSED (after already sent others PUBLISH
>with status OPENED) and OpenSER doesn't send NOTIFY message to inform
>subscribers that that contact is now OFFLINE. According to your answer it
>happens because I'm not sending PUBLISH's with Sip-If-Match. Is it right? If
>no, how is the correct way to send PUBLISH? Just to complement, PUBLISH with
>expires = 0 that do UNPUBLISH is working fine.
>
>Regards,
> Hildebrando Trannin
>
>-----Mensagem original-----
>De: Anca-Maria Vamanu [mailto:anca@voice-system.ro]
>Enviada em: segunda-feira, 21 de maio de 2007 06:12
>Para: Hildebrando Trannin
>Cc: users(a)openser.org
>Assunto: Re: [Users] Presence Problem - Publish Offline
>
>Hello,
>
>What happens here is that the presence module receives a first Publish
>from your aplication (that is a Publish with no Sip-If-Match header)
>having the basic status closed. In this situation, it does not send
>Notify to its watches to prevent descovering that the user is in fact
>online by tracking packets.
>
>Hildebrando Trannin wrote:
>
>
>
>>Hi all,
>>
>>I was testing OpenSER presence functionality using eyebeam and a
>>softphone developed by my team. The OFFLINE state with eyebeam worked
>>perfectly, but with my softphone it didn't work. I set force_active =
>>1. XML sent by PUBLISH and OpenSER log are below. Can anyone help me?
>>
>>
>>
>I don't understand what you mean with the Offline state not working.
>Could you please give more details?
>
>
>
>>Thanks, Hildebrando
>>
>>*PIDF XML:*
>>
>>* *
>>
>><?xml xmlns="urn:ietf:params:xml:ns:pidf"
>>
>>entity="sip:hildebrando@voip.maritaca">
>>
>><presence>
>>
>><tuple id="">
>>
>><status>
>>
>><basic>closed</basic>
>>
>></status>
>>
>><note>offline</note>
>>
>></tuple>
>>
>></presence>
>>
>>The basic difference between my application and eyebeam is that
>>eyebeam uses *RPID XML *and I use *PIDF XML*.
>>
>>*OPENSER LOG:*
>>
>>* *
>>
>>3(26039) PRESENCE: update_presentity: The presentity status is
>>offline; do not send notify
>>
>>------------------------------------------------------------------------
>>
>>
>>
>>
>>
>regards,
>
>Anca Vamanu
>
>
>
>>_______________________________________________
>>Users mailing list
>>Users(a)openser.org
>>http://openser.org/cgi-bin/mailman/listinfo/users
>>
>>
>>
>>
>
>
>
Hi Ram,
Thanks for the note. I thought there may be some issues with SUSE regarding mysql since all the talk is about other Linux flavours. I will give it a try and see.
Thanks,
Cyp.
====
----- Original Message ----
From: ram <talk2ram(a)gmail.com>
To: Cyprian Clement <cyprian_clement(a)yahoo.co.uk>
Cc: "serusers(a)iptel.org" <serusers(a)iptel.org>
Sent: Sunday, 20 May, 2007 5:06:55 PM
Subject: Re: [Serusers] Does SER's MYSQL work in SUSE Linux?
On 5/18/07, Cyprian Clement <cyprian_clement(a)yahoo.co.uk> wrote:
Hello Community,
Does anyone know whether it's possible to install the current recommended MYSQL on SUSE Linux. I have a Machine with a SUSE installed on it. I have successfully installed SER 0.9.6 but now I would like to have MYSQL for authentication support. Does the SER's recommended MYSQL work with SUSE?. I only see the talk about Redhat and Debian so unsure if it works with SUSE.
Many thanks for in advance.
Hi
any linux with mysql and ser should support
try using mysql authentication
any problems post here
ram
Cyp.
----------
Yahoo! Answers - Got a question? Someone out there knows the answer. Try it now.
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
___________________________________________________________
What kind of emailer are you? Find out today - get a free analysis of your email personality. Take the quiz at the Yahoo! Mail Championship.
http://uk.rd.yahoo.com/evt=44106/*http://mail.yahoo.net/uk
Hi gyus,
I configure my openser to restrict the number of register with the same user using the function [max_contacts], and functioned perfectly.
# Allow no more than 1 contacts per AOR
modparam("registrar", "max_contacts", 1)
Whenever that a user tries to register using the user that already register, the system return the following message: "Registration error:503 - Service Unavailable"
I need to customize the message informing the user the reason of error, something as "user already registered" (softphone).
I effected some tests, but I did not have success. Something as:
if( t_check_status("503"))
{
t_reply("503","User already registered!!!");
exit;
}
Any sugestion ?
Regards
Hi guys!
Anyone going to VON Europe in Stockholm?!
I will be there, so if there it's interest, we can arrange an informal
users' meeting (or maybe a SER pub meeting :-) Jan has signaled his
interest of participating remotely if possible.
Regardless of users' meeting or not, I'm open to meeting anyone
interested, so ping me :-)
I'm staying at the Rica hotel next to the fairground and can thus easily
meet.
g-)
PS! For those of you who find it strange that SER is not present as an
exhibitor: That costs money and resources (in terms of volunteer
presence and preparation). As iptel.org only relies on sponsors and
part-time volunteers, and nobody has raised the topic on the mailing
lists, we won't be exhibiting :-)
I don't know if any of the sponsors of SER are present as exhibitors,
they may be.
Copy the list!
I don't understand your problem. The BYE will be caught by the loose route section of the config and relayed. The standard getting started should work fine.
g-)
------- Original message -------
From: flavio <flavio.patria(a)gmail.com>
Sent: 12.5.'07, 15:09
> 2007/5/12, Greger V. Teigre <greger(a)teigre.com>:
> > Flavio,
> > SER doesn't reply 200 OK to BYE message, the SIP UA does that. So, you
> > are fine, the BYE reaches the UA.
> > g-)
> >
>
> That's right.
>
> If my gateway send INVITE message to SER, it does proxy it to UAC reached!
> So UAC (SIP Phone) and Gateway (UAC in SIP scenario) are involved in a
> media session.
> If my gateway send BYE message to SER, it does not proxy it to UAC.
> So I could send reply (200 OK) to Gateway (It works fine, but is not
> solution!), but I cannot proxy BYE to UAC.
>
> How can proxy this?
>
> Thanks,
>
> Flavio
Hello all,
I have an issue with some SIP clients (like Linksys SPA 1001) that have not comply with
the "expires" parameter of the Contact header of a "200 OK" Registrar Response.
My SER conf :
modparam("registrar", "default_expires", 1800)
modparam("registrar", "min_expires", 300)
modparam("registrar", "max_expires", 1800)
Although the (200 OK) response contains the 'expires' parameter :
Contact: <sip:userb2@192.168.2.10:5061>;expires=300;received="sip:1.2.3.4:5061"
the SIP client ignores it and keeps sending REGISTERs every 5 sec (if configured so).
Is there a way for SER to reject these registrations with (423 Interval Too Brief),
according to RFC3261 - 21.4.17 (423 Interval Too Brief) &
10.3 (Processing REGISTER Requests).
The 'retry_after()' registrar modparam is not my case.
thank you,
Kostas