Hi All,
I am new to SER/OpenSER and I have received much help and in return, I am
offering free Dynamic DNS services to whoever is interested. To find out
more go to http://www.t4tm.net, signup and enjoy the benefits.
Tracy
_________________________________________________________________
Got something to buy, sell or swap? Try Windows Live Expo
ttp://clk.atdmt.com/MSN/go/msnnkwex0010000001msn/direct/01/?href=http://exp…
When I add with serctl some alias to the DB, only after some time it
appears written in the aliases table of DB. How can I force that to be
simultaneously written in DB? Any parameter I have to tune in ser.cfg?
Regards,
Ricardo.
>> 2) t_relay will return several error codes:
>> -1 = no transaction created -> need to use sl_* functions
>> -2 = transaction created, relay failed -> may destroy
If I understand this correctly, the difference between these two
return codes really has to do with who it is that cares about it...
-2 relates to this exact call, at this exact moment,
chances are the very next call the openser box handles will be OK.
It looks to me like -1 means serious trouble, for the entire call
switching platform. It sounds like it could happen because of a
resource shortage (memory), possibly because of a bug in openser,
or a bug in the openser.cfg. If you get -1 once, then the chances that
you'll get the same code on the next call are very high.
Let's say we've run out of memory. Then, what tools are available at
the openser.cfg script level that can handle this? Is there a way to
force some internal garbage collection? Or to do a warm-restart
(e.g., trash all transactions, but not registrations)?
My point here is this: if I'm right about -1 meaning serious trouble
that is likely to mean serious problems from now on, then this is a more
general problem than just t_relay, and much bigger than just handling this
one call or a call to one particular neighbour.
It's true that the application may halt and catch fire, but there are
plenty of errors that are catchable by openser and the larger question
seems to be: what do we do then?
If there were script-level tools that could be used to try to manage
the failure, possibly clean up (in a large way) and try to keep going,
then maybe we should have openser_failure route blocks that the
user can register with openser to handle various errors.
Thanks,
-mark
Hi all,
there are some topics largely discussed lately on the mailing list; in
order to fix them problems first we need to find a solution for logical
point of view - and here I think that several opinions are better than
one :)
In order to have failover based on serial forking, it is mandatory to be
able to detect from script if the initial t_relay() fails. The problem
is that now t_relay() masks any error by internally generating an error
SIP reply. Of course, it can be internal errors (like lack of memory),
msg errors (parse errors) or transport errors (DNS failed, send/connect
failed, etc).
Now, disabling the auto replying in case of error is not a problem. The
problem is how to handle the errors from the script; two make
distinction between the error classes a listed above will not be the
purpose of this email ( I will open another one for this ;) ). What is
important here is to be able to properly resume from the point were the
error popped up. What I mean is: the t_relay() function builds the
transaction and sends the requests. If the error occurred during
transaction creation, from script, you will had to use only stateless
functions to send err. replies. If the transaction was already created
and the error popped up during relaying stage, you will need from the
script to take care of the transaction and either destroy it, either
reply it.
Based on this, here is what I suggest:
1) have a new param for disabling the auto reply in t_relay()
2) t_relay will return several error codes:
-1 = no transaction created -> need to use sl_* functions
-2 = transaction created, relay failed -> may destroy
transaction, reply via TM with error, trigger failover.
any comments on this ?
regards,
bogdan
Sorry for double posting.
I forgot to put subject line in previous posting.
Hi, all.
I just installed serweb and it is working however there is are no calls
shown under "accounting" tab, saying "no calls".
Mysql table has call records with matching flag set in ser.cfg. Records
seem to be correct for numerous test calls made. It just that serweb
doesn't seem to pull those records out of mysql at all.
Any idea where I should look at?
Thanks in advance.
--
Chahn John Kim
Hi, all.
I just installed serweb and it is working however there is are no calls
shown under "accounting" tab, saying "no calls".
Mysql table has call records with matching flag set in ser.cfg. Records
seem to be correct for numerous test calls made. It just that serweb
doesn't seem to pull those records out of mysql at all.
Any idea where I should look at?
Thanks in advance.
--
Chahn John Kim
How can I prevent a dialled username (without dialling the domain) to
ring a phone registered with that username?
I pretend to use a multi-domain architecture where apart from aliases of
users, only dialling with username@domain will ring registered phones.
Thanks,
Ricardo.
Dear Members!
I am very new to This VOIP Technology. I have just installed the Openser. I
am now able to Do the Communication between the users who are resisterd in
the proxy but how do I establish the calls to another proxy.I mean Lets
consider I have two Proxies and I want a user of Proxy 1 to coomunicate
with a user of Proxy2.How will I edit the configuration files so that I can
achieve that.
And One more thing.How do I achieve the Nat Traversal in openser.Let us
consider I am running my Server in 24.10.65.90(Public and static).and I have
a Lan connection In the client side, When the two phones from the same LAN
want to talk with each other by using the proxy at 24.10.65.90, Its not
possible.I got Disconnected from the internet connection and also when I
tried this.If I am calling to a Phone other than this LAN using proxy at
24.10.65.90, I am able to establish.What may be the problem to the previous.
I hope I have explained my problems in a user Understandable way. I am
expecting a sooner reply.
Thanking you In Advance,
Shiva
When I add my dictionary.openser to Freradius v 1.0.1-3 on Centos 4.3,
and after following all the steps outlined on the webpage:
http://www.openser.org/docs/openser-radius-1.0.x.html
When I get to testing the configuration, radiusd -X
i get this:
read_config_files: reading dictionary
Errors reading dictionary: dict_init: No ATTRIBUTE "Sip-Method" defined
for VALUE "Other"
Errors reading radiusd.conf
Unfortunately freeradius.org is now a parked domain (seems like a rather
large oversight on their part...) so I can't ask them..
Has anyone here ever seen an issue like this?
BTW, I'm using openser 1.1.0-notls compiled from source. Not that seems
to apply here though.