sr-users May 2007

sr-users@lists.kamailio.org

164 participants
295 discussions

[Serusers] Call Forward Redirection By server(SER)

by Cyprian Clement

Hello Community, I have managed to setup my SER to do serial forking(CFU) by simply intercepting the incoming INVITE and generating a new INVITE to a user that is different from the one contained in the original invite. This means the user ID of the Request URI generated by the SER is different from that of the original/received RURI. I am currently working on the Call Forward (CFU, CFB, CFNA) scenarios. I would like to configure the SER in such a way that it generates the 302 message back to the caller and this 302 contains the contact of the third party that the caller needs to get in touch with. Basically, the caller should generate a new INVITE to this third party since the intended target has had his phone activated with the CF feature. I currently managed to get the SER do the serial forking(i.e. without sending back the 302) using the AVPops madule as instructed in the User Guide. Does the AVPops do the redirection too? if yes, then I will really appreciate to hear your helping info on how to achieve this. Many thanks in advance. Cyp. --------PS: if anything is unclear I can clarify. ___________________________________________________________ Yahoo! Answers - Got a question? Someone out there knows the answer. Try it now. http://uk.answers.yahoo.com/

17 years, 7 months

Re: [Users] How to log the username of caller and callee to acc table?

by Bogdan-Andrei Iancu

Charles, glad to help - all the changes between the versions are documented on the web site. See: http://www.openser.org/dokuwiki/doku.php/install:1.1.x-to-1.2.x regards, bogdan Charles Wang wrote: > Dear Bogdan, > > Thank you for your important information. > It helps me to solve my problems. > I add four fields to DB and use db_extra to insert them. > > modparam("acc", "db_extra", "from_uri=$fu ; sip_from=$hdr(From) ; > to_uri=$tu ; sip_to=$hdr(To)") > > > > Best regards, > Charles > > 2007/5/18, Bogdan-Andrei Iancu <bogdan(a)voice-system.ro > <mailto:bogdan@voice-system.ro>>: > > Hi Charles, > > in openser 1.2 only a few mandatory info about the SIP transaction are > accounted. If you want something more, use the the extra accounting. > For, example, for db, to get the from uri, so: > > modparam("acc","db_extra","from_uri=$fu ; sip_from=$hdr(From)") > > Note, you need to create the new columns in the acc table. See > http://www.openser.org/docs/modules/1.2.x/acc.html#ACC-EXTRA-ID > > regards, > bogdan > > Charles Wang wrote: > > Hi all, > > > > I ever used SER and I know it will save the From information such as > > 101(a)192.168.11.200 <mailto:101@192.168.11.200> > <mailto:101@192.168.11.200 <mailto:101@192.168.11.200>> to > sip_from or from_uri > > in its acc table. > > But in my openser, I also setup the acc module. Where is my > caller info? > > > > I can find a lot of number such as "2806655523" in my from_tag. > > I wanna store the caller and callee info in my acc table when I > make > > an internal call or an external call. > > > > Can anybody kind to help me to solve it? or give me some tips > please. > > PS: I got this openser.cfg from http://www.sipwise.com/wizard > <http://www.sipwise.com/wizard>. > > > > Best regards, > > Charles > > > > > -- > > Best Regards > Charles

17 years, 7 months

Re: [Users] Not able to add users

by Henning Westerholt

On Freitag, 25. Mai 2007, you wrote: > Hi Henning, > > I have added the mysql module into my configuration file. Can you please > tell me how to and where to look for log files, indicating any problems > with database connectivity > > Thanks, > Kiran. Hi, increase the debug level in your config, and look in your system logfile (/var/log/messages on debian, could differ on your system) for messages. Henning P.S: please CC to the list

17 years, 7 months

Re: [Users] failure_route problem

by Klaus Darilion

openser uses syslog logging. The destination of the logs is distribution dependent. E.g. debian based -->/var/log/syslog, redhat based --> /var/log/messages. Read http://openser.org/dokuwiki/doku.php/tutorials:debug-syslog-messages for details about to configure logging. regards klaus ps: please cc the list Yago Bargalló wrote: > Sorry, but I've tried to use xlog but I don't know where logs are printed. In which file does logs saved?? > > Thanks...!! > > > -----Mensaje original----- > De: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] > Enviado el: jueves, 24 de mayo de 2007 14:42 > Para: Yago Bargalló > CC: users(a)openser.org > Asunto: Re: [Users] failure_route problem > > Add xlog statements to your config and watch syslog. This is how you can > trace if the failure route is executed. Further you can set debug=4 to > see debug messages of openser. > > Further watch the SIP traffic using ngrep and dump it here > > regards > klaus > > > > > Yago Bargalló wrote: >> Hello, >> >> First of all thaks to Kraus for his quick reply on my last question. However I can't do openser work fine. >> >> I'm trying to use failure_route as follows, can anybody tell me which could be the problem?? >> >> >> >> (...) >> >> modparam("tm", "fr_inv_timer" , 10) >> >> >> >> # timer for response to a request >> >> modparam("tm","fr_timer", 4) >> >> >> >> >> >> # ------------------------- request routing logic ------------------- >> >> >> >> # main routing logic >> >> >> >> route{ >> >> (...) >> >> if (uri==myself) { >> >> (...) >> >> # Redirecciono cap a l'asterisk si marquen una extensió que comença per 3 >> >> >> >> if(uri=~"sip:2[0-9]+@" && method=="INVITE") { >> >> t_on_failure("1"); >> >> } >> >> (...) >> >> route(1); >> >> } >> >> >> >> >> >> route[1] { >> >> # send it out now; use stateful forwarding as it works reliably >> >> # even for UDP2TCP >> >> if (!t_relay()) { >> >> sl_reply_error(); >> >> }; >> >> exit; >> >> } >> >> >> >> failure_route[1]{ >> >> rewritehostport("172.16.51.160"); #asterisk >> >> rewriteuser("2002"); >> >> append_branch(); >> >> t_relay(); >> >> exit; >> >> } >> >> >> >> >> >> With this openser.cfg the call is cancelled after fr_inv_timer and failure_route[1] doesn't work but, however, if I do this: >> >> >> >> route{ >> >> (...) >> >> if (uri==myself) { >> >> (...) >> >> # Redirecciono cap a l'asterisk si marquen una extensió que comença per 3 >> >> >> >> if(uri=~"sip:2[0-9]+@" && method=="INVITE") { >> >> à rewritehostport("172.16.51.160"); #asterisk >> >> à rewriteuser("2002"); >> >> t_relay(); >> >> exit; >> >> } >> >> (...) >> >> route(1); >> >> } >> >> >> >> If I use this the call is redirected to my asterisk but using the failure_route as my first openser.cfg it does't work. >> >> >> >> Which is my problem?? >> >> >> >> Thanks.... >> >> >> >> >> >> >> >> >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Users mailing list >> Users(a)openser.org >> http://openser.org/cgi-bin/mailman/listinfo/users > >

17 years, 7 months

RE: [Users] Interaction Presence Agent - Presence User Agent

by Schumann Sebastian

Perfect! Thanks for quick answer, Anca! Sebastian -----Original Message----- From: Anca-Maria Vamanu [mailto:anca@voice-system.ro] Sent: Friday, May 25, 2007 11:14 AM To: Schumann Sebastian Cc: users(a)openser.org Subject: Re: [Users] Interaction Presence Agent - Presence User Agent Hello, There is already a means to do that but in the trunk version. You should just give the command with expires -1 and the pua module will refresh Publish until you give a command with expires 0. regards, Anca Schumann Sebastian wrote: > Dear all, > > > > I have a question for understanding: I have implemented one OpenSER as > Registrar and one OpenSER as Presence Agent plus XCAP Server 1.0.0. > This is all working so far with newest SVN Release (Big Thanks to > Ovidiu and Anca for the hint) of OpenSER. > > > > Now I want to deploy a Web-Front-End for user interaction with the > Presence Core, because not all clients used are SIMPLE capable. User > of non-capable devices should be able to just login and change their > presence state. They do not necessarily have to be registered at the > registrar, why PUA+ pua_usrloc on registrar side is no choice. > > > > I was thinking about another OpenSER deployed as PUA plus the pua_mi > module for a solution. It gets commands from Web-Frontend via PHP, > forwarded to the FIFO with pua_mi module. The problem I have now is > that the messages are sent just once. Means a user changes his > presence state, PUA sends a PUBLISH to PA but after the expiry the > user appears to be offline. > > > > Is there any possiblitiy to let the PUA send messages constantly, when > the user selects online - means all the time until offline is > selected? I was thinking about many possiblities (cronjob or > shellscript running all the time during online time and sending data > to FIFO) but they are more or less just work-arounds. > > > > Best regards > > Sebastian > > > > **Sebastian Schumann** > > Diploma Student Architecture and Design Department > > > > Slovak Telekom, a. s. > > T-Com, Operations Unit > > Production and Service Division > > Innovations and Enterprise Solution Subunit > > > > Address: Namestie Slobody 6, 817 62 Bratislava, Slovakia > > Office: Room 232, Jarabinkova 1, 821 09 Bratislava, Slovakia > > > > +421 910 643010 (mobile) > > > > sebastian.schumann(a)t-com.sk <mailto:sebastian.schumann@t-com.sk> > > http://www.t-com.sk > >----------------------------------------------------------------------- - > >_______________________________________________ >Users mailing list >Users(a)openser.org >http://openser.org/cgi-bin/mailman/listinfo/users > >

17 years, 7 months

[Serusers] INFO: Overview page of nominations for technical board

by Greger V. Teigre

As requested, here is a page for tracking nominations and status for the technical board: http://www.iptel.org/nominations_and_voting_technical_board_2007

17 years, 7 months

[Serusers] ANNOUNCEMENT: New serdoc mailing list for documentation work

by Greger V. Teigre

Dear all, We have just created a new mailing list called serdoc(a)iptel.org. The list will be used for coordination, questions, doc patches, and discussions/input on any iptel.org documentation. The main ongoing efforts right now are: - Migration guide to 2.0 - Reference guide - SER - Getting Started and the configuration files - Improve module documentation Other documentation work also for other projects like sems, serweb, rtpproxy etc will be covered on this list. Developer or user, please consider subscribing to the list and contribute to an improved iptel.org documentation! http://lists.iptel.org/mailman/listinfo/serdoc Thanks, g-)

17 years, 7 months

Re: [Serusers] behind 2 routers

by karl lu

Hi Ram, Thank you for your reply. Do you mean read the "NAT Traversal with Media proxy" section in get started document or search for "NAT Traversal with Media proxy" in our emial archive? Thanks, Karl ram <talk2ram(a)gmail.com> wrote: Hi look NAT Traversal with Media proxy ram On 5/22/07, root <taishan02(a)yahoo.com> wrote: Hi, I have a DSL router, which has only one port. To connect multiple computers I have another 4 ports router behind this DSL router. So SER is behind two routers. How can I configure these two routers so that I can use SER in this situation? Thanks, _______________________________________________ Serusers mailing list Serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

17 years, 7 months

Re: [Serusers] Frustrating error - please help

by Mahatma Sarasvati

Samuel, That was very helpful. The last line of the output made me wonder what was happening with the "ESTABLISHED" link. It was CounterPath Eyebeam UA that needed to be restarted. Somehow it was hung and was the source of the problem, not SER. Thanks for the help, M [root@vx1 ser]# lsof -i:5060 COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME . . ser 4739 root 10u IPv4 35606 TCP localhost.localdomain:sip (LISTEN) ser 4739 root 11u IPv4 35607 TCP vx1.v11.com:sip (LISTEN) . . ser 4741 root 10u IPv4 35606 TCP localhost.localdomain:sip (LISTEN) ser 4741 root 11u IPv4 35607 TCP vx1.v11.com:sip (LISTEN) ser 4741 root 45u IPv4 35925 TCP vx1.v11.com:sip->10.10.30.121:ispipes (ESTABLISHED) [root@vx1 ser]# ----- Original Message ---- From: samuel <samu60(a)gmail.com> To: Mahatma Sarasvati <gnoahhb(a)yahoo.com> Cc: Andrey Kuprianov <andrey.kouprianov(a)gmail.com>; "serusers(a)iptel.org" <serusers(a)iptel.org> Sent: Thursday, May 24, 2007 9:27:16 AM Subject: Re: [Serusers] Frustrating error - please help Maybe you've got another software bind to the address SER is trying to bind to(softphone,asterisk,...). Can you check whether the port 5060 is in use? what's the output of the next comand? #lsof -i:5060 samuel. 2007/5/24, Mahatma Sarasvati <gnoahhb(a)yahoo.com>: Also a good idea. Still no effect. This installation was working great for a while. Is it possible that some other software I've installed is causing the problem? This is 2.0.0 rc2 from CVS. M ----- Original Message ---- From: Andrey Kuprianov <andrey.kouprianov(a)gmail.com> To: "serusers(a)iptel.org" < serusers(a)iptel.org> Sent: Thursday, May 24, 2007 8:23:14 AM Subject: Re: [Serusers] Frustrating error - please help Maybe just try setting fork=yes ?... On 5/24/07, Mahatma Sarasvati < gnoahhb(a)yahoo.com> wrote: > > A good hint, but no. I'm using the standard version 1.4 ser.cfg. I've only > added my 10.10.10.41 ip address. The "fork=no" command is commented out. > > Is there something else that would cause ser to start in non-forking mode? > > Thanks, > M > > > ----- Original Message ---- > From: samuel < samu60(a)gmail.com> > To: Mahatma Sarasvati <gnoahhb(a)yahoo.com> > Cc: serusers(a)iptel.org > Sent: Thursday, May 24, 2007 12:40:41 AM > Subject: Re: [Serusers] Frustrating error - please help > > Are you starting SER in non-forking mode? It looks like SER is not binding > to the 10.10.10.41 IP, only to the local IP ( 127.0.0.1) and that's why you > see in the logs that it's not able to send to a "standard" IP address: > WARNING: xl_mod_init: more IP 10.10.10.41 not used > CRITICAL: invalid sendtoparameters one possible reason is the server is > bound to localhost and attempts to send to the net > > Case you need to use 2 interfaces, I would recommend using mhomed=yes (don't > recall the exact syntax right now..). > > Hope it helps, > Samuel. > > 2007/5/24, Mahatma Sarasvati <gnoahhb(a)yahoo.com>: > > Hi All, > > > > This ser installation was working fine and I can't figure out why its not > working now. > > I'm getting an error (see last log line) every time I attempt a call to > local users. Calling out to PSTN works great. ngrep reveals that SER is not > sending any messages to the callee location. > > > > There are 2 registered local users, one registered twice. > > > > I have no idea what is going on. I'm using an unmodified version 1.4 > ser.cfg file on CentOS 5. > > > > I suspect some server configuration error? ? ? ? > > > > > > Thanks, > > M > > > > > > > > Here are the logs. > > > > > > May 23 16:03:38 vx1 ser: init_tcp: using epoll_lt as the io watch method > (auto detected) > > May 23 16:03:38 vx1 /usr/local/sbin/ser[1692]: Maxfwd module- initializing > > May 23 16:03:38 vx1 /usr/local/sbin/ser[1692]: WARNING: xl_mod_init: more > IP 10.10.10.41 not used > > May 23 16:03:38 vx1 last message repeated 8 times > > May 23 16:03:38 vx1 /usr/local/sbin/ser[1692]: AVPops - initializing > > May 23 16:03:38 vx1 /usr/local/sbin/ser[1692]: DEB: IP address of RTPPROXY > is /var/run/rtpproxy.sock > > May 23 16:03:38 vx1 /usr/local/sbin/ser[1692]: INFO: xlog null is "<null>" > > May 23 16:03:38 vx1 /usr/local/sbin/ser[1692]: INFO: udp_init: SO_RCVBUF > is initially 109568 > > May 23 16:03:38 vx1 /usr/local/sbin/ser[1692]: INFO: udp_init: SO_RCVBUF > is finally 262142 > > May 23 16:03:38 vx1 /usr/local/sbin/ser[1692]: INFO: udp_init: SO_RCVBUF > is initially 109568 > > May 23 16:03:38 vx1 /usr/local/sbin/ser[1692]: INFO: udp_init: SO_RCVBUF > is finally 262142 > > . > > . > > . > > . > > May 23 16:09:15 vx1 /usr/local/sbin/ser[1781]: rtpp_test: RTP proxy > <unix:/var/run/rtpproxy.sock> found, support for it re-enabled > > May 23 16:09:15 vx1 /usr/local/sbin/ser[1781]: ERROR: udp_send: > sendto(sock,0xb62048f4,1773,0, 10.10.100.103:5060,16): Invalid argument(22) > > > > May 23 16:09:15 vx1 /usr/local/sbin/ser[1781]: CRITICAL: invalid > sendtoparameters one possible reason is the server is bound to localhost > > and attempts to send to the net > > May 23 16:09:15 vx1 /usr/local/sbin/ser[1781]: msg_send: ERROR: udp_send > failed > > May 23 16:09:15 vx1 /usr/local/sbin/ser[1781]: ERROR: t_send_branch: > sending request on branch 0 failed > > May 23 16:09:15 vx1 /usr/local/sbin/ser[1781]: ERROR: sl_reply_error used: > Unfortunately error on sending to next hop occurred (477/SL) > > > > > > > > When I start SER I get this response: > > > > [root@vx1 ~]# service ser restart > > Stopping ser: > [ OK ] > > Starting ser: Listening on > > udp: 127.0.0.1 [127.0.0.1]:5060 > > udp: 10.10.10.41 [ 10.10.10.41]:5060 > > tcp: 127.0.0.1 [127.0.0.1]:5060 > > tcp: 10.10.10.41 [ 10.10.10.41]:5060 > > Aliases: > > tcp: vx1:5060 > > tcp: vx1.velocity11.com:5060 > > tcp: localhost:5060 > > tcp: localhost.localdomain:5060 > > udp: vx1:5060 > > udp: vx1.velocity11.com:5060 > > udp: localhost:5060 > > udp: localhost.localdomain:5060 > > > > > [ OK ] > > [root@vx1 ~]# > > > > > > > > > > > > > > > > > > > ____________________________________________________________________________________Ready > for the edge of your seat? > > Check out tonight's top picks on Yahoo! TV. > > http://tv.yahoo.com/ > > _______________________________________________ > > Serusers mailing list > > Serusers(a)lists.iptel.org > > http://lists.iptel.org/mailman/listinfo/serusers > > > > > > ________________________________ > Sucker-punch spam with award-winning protection. > Try the free Yahoo! Mail Beta. > _______________________________________________ > Serusers mailing list > Serusers(a)lists.iptel.org > http://lists.iptel.org/mailman/listinfo/serusers > > _______________________________________________ Serusers mailing list Serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers ____________________________________________________________________________________Get the free Yahoo! toolbar and rest assured with the added security of spyware protection. http://new.toolbar.yahoo.com/toolbar/features/norton/index.php _______________________________________________ Serusers mailing list Serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers ____________________________________________________________________________________Sick sense of humor? Visit Yahoo! TV's Comedy with an Edge to see what's on, when. http://tv.yahoo.com/collections/222

17 years, 7 months

[Users] question about the openserctl ping command

by Papadopoulos Georgios

Hello all, I am using the openserct ping command to periodically check whether openser is working properly (If there is a better way to do this, please let me know). My script looks like this: SIP_URI="sip:213.5.xxx.xxx:5060" OPENSER_DIR=/root/openser TMP_FILE=/tmp/openser_ping.result $OPENSER_DIR/bin/openserctl ping $SIP_URI > $TMP_FILE 2>&1 Sometimes in TMP_FILE I see the following type of message: mkfifo: cannot create fifo `/tmp/openser_receiver_26907': File exists anaconda-ks.cfg install.log install.log.syslog mbox openser ERROR: error opening read fifo /tmp/openser_receiver_26907 At the same time openser seems to be working fine, however because the script gets this error, it restarts the server (the idea is that if ping fails then restart). Any idea why this is happening? What is the best way to make sure openser is working properly? I am assuming that a succesful ping only proves that one child is working properly. Thank you for any help George Disclaimer The information in this e-mail and any attachments is confidential. It is intended solely for the attention and use of the named addressee(s). If you are not the intended recipient, or person responsible for delivering this information to the intended recipient, please notify the sender immediately. Unless you are the intended recipient or his/her representative you are not authorized to, and must not, read, copy, distribute, use or retain this message or any part of it. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses.

17 years, 7 months

← Newer
1
...
6
7
8
9
10
11
12
...
30
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users May 2007