sr-users May 2006

sr-users@lists.kamailio.org

195 participants
503 discussions

[Serusers] Q:ABOUT:SerWeb "table CDR not found"
by Alejandro Sanchez 05 May '06

05 May '06

Hello! anyboby knows if the CDR table must be created manually because the table is not in the script of the SER 0.9.6 and when i try to access to accounting page sends a database error saying that the table dose not exists. Thank's for the help. ___________________________________________________________ Do You Yahoo!? La mejor conexión a Internet y <b >2GB</b> extra a tu correo por $100 al mes. http://net.yahoo.com.mx

2 1

[Users] ERROR: append_branch: max nr of branches exceeded
by Giuseppe Parlato 04 May '06

04 May '06

I get the following error sometimes.. May 4 11:53:35 dns2 ser[28473]: ERROR: append_branch: max nr of branches exceeded May 4 11:53:35 dns2 ser[28473]: lookup(): Error while appending a branch I read it was because the destination set has to be increased. I have to check configur.h file but where is it? I can't find it. I only found in ser.cfg childre=4 Giuseppe

4 8

[Serusers] Capture REDIRECT and BLOCK messages
by Steve Morard 04 May '06

04 May '06

Hi ! I'm wondering if there is a way to capture the REDIRECT messages and BLOCK messages created by SER ( we are using CPL to make decisions when an INVITE arrives ) and to store them in a database. Thank you Regards Steve

1 0

RE: [Serusers] How to use record route to change path of BYE messages
by İlker Aktuna (Koç.net) 04 May '06

04 May '06

Hi, Thanks for your reply but this is totally a different case. In my case the problem is not CANCEL messages but BYE and ACK messages. BYE message (and also ACK) is sent to the contact of the RTP stream instead of the SER proxy. But I want these messages to be sent to SER. That's why I should somehow make them to be sent to SER. So It should be done by either recording route or changing contact header. How can I do that ? Thanks, ilker ________________________________ From: serusers-bounces(a)iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of fay butt Sent: Thursday, May 04, 2006 7:08 PM To: serusers(a)lists.iptel.org Subject: Re: [Serusers] How to use record route to change path of BYE messages hi, i had that problem a time ago. I just put this messege and now it's working fine. if (method == "CANCEL" ) { if (uri =~"^sip:4[0-9]*@localhost") { forward ( asterisk , 5060 ); t_relay(); break; }; }; "Ýlker Aktuna (Koç.net)" <ilkera(a)koc.net> wrote: Hi, For voice communication I use a SIP+RTP proxy together with SER. For PSTN calls SER routes the INVITE messages to the RTP proxy. Everything works fine there, but when the call is ended by one client (which is connected to SER) or the PSTN user, the BYE message does not arrive to SER. If our RTP proxy does not see the message coming from SER, call doesn't end. That's why I need all of the BYE messages to go through SER. How can I do that ? In the default configuration there is a record route process for every message other than REGISTER. But still BYE and ACK messages are not sent to SER. Should I change the contact header of the messages arriving from RTP proxy ? If so, how can I do it ? What does following configuration block do ? if (loose_route()) { # mark routing logic in request append_hf("P-hint: rr-enforced\r\n"); route(1); break; }; Thanks, ilker _____________________________________________________________________________________________________________________________________________ Bu e-posta mesaji kisiye ozel olup, gizli bilgiler iceriyor olabilir. Eger bu e-posta mesaji size yanlislikla ulasmissa, icerigini hic bir sekilde kullanmayiniz ve ekli dosyalari acmayiniz. Bu durumda lutfen e-posta mesajini kullaniciya hemen geri gonderiniz ve tum kopyalarini mesaj kutunuzdan siliniz. Bu e-posta mesaji, hic bir sekilde, herhangi bir amac icin cogaltilamaz, yayinlanamaz ve para karsiligi satilamaz. Bu e-posta mesaji viruslere karsi anti-virus sistemleri tarafindan taranmistir. Ancak yollayici, bu e-posta mesajinin - virus koruma sistemleri ile kontrol ediliyor olsa bile - virus icermedigini garanti etmez ve meydana gelebilecek zararlardan dogacak hicbir sorumlulugu kabul etmez. This message is intended solely for the use of the individual or entity to whom it is addressed , and may contain confidential information. If you are not the intended recipient of this message or you receive this mail in error, you should refrain from making any use of the contents and from opening any attachment. In that case, please notify the sender immediately and return the message to the sender, then, delete and destroy all copies. This e-mail message, can not be copied, published or sold for any reason. This e-mail message has been swept by anti-virus systems for the presence of computer viruses. In doing so, however, sender cannot warrant that virus or other forms of data corruption may not be present and do not take any responsibility in any occurrence. _____________________________________________________________________________________________________________________________________________ _______________________________________________ Serusers mailing list serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers ________________________________ How low will we go? Check out Yahoo! Messenger’s low PC-to-Phone call rates. <http://us.rd.yahoo.com/mail_us/taglines/postman8/*http://us.rd.yahoo.com/ev…> <http://387555.sigclick.mailinfo.com/sigclick/02090504/06074F06/04084E03/211…> _____________________________________________________________________________________________________________________________________________ Bu e-posta mesaji kisiye ozel olup, gizli bilgiler iceriyor olabilir. Eger bu e-posta mesaji size yanlislikla ulasmissa, icerigini hic bir sekilde kullanmayiniz ve ekli dosyalari acmayiniz. Bu durumda lutfen e-posta mesajini kullaniciya hemen geri gonderiniz ve tum kopyalarini mesaj kutunuzdan siliniz. Bu e-posta mesaji, hic bir sekilde, herhangi bir amac icin cogaltilamaz, yayinlanamaz ve para karsiligi satilamaz. Bu e-posta mesaji viruslere karsi anti-virus sistemleri tarafindan taranmistir. Ancak yollayici, bu e-posta mesajinin - virus koruma sistemleri ile kontrol ediliyor olsa bile - virus icermedigini garanti etmez ve meydana gelebilecek zararlardan dogacak hicbir sorumlulugu kabul etmez. This message is intended solely for the use of the individual or entity to whom it is addressed , and may contain confidential information. If you are not the intended recipient of this message or you receive this mail in error, you should refrain from making any use of the contents and from opening any attachment. In that case, please notify the sender immediately and return the message to the sender, then, delete and destroy all copies. This e-mail message, can not be copied, published or sold for any reason. This e-mail message has been swept by anti-virus systems for the presence of computer viruses. In doing so, however, sender cannot warrant that virus or other forms of data corruption may not be present and do not take any responsibility in any occurrence. _____________________________________________________________________________________________________________________________________________

1 0

[Users] limiting number of calls per user
by Jayesh Nambiar 04 May '06

04 May '06

Hi, I was tring to limit the number of simultaneous calls a single user can recieve in openser. I am planning to keep a column in preferences table where his max number of calls will be mentioned and as and when an Invite goes to his uri, the value will be decremented and the value will be incremented again when the bye is received for that particular call. If the value becomes '0' he can receive no more calls. But there is also a possible issue where in if a bye is not received for any particular call due to any reason, the call would be on forever and his max_calls value will not be incremented again. First of all, can this idea be implemented using avps efficiently and what would be the overhead?? If it can be implemented, how can we overcome the issue of missing byes..... Can someone already tried this feature help me or guide me to go ahead with this idea. thanks.... jayesh. --------------------------------- Yahoo! India Answers: Share what you know. Learn something new. Click here

2 1

[Serusers] ReINVITE logging query
by sip 04 May '06

04 May '06

So... currently, we use a query modified from the one provided by the ever helpful Olivier Taylor to get CDR-like call-log info from SER's acc: SELECT t1.from_uri as Caller, t1.to_uri as Callee, TIMEDIFF(t2.time, t1.time) as Duration, t1.time as CallDate FROM acc t1, acc t2 WHERE t1.sip_callid=t2.sip_callid AND ((t1.fromtag=t2.fromtag AND t1.totag=t2.totag) OR (t1.fromtag=t2.totag AND t1.totag=t2.fromtag)) AND t1.sip_method='INVITE' AND t2.sip_method='BYE' AND t1.from_uri='<username>' ORDER BY t1.time DESC; It works really well with one glaring problem.... reINVITES get logged as separate calls. We see a lot of these going through FWD and our PSTN stuff and several other providers we peer with, and it becomes weird. For instance, a normal call... userA --> proxy --> userB Works really well UNLESS there's a reINVITE from userB to userA for a direct path. In that case, for a 10-second call, we get call logs that looks like: Outgoing: uriA | uriB | 00:10 | 2006-04-04 13:34:48 Incoming: uriB | uriA | 00:10 | 2006-04-04 13:34:48 The same call is logged twice as it logs both the INVITE outgoing and the incoming reINVITE. Can anyone think of a query that would strip the reINVITEs? Or are we likely going to have to do something programatically to get rid of these? Thanks, N.

1 0

[Serusers] How to use record route to change path of BYE messages
by İlker Aktuna (Koç.net) 04 May '06

04 May '06

Hi, For voice communication I use a SIP+RTP proxy together with SER. For PSTN calls SER routes the INVITE messages to the RTP proxy. Everything works fine there, but when the call is ended by one client (which is connected to SER) or the PSTN user, the BYE message does not arrive to SER. If our RTP proxy does not see the message coming from SER, call doesn't end. That's why I need all of the BYE messages to go through SER. How can I do that ? In the default configuration there is a record route process for every message other than REGISTER. But still BYE and ACK messages are not sent to SER. Should I change the contact header of the messages arriving from RTP proxy ? If so, how can I do it ? What does following configuration block do ? if (loose_route()) { # mark routing logic in request append_hf("P-hint: rr-enforced\r\n"); route(1); break; }; Thanks, ilker <http://387555.sigclick.mailinfo.com/sigclick/0B0A0505/07074505/0D014E02/182…> _____________________________________________________________________________________________________________________________________________ Bu e-posta mesaji kisiye ozel olup, gizli bilgiler iceriyor olabilir. Eger bu e-posta mesaji size yanlislikla ulasmissa, icerigini hic bir sekilde kullanmayiniz ve ekli dosyalari acmayiniz. Bu durumda lutfen e-posta mesajini kullaniciya hemen geri gonderiniz ve tum kopyalarini mesaj kutunuzdan siliniz. Bu e-posta mesaji, hic bir sekilde, herhangi bir amac icin cogaltilamaz, yayinlanamaz ve para karsiligi satilamaz. Bu e-posta mesaji viruslere karsi anti-virus sistemleri tarafindan taranmistir. Ancak yollayici, bu e-posta mesajinin - virus koruma sistemleri ile kontrol ediliyor olsa bile - virus icermedigini garanti etmez ve meydana gelebilecek zararlardan dogacak hicbir sorumlulugu kabul etmez. This message is intended solely for the use of the individual or entity to whom it is addressed , and may contain confidential information. If you are not the intended recipient of this message or you receive this mail in error, you should refrain from making any use of the contents and from opening any attachment. In that case, please notify the sender immediately and return the message to the sender, then, delete and destroy all copies. This e-mail message, can not be copied, published or sold for any reason. This e-mail message has been swept by anti-virus systems for the presence of computer viruses. In doing so, however, sender cannot warrant that virus or other forms of data corruption may not be present and do not take any responsibility in any occurrence. _____________________________________________________________________________________________________________________________________________

2 1

[Users] extra accounting and exported pseudo variables
by Klaus Darilion 04 May '06

04 May '06

Hi! I'm trying to extra account exported pseudo variables. should this work? modparam("acc", "db_extra", "source_ip=$si;source_port=$sp;received_ip=$Ri;received_port=$Rp;tls_peer_subject=$tls_peer_subject"); nomal logging is fine: xlog("L_INFO","[$Tf] $$tls_peer_subject = '$tls_peer_subject'\n"); results in: [Wed May 3 16:11:52 2006] $tls_peer_subject = '/C=at/ST=Vienna/L=Vienna/O=itsp2/CN=itsp2.labs.nic.at But the accounting fails: ERROR:acc:extra2strar: failed to get 'tls_peer_subject' Is there a known problem? Is it because when the accounting is done, there is no more TLS connection available to retrieve the cert parameters? Meanwhile I will try the workaround with copying to AVPs and accounting of the AVPs. regards klaus

2 6

[Serusers] ser and History-Info (RFC 4244) for VM/UM application
by john hess 04 May '06

04 May '06

hi, does anyone have experience in using ser in processing call-forwarding/redirection signaled in the History-Info section (as per RFC 4244)? the application context is ser as a means to interpolate signaling between an IP PBX and a SIP-speaking VM/UM platform (I3 Communite -- v2.3.1). the problem i am trying to solve (at least in the near-term) is that the PBX is using History-Info to signal call-forwarding events (ex: CFNA, CFB) while Communite is expecting call-forwarding to be signaled via Diversion. until the platforms support have a call-forwarding signaling method in common, i would like to be able to insert ser into the signaling path -- more or less as a translator between the two platforms. tia, john john hess <jhess(a)berkeley.edu> nocman ist, uc berkeley 510 643-6401

1 0

RE: [Serusers] IM and presence problems
by İlker Aktuna (Koç.net) 04 May '06

04 May '06

Hi Vaclav, The following message bounced from the mailing list. Please confirm if you received it. Thanks, ilker ________________________________ From: İlker Aktuna (Koç.net) Sent: Thursday, May 04, 2006 4:20 PM To: 'Vaclav Kubart' Cc: serusers(a)lists.iptel.org Subject: RE: [Serusers] IM and presence problems Hi Vaclav, I've run with no NAT; ngrep output and ser log with debug=4 is attached. You can see that Ser server can ping the contact address at the end of the ngrep output. In the debug log I filtered the process ID 2905 for you. I hope it helps to figure out where the problem is. Btw, xcap root does not have any index file. Eyebeam client does not receive xcap authorization request. Presentity is not shown also. Online IM messages are working but offline messages don't reach user (maybe it's related). Today I returned back to the eyebeam 1.1 release and results are the same. Thanks, ilker -----Original Message----- From: Vaclav Kubart [mailto:vaclav.kubart@iptel.org] Sent: Thursday, May 04, 2006 3:02 PM To: İlker Aktuna (Koç.net) Cc: serusers(a)lists.iptel.org Subject: Re: [Serusers] IM and presence problems Hi, run it without NAT and debug=4 and send me ngrep dump again. In the log try to find debug messages containing next hop address like: May 2 13:19:51 sesapp /root/ser/sbin/ser[19887]: DEBUG:tm:t_uac: next_hop=<sip:200000900568888888@192.168.2.17:26548;transport=udp> May 2 13:19:51 sesapp /root/ser/sbin/ser[19885]: qm_free(0x8120e80, 0x81703b0), called from data_lump.c: free_lump_list(409) May 2 13:19:51 sesapp /root/ser/sbin/ser[19886]: qm_malloc(0x8120e80, 32) called from data_lump.c: insert_cond_lump_after(216) May 2 13:19:51 sesapp /root/ser/sbin/ser[19888]: qm_malloc(0x8120e80, 8) returns address 0x81706b8 frag. 0x81706a0 (size=8) on 1 -th hit May 2 13:19:51 sesapp /root/ser/sbin/ser[19887]: t_uac: no socket found May 2 13:19:51 sesapp /root/ser/sbin/ser[19887]: t_uac: no socket found May 2 13:19:51 sesapp /root/ser/sbin/ser[19885]: qm_free: freeing frag. 0x8170398 alloc'ed from data_lump.c: insert_new_lump_before(140) In this sample is next_hop = sip:200000900568888888@192.168.2.17:26548;transport=udp. The number of process has to be the same as in consequent error message "t_uac: socket not found". It is the number in [ ] - in this case 19887. The address there has to be accessible from machine with SER (try to ping the IP). The index file is not needed. And are watchers authorized? (Do they see status of presentity?) Vaclav On Thu, May 04, 2006 at 02:52:39PM +0300, ?lker Aktuna (Koç.net) wrote: > Hi Vaclav, > > I still couldn't succeed in presence over SER. > Still getting following messages, no matter if I'm behid NAT or not. > I tested on LAN many times but I still get same error messages. > > Btw, there is no index file in my xcap-root directory. Should I have something there ? > I didn't receive any xcap authorization request after changing xcap > authorization root to real hostname instead of 127.0.0.1 > > May 4 14:42:27 sesapp /root/ser/sbin/ser[19996]: t_uac: no socket > found May 4 14:42:27 sesapp /root/ser/sbin/ser[19996]: t_uac: no > socket found May 4 14:42:27 sesapp /root/ser/sbin/ser[19996]: ERROR: > notify.c:398: Can't send watcherinfo notification (-7) May 4 14:42:27 > sesapp /root/ser/sbin/ser[19996]: ERROR: notify.c:398: Can't send > watcherinfo notification (-7) May 4 14:42:27 sesapp > /root/ser/sbin/ser[19996]: send_winfo_notify returned -7 May 4 > 14:42:27 sesapp /root/ser/sbin/ser[19996]: send_winfo_notify returned > -7 > > > Thanks, > ilker > > > -----Original Message----- > From: Vaclav Kubart [mailto:vaclav.kubart@iptel.org] > Sent: Tuesday, May 02, 2006 5:50 PM > To: ?lker Aktuna (Koç.net) > Cc: serusers(a)lists.iptel.org > Subject: Re: [Serusers] IM and presence problems > > Try to use nathelper module. I'm not familiar with it but there exists some documentation for it (in modules/nathelper/README). > > Vaclav > > On Tue, May 02, 2006 at 05:19:10PM +0300, ?lker Aktuna (Koç.net) wrote: > > Hi Vaclav, > > > > The ngrep.out file was from Friday. And I realized that I'd changed Eyebeam client configuration after Friday. > > Now it sends internal IP as contact. (as in the attached ngrep2.out > > file) > > > > Now I don't know how to change the contact as public IP. But > > presencce messages were not working Friday also > > > > Any idea how to change the contact as public IP ? > > > > Thanks, > > ilker > > > > > > -----Original Message----- > > From: Vaclav Kubart [mailto:vaclav.kubart@iptel.org] > > Sent: Tuesday, May 02, 2006 2:56 PM > > To: ?lker Aktuna (Koç.net) > > Cc: serusers(a)lists.iptel.org > > Subject: Re: [Serusers] IM and presence problems > > > > > 192.168.2.17 is a NAT client behing 85.105.102.167 Could it be > > > that the SER is sending the messages to the internal IP address of my Eyebeam client ? > > > > It seems so. > > > > > On eyebeam 1.5 I use the "use rport" option of the client if that matters. > > > > > > Any idea why I get so many "no socket found" errors ? (might it be > > > because ser is trying to connect to the internal IP address ?) > > > > SER tries to connect to IP address which is not accessible for it. And it tries again and again... > > > > But I don't know how this IP address got to presence SER, because there was 85.xxx.xxx.xxx in Contact in SUBSCRIBE request in the network dump. > > > > Vaclav > > > > > > > > Thanks, > > > ilker > > > > > > > > > -----Original Message----- > > > From: Vaclav Kubart [mailto:vaclav.kubart@iptel.org] > > > Sent: Tuesday, May 02, 2006 1:34 PM > > > To: ?lker Aktuna (Koç.net) > > > Cc: serusers(a)lists.iptel.org > > > Subject: Re: [Serusers] IM and presence problems > > > > > > I take a look into the log and it seems, that NOTIFY requests try to be sent to 192.168.2.17. > > > > > > But in the ngrep dump I see only some 85.105.102.167 addresses in Contacts in SUBSCRIBE requests. Are you sure, that these log and the flow belong to the same scenario? > > > > > > If yes, it means, that there is a bug in PA module. > > > > > > Be sure to catch messages on machine with presence server. > > > > > > Vaclav > > > > > > On Tue, May 02, 2006 at 01:14:37PM +0300, ?lker Aktuna (Koç.net) wrote: > > > > Hi, > > > > > > > > I've captured debug logs by suggestion of Mr. Michal Matyska. > > > > Attached I'm sending them to you. I hope it reaches you. > > > > Please look for the "no socket found" and "Can't send watcherinfo notification " lines in the log as it's too long. > > > > > > > > Thanks, > > > > ilker > > > > <http://387555.sigclick.mailinfo.com/sigclick/020A0707/07044906/050B4C00/212…> _____________________________________________________________________________________________________________________________________________ Bu e-posta mesaji kisiye ozel olup, gizli bilgiler iceriyor olabilir. Eger bu e-posta mesaji size yanlislikla ulasmissa, icerigini hic bir sekilde kullanmayiniz ve ekli dosyalari acmayiniz. Bu durumda lutfen e-posta mesajini kullaniciya hemen geri gonderiniz ve tum kopyalarini mesaj kutunuzdan siliniz. Bu e-posta mesaji, hic bir sekilde, herhangi bir amac icin cogaltilamaz, yayinlanamaz ve para karsiligi satilamaz. Bu e-posta mesaji viruslere karsi anti-virus sistemleri tarafindan taranmistir. Ancak yollayici, bu e-posta mesajinin - virus koruma sistemleri ile kontrol ediliyor olsa bile - virus icermedigini garanti etmez ve meydana gelebilecek zararlardan dogacak hicbir sorumlulugu kabul etmez. This message is intended solely for the use of the individual or entity to whom it is addressed , and may contain confidential information. If you are not the intended recipient of this message or you receive this mail in error, you should refrain from making any use of the contents and from opening any attachment. In that case, please notify the sender immediately and return the message to the sender, then, delete and destroy all copies. This e-mail message, can not be copied, published or sold for any reason. This e-mail message has been swept by anti-virus systems for the presence of computer viruses. In doing so, however, sender cannot warrant that virus or other forms of data corruption may not be present and do not take any responsibility in any occurrence. _____________________________________________________________________________________________________________________________________________

1 0

← Newer
1
...
41
42
43
44
45
46
47
...
51
Older →

Jump to page:

2025

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 2006