Hi All,
Can anyone tell me If I can generate Radius record for Instant Messaging using
Iptel .
Thanks in Advance.
Techno
---------------------------------
Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. Great rates starting at 1¢/min.
Hello,
I have an Openser server with TLS support running ok. However, when a UA
client tries to register with it, it gives off this error:
7(63031) tls_accept: Error in SSL:
7(63031) tls_error: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong
version number
I ran SSLDUMP and got these logs:
8 1 2.4157 (2.4157) C>S SSLv2 compatible client hello
Version 3.1
cipher suites
TLS_RSA_WITH_RC4_128_MD5
TLS_RSA_WITH_RC4_128_SHA
TLS_RSA_WITH_3DES_EDE_CBC_SHA
SSL2_CK_RC4
SSL2_CK_3DES
SSL2_CK_RC2
TLS_RSA_WITH_DES_CBC_SHA
SSL2_CK_DES
TLS_RSA_EXPORT1024_WITH_RC4_56_SHA
TLS_RSA_EXPORT1024_WITH_DES_CBC_SHA
TLS_RSA_EXPORT_WITH_RC4_40_MD5
TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5
SSL2_CK_RC4_EXPORT40
SSL2_CK_RC2_EXPORT40
TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA
TLS_DHE_DSS_WITH_DES_CBC_SHA
TLS_DHE_DSS_EXPORT1024_WITH_DES_CBC_SHA
8 2.4163 (0.0005) S>C TCP FIN
8 2.4165 (0.0002) C>S TCP FIN
Any idea of what might the problem be? Help would be greatly appreciated.
Thanks!
Hi,
I'm using ser proxy server the latest version 0.9.I'm running ser on ipv6 PC ,listening on ipv6 address whihc i configured in ser.cfg.
Using some other clients which are running on ipv6 PC's can able to call from UDP-UDP properly.AS ser runs on both UDP and TCP ,the TCP-TCP calls also should go properly.
But the error 'tcp_blocking_connect:(22) Invalid Argument' is coming when the next hop from the proxy is TCP.
Kindly support for this problem.
Regards,
Jayasree
Hello Everybody,
we are pleased to announce that first OpenSER Summit will take place in
Berlin, on the 8th November. The summit is hosted inside the VoN Europe
Exhibition. The participants registered via OpenSER will have free
access to summit and exhibition. A registration form will be available
very soon on the web site, as an alternative you can send email to
team(a)openser.org with your details.
We are looking to network people around OpenSER, to share experiences
and build business relations, among invited persons are executives from
major communication companies. The board members and main developers
will be there as well. There is no need for other words about VoN
(http://www.von.com), is the leading conference in VoIP and we are glad
that we can tie up together the OpenSER Summit.
To be able to cover organizing expenses, we are looking for
sponsorships. The sponsors will get the opportunity to held a
presentation and do advertising inside the event. Banners will be
published on the OpenSER web site and event's page. We will be able to
offer to sponsors free passes to full conference (all presentations at
VoN, lunches, dinners and parties) and other discounts.
If you are interested to be a sponsor of the event, please contact us at
team(a)openser.org and we will give you more details about the conditions
and offering you will get.
More details will be published on http://www.openser.org site as soon as
updates come.
Looking forward to meet you there,
Daniel
Hi,
I'm using ser proxy server the latest version 0.9.I'm running ser on ipv6 PC ,listening on ipv6 address whihc i configured in ser.cfg.
Using some other clients which are running on ipv6 PC's can able to call from UDP-UDP properly.AS ser runs on both UDP and TCP ,the TCP-TCP calls also should go properly.
But the error 'tcp_blocking_connect:(22) Invalid Argument' is coming when the next hop from the proxy is TCP.
Kindly support for this problem.
Regards,
Jayasree
The information contained in this e-mail message and/or attachments to it may
contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail immediately and permanently delete the message and any attachments.
Hello,
I'm sorry for a big lag. I test system yesterday on other linux kernel (2.6) and obtain the same results. In this case i suppose,
that this problem don't bases on system socket implementation. I tested openser on other numbers of tcp workers and obtain next results:
20 children: 2 sockets don't flushed (all had data on receive and send queues), cpu usage is above 48% on each of 2 openser processes,
one of them invokes poll function in tls_server.c, other trying to write into tls socket.
1 child: 1 socket don't flushed (receive queue not empty, send queue empty), cpu usage is 90% on one process.
100 children: no problems, all work correctly
2 children: no problems.
>Hello,
>
>On 09/29/06 16:06, serega wrote:
>> Hi Klaus and all other who read this.
>>
>> It's not a problem of tcp socket - yesterday i rewrite gateway config for fowarding directed to extgateway requests to gateway itself.
>> In tcp this problems not occured, but after i switched on tls, i see overfilled queues again. In that case i haven't extgateway, communications with
>> remote sockets and etc. Did anybody test openser whith big payload? I think this problem occurs because in my case i have big traffic and several process that simultaniously use tls. Did anybody have the same problem?
>>
>
>If you increase the number of the TLS/TCP workers do you get same
>results? In case of TLS, there is more CPU used because of
>encryption/decryption. How is the CPU usage in teh system while you are
>testing?
>
>As Klaus said, the management of socket queue is done by OS.
>
>Cheers,
>Daniel
>
>>
>>> Hi Serega!
>>>
>>> I'm not sure - just a guess. openser uses "worker threads". This worker
>>> threads get a SIP message from the listener thread, process them, and
>>> then they send them.
>>>
>>> If for some reason the sending fails - e.g. the gateway sends via
>>> TCP/TLS to extgateway and extgateway's receiving queue is full. Then
>>> gateway's sending buffer gets full and the threads wait until they can
>>> send. Thus, as the threads are all busy, also the receiving queue of
>>> gateway gets full. I guess after some time the threads give up sending
>>> and will read again.
>>>
>>> The question is: why does the sending buffer gets full? Where is gateway
>>> sending the messages to?
>>>
>>> The sending queue must not get flushed. The queue is in the OS, not in
>>> openser. As TCP guarantees that there is no loss/reordering the TCP
>>> stack must not flush the queue.
>>>
>>> regards
>>> klaus
>>>
>>> serega wrote:
>>>
>>>> Hi all.
>>>>
>>>> I have next problem while using openser with tls. System consists of
>>>> sip statefull server (in next time, simply, server) and stateless sip
>>>> gateway (gateway). Server used for connect to jabber server. Server
>>>> contains rewrote jabber module logic and also use presence module.
>>>> Gateway used to connect to other sip gateway (extgateway) via tls
>>>> protocol. Gateway use 1.1 openser version and doesn’t contain changed
>>>> code. When server together with gateway restarts and server in its
>>>> database contains above 260 subscriptions (in watcherinfo table) i
>>>> have error. Socket used by gateway to connect with extgateway
>>>> contains in receive and sent queues a lot of data (above 50kByte on
>>>> each sides). This data never flushed out. This happens because after
>>>> restart sip server through gateway send notifications to extgateway.
>>>> When I attached using gdb to process that send data, I saw that it
>>>> was in infinity loop because tls library returns SSL_ERROR_WANT_WRITE
>>>> and I think it’s correct because we have overfilled send queue. In
>>>> this case I don’t interest why receive queue not empty (I think it
>>>> happens because sending process have got block on socket). But I
>>>> don’t understand why sent queue not flushed. I test this behavior
>>>> using tcp – all was correct. Socket not closed by other side because
>>>> this status can be unchanged above one day. Anybody can help me? Why
>>>> this happens?
>>>>
>>>> I use openssl-0.9.8c and redhat os (Linux xdevel1 2.4.21-4.ELsmp #1
>>>> SMP Fri Oct 3 17:52:56 EDT 2003 i686 i686 i386 GNU/Linux). Computer
>>>> have too Pentium 4 processors).
>>>>
>>>>
>>>> Gateway.cfg (sip.qa.hbex.com – gateway address):
>>>>
>>>> # # $Id: router_qa.cfg,v 1.1 2006/08/02 18:14:34 ilya Exp $ # #
>>>> simple quick-start config script #
>>>>
>>>> # ----------- global configuration parameters
>>>> ------------------------
>>>>
>>>> debug=9 # debug level (cmd line: -dddddddddd)
>>>> log_facility=LOG_LOCAL0 fork=yes log_stderror=yes # (cmd line: -E)
>>>>
>>>>
>>>> check_via=no # (cmd. line: -v) dns=no # (cmd. line: -r)
>>>> rev_dns=no # (cmd. line: -R) children=20
>>>> fifo="/tmp/openser_fifo" server_signature=no
>>>>
>>>> fifo_db_url="mysql://root:@localhost/openser"
>>>>
>>>> listen = udp:sip.qa.hbex.com:5060 #incoming sip server address listen
>>>> = tcp:sip.qa.hbex.com:5060
>>>>
>>>> #tls address disable_tls = 0 listen = tls:sip.qa.hbex.com:5061 listen
>>>> = udp:sip.qa.hbex.com:5061
>>>>
>>>> tls_certificate = "/ home/inop/ex.com-cert.pem" tls_private_key =
>>>> "/home/inop/ex.com-privkey.pem" tls_ca_list =
>>>> "/home/inop/ex.com-calist.pem" tls_require_client_certificate=0
>>>> tls_verify_client=0 tls_verify_server=0
>>>>
>>>> # ------------------ module loading
>>>> ---------------------------------- loadmodule
>>>> "/home/interop/openser/lib/openser/modules/rr.so" loadmodule
>>>> "/home/interop/openser/lib/openser/modules/xlog.so" loadmodule
>>>> "/home/interop/openser/lib/openser/modules/textops.so" loadmodule
>>>> "/home/interop/openser/lib/openser/modules/maxfwd.so" loadmodule
>>>> "/home/interop/openser/lib/openser/modules/sl.so" loadmodule
>>>> "/home/interop/openser/lib/openser/modules/mysql.so" loadmodule
>>>> "/home/interop/openser/lib/openser/modules/tm_unchanged.so"
>>>> loadmodule "/home/interop/openser/lib/openser/modules/usrloc.so"
>>>> loadmodule "/home/interop/openser/lib/openser/modules/registrar.so"
>>>>
>>>> # ----------------- setting module-specific parameters
>>>> --------------- modparam("registrar", "default_expires", 120)
>>>> modparam("registrar", "use_domain", 1)
>>>>
>>>> modparam("usrloc", "use_domain", 1) modparam("usrloc", "db_mode",
>>>> 0) # Uncomment this if you want to use SQL database # for persistent
>>>> storage and comment the previous line #modparam("usrloc", "db_mode",
>>>> 2)
>>>>
>>>> # add value to ;lr param to make some broken UAs happy modparam("rr",
>>>> "enable_full_lr", 1) modparam("maxfwd", "max_limit", 10) #
>>>> ------------------------- request routing logic -------------------
>>>> # main routing logic route{ if (!mf_process_maxfwd_header("10")) {
>>>> sl_send_reply("483","To Many Hops"); drop(); }; if (dst_port==5061) {
>>>> if (search("^To:.*@.*cmnicator.com") || search("^To:.*@.*cihb.com"))
>>>> { # rewrite destination and forward to jabber (sip server) route(1);
>>>> return; }; sl_reply_error(); return; } if (method=="REGISTER") {
>>>> xlog("XXX: saving location msg=$mb\n"); if(!save_noreply("location"))
>>>> { log("XXX: Error saving location!\n"); sl_reply_error(); }
>>>> sl_send_reply("200","OK"); return; } if
>>>> (search("^To:.*@.*cmnicator.com") || search("^To:.*@.*cihb.com")) {
>>>> #forward to self route(3); return; } ##forward to ext gateway
>>>> route(2); }
>>>>
>>>> route[1]{ if (method!="MESSAGE" && method!="SUBSCRIBE" &&
>>>> method!="NOTIFY") { log("XXX: Request not forwarded to sip
>>>> server!\n"); sl_send_reply("202","Accepted"); return; }
>>>> t_on_reply("1"); record_route();
>>>>
>>>> if(!lookup("location")) { if (method!="SUBSCRIBE") { log("XXX: only
>>>> subscribes are processed for user that are not registered\n");
>>>> sl_reply_error(); return; }
>>>> subst_uri('/(.*)@(.*)/\1#\2*jabber.qa.im.hb.com@jabber01.qa.im.hb.com/ig');
>>>> if(!t_relay()) { log("XXX: error forwarding jabber01...\n");
>>>> sl_reply_error(); return; } else { sl_send_reply("200","OK"); return;
>>>> } } else { log("XXX: forwarding to the address of record...\n");
>>>> if(!t_relay()) { log("XXX: error forwarding to address of record
>>>> \n"); sl_reply_error(); return; } else { sl_send_reply("200", "OK");
>>>> return; } }
>>>>
>>>> }
>>>>
>>>> # forwarding to external gateway route[2]{ log("XXX: rewriting
>>>> headers\n");
>>>> subst('/^(From:[^@#]*)#([^@]*)\*jabber.qa.im.hb.com@jabber...qa.im.hb.com(.*)/\1@\2\3/ig');
>>>>
>>>> subst('/^(Contact:[^@#]*)#([^@]*)\*jabber.qa.im.hb.com@jabber...qa.im.hb.com(.*)/\1@\2\3/ig');
>>>>
>>>>
>>>> if(!forward("tls:43.123.141.166:3000")) { log("XXX: Error forwarding
>>>> to external gateway!\n"); sl_reply_error(); } else {
>>>> sl_send_reply("200", "Accepted"); }; }
>>>>
>>>> # forwarding to SELF route[3]{ log("XXX: rewriting headers\n");
>>>> subst('/^(From:[^@#]*)#([^@]*)\*jabber.qa.im.hb.com@jabber...qa.im.hb.com(.*)/\1@\2\3/ig');
>>>>
>>>> subst('/^(Contact:[^@#]*)#([^@]*)\*jabber.qa.im.hb.com@jabber...qa.im.hb.com(.*)/\1@\2\3/ig');
>>>>
>>>>
>>>> log("XXX: about to forward to self\n");
>>>> if(!forward("tcp:sip.qa.hbex.com:5061")) { log("XXX: Error forwarding
>>>> to self!\n"); sl_reply_error(); } else { sl_send_reply("200",
>>>> "Accepted"); }; }
>>>>
>>>> # this is executed for replies onreply_route[1]{
>>>> subst('/^(To:[^@#]*)#([^@]*)\*jabber.qa.im.hb.com@jabber...qa.im.hb.com(.*)/\1@\2\3/ig');
>>>>
>>>> subst('/^(Contact:[^@#]*)#([^@]*)\*jabber.qa.im.hb.com@jabber...qa.im.hb.com(.*)/\1@\2\3/ig');
>>>> route(2); }
>>>>
>>>>
>>>>
>>>> _______________________________________________ Users mailing list
>>>> Users(a)openser.org http://openser.org/cgi-bin/mailman/listinfo/users
>>>>
>>>
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users(a)openser.org
>> http://openser.org/cgi-bin/mailman/listinfo/users
>>
>>
>
In the log file (OpenserAdmin) I see my registered phones with different
addresses. I would like to know what it means:
a. public IP with a port number
sip:7111@59.124.230.151:65129
b. private IP with a port number
sip:7112@192.168.10.75:5060
c. private IP with NO port number
sip:7113@192.168.10.45
d. Eyebeam with public IP with port and rinstance (???)
sip:7311@203.70.36.126:65321;rinstance=059afa5458d206a7
e. Gizmo phone, secondary number should be 7312.
sip:17476063396@proxy01.sipphone.com:5060
d. and e. are on my desktop connected to a ADSL router, which obviously
makes the NAT to 203.70.36.126, my current public IP on that line.
b and c are also on a private network and connected through the same
ADSL router as a. Why a has a public IP, while b and c not? Why have all
a port, but c not ???
bye
Ronald
I got two places to look: /var/log/openser and the output of ngrep.
I would like to see only one case of one phone / phone call. Is there a
tool to filter that out?
Has anybody made a transfer from the ngrep to a mysql database? I expect
that this would be easier to select single cases.
Where are and how must I set-up openser to get CDRs ?
bye
Ronald Wiplinger
Hi,
Two questions about the uac_redirect module:
1. If I extract contacts from a 302 with two contacts having the same
q-value by using get_redirects("1:1"), which one of the contacts is
selected? The first one? The last one?
2. If I apply a filter rule like:
modparam("uac_redirect", "default_filter", "deny")
modparam("uac_redirect", "accept_filter", "sip:.+@foo.bar.com")
and I get a 302 with a Contact, say, "sip:foo@some.other.tld", then the
module logs this error: "ERROR:uac_redirect:get_redirects: get contact
from shm_reply branch 0 failed". I'd say if zero contacts are extracted
from branches due to filters, it's not really an error. Any suggestions
for a better error handling?
Andy
Hi,
I was just wondering if the check_route_param("") works on
record_route_preset Routes?
It never hits when my Route: are, f.ex like
xxx.xxx.xxx.xxx:<port>;nat=yes
Is this true?
br hw
--
Helge Waastad
Senior Engineer
Systemavdelingen
Smartnet
