I realize that first message with different addresses is 401 Unauthorized
message from server.
In TLS message i have
WWW-Authenticate: Digest realm=89.216.xx.xxx as a server address
in TCP message i have
WWW-Authenticate: Digest realm=10.99.10.249
can this cause problem? how to change realm in
Hi all,
I am using opensips-1.9.1-tls vaersion. And opensips-cp-5.0.
I am able to see some changes in acc table after made calling between
clients.
But i did't see any changes in cdrs table.
I loaded dialog module and enabled cdr_flag in acc.
Please help me to solve this issue.
Here is my
Hello,
Actually, the ERROR:core:fixup_uint: bad number -1 error message was a
bug in the code, that it wouldn't accept negative numbers for the
gateway type ( as the docs suggest would match any gw type ).
I've just pushed a fix for this on 1.8, 1.9 and 1.10.
Best Regards,
Vlad Paiu
Hello,
While it may not be that straight-forward, you might want to take a look
at the dispatcher module.
The dispatcher module does full NAPTR and SRV lookups for the hosts in
the dispatcher table. So you could add your needed domains to the
dispatcher table and then in your OpenSIPS
That'll work. Thanks, Vlad.
- Jeff
On Tue, Aug 6, 2013 at 3:42 PM, Vlad Paiu vladp...@opensips.org wrote:
Hello,
While it may not be that straight-forward, you might want to take a look
at the dispatcher module.
The dispatcher module does full NAPTR and SRV lookups for the hosts in
Hello,
If you want to have a shared registration database, you might want to
look into the db_mode 3 mode of the usrloc module [1].
Still, this will most likely get slow if you have a large pool of
registered users, and also you'll run into some NAT issues.
Rather than actually sharing the DB,
Hello,
What are you thinking about more exactly here in terms of security ?
The OpenSIPS worker processes that listen for BIN replicated packages do
not perform any IP authentication by themselves, so if you leave those
UDP ports open from the outside, you are leaving yourself exposed to
Hello,
You also have to edit your init.d file so that in the section where the
OpenSIPS config is checked for proper syntax you are also using the new
/usr/local/opensips_proxy/etc/opensips/opensips_residential.cfg config
file.
Currently, it seems that in that section you still have the old
OpenSIPS project has now an official YUM repository providing RPM builds
for :
RedHat Enterprise
CentOS
Fedora
Scientific Linux
All maintained OpenSIPS versions are present on the repository,
including the freshly released 1.10 beta.
Visit http://yum.opensips.org/ for details,
I read in the release notes for 1.9 that WebSockets are now supported, but
I can find no information on this. I did see this page:
http://www.opensips.org/Documentation/Tutorials-WebSocket
But that is just about how to use OverSIP, which isn't really support, just
telling how to use another
Hello Vlad,
I tested and confirmed it is OK now.
Thanks.
Regards,
Takeshi
On Wed, Aug 7, 2013 at 4:52 AM, Vlad Paiu vladp...@opensips.org wrote:
Hello,
What are you thinking about more exactly here in terms of security ?
The OpenSIPS worker processes that listen for BIN replicated
11 matches
Mail list logo