Hi, Olaf!
Thanks for your reply. Could you please further explain on the connectivity
between those to DIFFERENT sip servers? If I wanna call using a softphone to
call from SER to SIPserver B, how should I make the call?
Thanks.
Best Regards,
Roa Yu
-----Original Message-----
From: Olaf Bergmann [mailto:Olaf.Bergmann@freenet-ag.de]
Sent: Wednesday, June 27, 2007 3:10 PM
To: roayu
Cc: serusers(a)lists.iptel.org
Subject: Re: [Serusers] How SER communicate to other SIP server
roayu wrote:
> I would like to find out is there anyway that the SER server can
> communicate to other SIP servers?
You could use SIP for this purpose. It has turned out to work pretty
well since all SIP servers implement it by design ;-)
> For instance, I have an account at SER
> and another account at SIPserver B. I would like to call from SER to
> SIPserver B, and vice versa. Is it workable? Or any additional devices
> needed in between these 2 SIP servers? If yes, could anyone give me some
> clues or guide to do so.
You might want to have a look at the documents section at
<http://iptel.org> , especially
<http://www.iptel.org/ser/doc/gettingstarted>.
HTH,
Olaf
Hi,
I download the ser software and I can compile it successfully on my
machine with Fedora core 4.
But when I tried to run it with the 'hello world ser.cfg' configuration file,
it reports "Floating point exception" error message.
Any body had similar error before? or any idea what is happening?
I tried to copy the compiled binary to other machines with FC4 , all gave
me the "Floating point exception" error.
any input will be appreacited!
-Bo
On Mittwoch, 27. Juni 2007, gaoqiang.qian(a)nokia.com wrote:
> Yes, I have the database in the msyql server by the openser_mysql.sh
> create command, I can see it.
> But I am not sure with the openser_mysql.sh create, is it enough for
> adding those two users openserro and openserrw in the database?
Normally this should be sufficient. But better check to be safe. Please reply
also to the mailing list, that others can see your questions and the answers
too.
Henning
Hi,
I did a little reading through the documentation at
openser.org looking for something like a "tutorial"
and couldn't find one,
is there any kind of tutorial like resource available?
Thanks,
Andres Paglayan
--"Harmony is more important than being right"
Bapak
Is there a way to have OpenSER try each NAPTR record when multiple are
returned?
4.3.2.1.5.5.5.5.5.5.1.mysite.enum. 0 IN NAPTR 100 15 "u" "E2U+sip"
"!^.*$!sip:+15555551234@server2" .
4.3.2.1.5.5.5.5.5.5.1.mysite.enum. 0 IN NAPTR 100 10 "u" "E2U+sip"
"!^.*$!sip:+15555551234@server1" .
4.3.2.1.5.5.5.5.5.5.1.mysite.enum. 0 IN NAPTR 100 25 "u" "E2U+sip"
"!^.*$!sip:+15555551234@server3" .
That would route the calls to server1 (order 100, preference 10) but if
server1 is not responding I would like it to move on and try server2.
-Jonathan
We are currently experiencing problems with our production OpenSER
(1.1.0) environment where the load on the server is steadily increasing
and the OpenSER response time increases drastically (e.g., 30+ seconds
for an internal call to ring).
Capturing the network traffic when this happens we have noticed that our
Asterisk (1.2.10) voicemail server is sending malformed CANCEL requests
to our OpenSER proxy. We are not certain whether this is a cause or an
effect of the load problems on the OpenSER server. Here is the SIP data
from the bad CANCEL request:
Session Initiation Protocol
Request-Line: CANCEL :u43974@128.59.59.215:5069 SIP/2.0
Method: CANCEL
[Resent Packet: False]
Message Header
Via: SIP/2.0/UDP 128.59.59.215:5069;branch=z9hG4bK6734835b;rport
Transport: UDP
Sent-by Address: 128.59.59.215
Sent-by port: 5069
Branch: z9hG4bK6734835b
RPort: rport
Route: <sip:128.59.59.199;lr=on;ftag=4FC702F4-7F812557>
From: <sip:43974@sip.columbia.edu;user=phone>
SIP from address: sip:43974@sip.columbia.edu
To: "Jim Rios" <sip:47891@sip.columbia.edu>;tag=4FC702F4-7F812557
SIP Display info: "Jim Rios"
SIP to address: sip:47891@sip.columbia.edu
SIP tag: 4FC702F4-7F812557
Contact: <sip:u43974@128.59.59.215:5069>
Contact Binding: <sip:u43974@128.59.59.215:5069>
URI: <sip:u43974@128.59.59.215:5069>
SIP contact address: sip:u43974@128.59.59.215:5069
Call-ID: c9a0135b-41273fb6-f7b6cea9(a)160.39.14.100
CSeq: 101 CANCEL
Sequence Number: 101
Method: CANCEL
User-Agent: Asterisk PBX
Max-Forwards: 70
Content-Length: 0
Accompanying this bad CANCEL request are the following error messages
recorded by OpenSER to syslog when it attempts to process it:
May 29 15:34:07 cocoa openser[892]: ERROR: parse_uri: bad uri, state 0 parsed: <:u43> (4) / <:u43974@128.59.59.215:5069> (26)
May 29 15:34:07 cocoa openser[892]: ERROR: parse_sip_msg_uri: bad uri <:u43974@128.59.59.215:5069>
May 29 15:34:07 cocoa openser[892]: xl_get_ruri: ERROR while parsing the R-URI
May 29 15:34:08 cocoa openser[892]: c9a0135b-41273fb6-f7b6cea9(a)160.39.14.100: route[0] CANCEL r-uri <<null>> from <sip:43974@sip.columbia.edu;user=phone> to <sip:47891@sip.columbia.edu>
May 29 15:34:08 cocoa openser[892]: ERROR: parse_uri: bad uri, state 0 parsed: <:u43> (4) / <:u43974@128.59.59.215:5069> (26)
May 29 15:34:08 cocoa openser[892]: ERROR: parse_sip_msg_uri: bad uri <:u43974@128.59.59.215:5069>
May 29 15:34:08 cocoa openser[892]: loose_route: Error while parsing Request URI
May 29 15:34:08 cocoa openser[892]: ERROR: parse_uri: bad uri, state 0 parsed: <:u43> (4) / <:u43974@128.59.59.215:5069> (26)
May 29 15:34:09 cocoa openser[892]: ERROR: parse_sip_msg_uri: bad uri <:u43974@128.59.59.215:5069>
May 29 15:34:09 cocoa openser[892]: WARNING: do_action:error in expression
May 29 15:34:09 cocoa openser[892]: ERROR: parse_uri: bad uri, state 0 parsed: <:u43> (4) / <:u43974@128.59.59.215:5069> (26)
May 29 15:34:09 cocoa openser[892]: ERROR: parse_sip_msg_uri: bad uri <:u43974@128.59.59.215:5069>
May 29 15:34:09 cocoa openser[892]: ERROR: parse_uri: bad uri, state 0 parsed: <:u43> (4) / <:u43974@128.59.59.215:5069> (26)
May 29 15:34:10 cocoa openser[892]: ERROR: parse_sip_msg_uri: bad uri <:u43974@128.59.59.215:5069>
May 29 15:34:10 cocoa openser[892]: ERROR: parse_uri: bad uri, state 0 parsed: <:u43> (4) / <:u43974@128.59.59.215:5069> (26)
May 29 15:34:10 cocoa openser[892]: ERROR: parse_sip_msg_uri: bad uri <:u43974@128.59.59.215:5069>
May 29 15:34:10 cocoa openser[892]: alias_db_lookup: Error while parsing Request-URI
While the malformed packet is likely the fault of the Asterisk server
(we see no packets from OpenSER to Asterisk with the sip protocol
missing from the URI), we are wondering if OpenSER errors out in a bad
way when it tries to process this packet, possibly entering into some
sort of loop that is causing the load to go through the roof.
It is also unclear to us why the Asterisk voicemail server would be
responding with a cancel. In our packet capture we see no record of a
request initiated by the Asterisk server that it would be sending a
CANCEL for.
Any insight that could be offered into this problem would be greatly
appreciated.
Thx,
David Coulthart
On Mittwoch, 27. Juni 2007, gaoqiang.qian(a)nokia.com wrote:
> When I start the debug model, I have got some error of connecting mysql
> database, it said something like
> "mysql:openserro.openserro@localhost/openser" not found in the pool.
> Could you tell me what could be the reason?
> I can not find the achieves about this issues in the mail achieves.
> Could you point out me some links?
Hello Qiang,
have you setup a mysql database and create the right tables with the database
setup script?
You find more informations about openser in the openser wiki on
www.openser.org. If you want to use openser in a production environment, you
should install a recent version, e.g. the latest stable release 1.2.1.
Cheers,
Henning
> Hi,
> I am working in Nokia and now response for setup a openser sip server
> providing sip proxy and registrar for one of our project. After I have
> install the openser Sip server by following all the steps from CVS
> installation guide. When I start the sip server with openser start
> command, I always got:
> 'openser' start: /etc/init.d/openser
> Openser failed to start
> Strating open sip router:
> Listen on
> Udp:
> ...
> Aliases:
> Tcp:
> ...
> It seems the starting is failed. So could you tell me what could be
> the reason? Or could you please tell me is there someway I can test if
> my openser is running now?
> Thanks.
>
Hi, there!
I would like to find out is there anyway that the SER server can communicate
to other SIP servers? For instance, I have an account at SER and another
account at SIPserver B. I would like to call from SER to SIPserver B, and
vice versa. Is it workable? Or any additional devices needed in between
these 2 SIP servers? If yes, could anyone give me some clues or guide to do
so.
Thank you.
Best Regards,
Roa yu