- sr-users - kamailio.org

[OpenSER-Users] perl
by David Villasmil Govea 03 Dec '07

03 Dec '07

> > > OpenSER modules can be included while compiling by using the > "include_modules" > statement. Thus, the perl module (not "mod_perl", as Daniel already > pointed > out) can be compiled along with OpenSER by using > make include_modules="perl" > > You will need your distribution's perl development packages installed > while > compiling. Yes, I have it compiled with no problems, but when i try to load a perl script, i get this: 0(0) perl: Setting lib path: '/usr/local/lib/openser/perl/' 0(0) perl error: Can't locate OpenSER/Utils/PhoneNumber.pm in @INC (@INC contains: /usr/local/lib/openser/perl/ /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl .) at /usr/local/etc/openser/openser.pl line 4. 0(0) perl error: Can't locate OpenSER/Utils/PhoneNumber.pm in @INC (@INC contains: /usr/local/lib/openser/perl/ /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl .) at /usr/local/etc/openser/openser.pl line 4. BEGIN failed--compilation aborted at /usr/local/etc/openser/openser.pl line 4. Can't locate OpenSER/Utils/PhoneNumber.pm in @INC (@INC contains: /usr/local/lib/openser/perl/ /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl .) at /usr/local/etc/openser/openser.pl line 4. BEGIN failed--compilation aborted at /usr/local/etc/openser/openser.pl line 4. Although modules are there in: me@server:/usr/local/lib/openser/perl# ls -l /usr/local/lib/openser/perl/ total 4 drwxrwx--- 4 root root 168 2007-12-03 14:00 OpenSER -rwxrwx--- 1 root root 1354 2007-12-03 14:00 OpenSER.pm me@server:/usr/local/lib/openser/perl# ls -l /usr/local/lib/openser/perl/OpenSER total 12 -rw-r--r-- 1 root root 4844 2007-12-03 14:00 Constants.pm drwxr-xr-x 2 root root 120 2007-12-03 14:00 LDAPUtils -rw-r--r-- 1 root root 1602 2007-12-03 14:00 Message.pm drwxr-xr-x 2 root root 80 2007-12-03 14:00 Utils me@server:/usr/local/lib/openser/perl# ls -l /usr/local/lib/openser/perl/OpenSER/Utils/ total 8 -rw-r--r-- 1 root root 6096 2007-12-03 14:00 PhoneNumbers.pm > > > Feel free to ask if you have any concrete questions. > > > - Is there a tutorial for using MySQL as a backend? How about a > > cluster? > > MySQL backend for what? I have it working as a MySQL backend for users. What i need is the logging of cdrs... i understand that there are several records for each call. But, how do i configure this? is it possible with MySQL? thanks a lot. > > > Bastian > thanks much for your help! David -- DVG -- Imagination is more important than knowledge Albert Einstein

2 1

[Serusers] Problems with syslog and mysql on version 0.96
by Michael Roeper 03 Dec '07

03 Dec '07

Hi, we have SER version 0.96 running on a debian system using mysql for user authentication. Everything works fine as long as we use the standard logging to /var/log/syslog. When we change the logging to use another syslog facility (e.g. log_facility=LOG_LOCAL0 in ser.cfg) all messages are written to the file specified in syslog.conf, but the users are not able to register to ser. It looks as if the db-connection to the mysql database is not available. Has anybody observed this behaviour and can provide a hint ? We appreciate any kind of help. Kind regards, Michael -- Dr.Michael Roeper Email: m.roeper(a)wenzel-elektronik.de Wenzel Elektronik GmbH Tel.: 04121/4872-69 Max-Planck-Str. 2-4 Fax : 04121/4872-18 25335 Elmshorn http://www.wenzel-elektronik.de Sitz der Gesellschaft: Elmshorn Registergericht: Pinneberg, HRB 1974 EL USt-IdNr.: DE 812946778 Geschäftsführung: Dipl. Ing Jörg Simon, Dr. Volker Henkel --

1 0

[OpenSER-Users] OpenSER: t-check_trans question
by Helmut Kuper 03 Dec '07

03 Dec '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, today I found, that t_check_trans function of TM module seems to has a problem with at least PUBLISH and SUBSCRIBE Messages. If openser checks theses messages with t_check_trans() route script execution will stop. Is this intended or a bug? Module docc says, that t_check_trans() cares about ACKs and CANCELs .. regards helmut -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHU9mU4tZeNddg3dwRAlk/AJ9k/B/YBum72U45csWBqyi7RMLxXQCfWLLx rxRkJmYXFSOFvq6FlYKR3ng= =0bIH -----END PGP SIGNATURE-----

2 1

[Serusers] function get_from_did(&did, msg) error
by Tomasz Zieleniewski 03 Dec '07

03 Dec '07

Hi, I was trying to set up media proxy module and after some time of debuging I discovered that the problems were in the get_from_did(&did, msg) function. in mediaproxy.c file in line 469 there is such piece of code: if (get_from_did(&did, msg) == 0) { *type = "local"; return did; } when this code is invoked the result is wrong. this is some nowhere pointer with the length of the field unpredictable. after this invocation there is another piece of code wich tries to allocate some memory baseing on the length of the did string.(line 1449) cmdlen = callId.len + strlen(clientIP) + fromDomain.len + toDomain.len + userAgent.len*3 + infolen + 128; command = pkg_malloc(cmdlen); if (!command) { LOG(L_ERR, "error: use_media_proxy() - (!command): out of memory\n"); return -1; } this causes out of memory error when value of fromDomain.len gives random big number(below example of one my shots) Dec 2 18:17:17 rd ser[5884]: route[MEDIA]: use_media_proxy() Dec 2 18:17:17 rd ser[5884]: error: get_from_did - true Dec 2 18:17:17 rd ser[5884]: error: callId.len: 44 Dec 2 18:17:17 rd ser[5884]: error: strlen(clientIP): 14 Dec 2 18:17:17 rd ser[5884]: error: fromDomain.len: 1235653920 Dec 2 18:17:17 rd ser[5884]: error: toDomain.len: 14 Dec 2 18:17:17 rd ser[5884]: error: userAgent.len*3: 96 Dec 2 18:17:17 rd ser[5884]: error: infolen: 107 Dec 2 18:17:17 rd ser[5884]: error: cmdlen 1235654349 Dec 2 18:17:17 rd ser[5884]: error: use_media_proxy() - (!command): out of memory please, can someone check this and fix best regards tomasz

2 2

[OpenSER-Users] mod_perl
by David Villasmil Govea 03 Dec '07

03 Dec '07

Hello all, Its my first time writing to the list, i hope someone can help me out. - Can anyone point me in the right direction for compiling with mod_perl? I tried compiling but it wouldn't work. That was a few months ago, though. Is there a good step-by-step tutorial? - Is there a tutorial for using MySQL as a backend? How about a cluster? thanks to all. David

3 2

[Serusers] error in mediaproxy - module generates wrong request format
by Tomasz Zieleniewski 02 Dec '07

02 Dec '07

Hi, I am using mediaproxy for rtp traffic. I am using ser rel_2_0_0_rc5 and media proxy 1.9.0. When there is an invite message and i invoke use_media_proxy media proxy module in ser send wrong request to proxydispatcher or mediaproxy (depending on the type of configuration) The lookup request format according to the modules/request.py file is 'cmd', 'sessionId', 'streams', 'signalingIP', 'callerDomain', 'callerType','calledDomain', 'calledType', 'userAgent', 'info' but mediaproxy module sends such one: lookup MjI3MjcwMzA3NGQxNTc3YjUxZDA5NmQ1NzE4ZmNiOTQ. 192.168.129.74:13122:audio 192.168.129.74 local voip.touk.pl remote Asterisk=20PBX info= from:tzl@voip.touk.pl,to:poczta@voip.touk.pl ,fromtag:cb239428,totag:as707ae074 there is no callerDomain attribute. Please tell me did I miss something or this is realy bug in mediaproxy module. Cheers -tomasz

1 0

Re: [OpenSER-Users] Users Digest, Vol 31, Issue 2
by David Villasmil Govea 02 Dec '07

02 Dec '07

Oops! sorry, wrong list!

1 0

[OpenSER-Users] compiling woomera for FS
by David Villasmil Govea 02 Dec '07

02 Dec '07

Hello all again, I jus compiled beta2 of FS perfectly. I want to use woomera H.323 but it is simply impossible to do. I tried to follow the instructions on the wiki but it simply doesn't work. pwlib and openh323 compiled fine but woomera comes back with: g++ -D_REENTRANT -Wall -I/root/openh323/../pwlib/include -DPTRACING -I/root/openh323/include -Os -felide-constructors -Wreorder -c main.cxx -o obj_linux_x86_r/main.o In file included from main.cxx:129: openh323.h:212:22: warning: no newline at end of file /root/openh323/../pwlib/include/ptclib/pwavfile.h:166: warning: â?~packedâ?T attribute ignored for field of type â?~char [4]â?T /root/openh323/../pwlib/include/ptclib/pwavfile.h:172: warning: â?~packedâ?T attribute ignored for field of type â?~PWAV::ChunkHeaderâ?T /root/openh323/../pwlib/include/ptclib/pwavfile.h:173: warning: â?~packedâ?T attribute ignored for field of type â?~char [4]â?T /root/openh323/../pwlib/include/ptclib/pwavfile.h:178: warning: â?~packedâ?T attribute ignored for field of type â?~PWAV::ChunkHeaderâ?T lib/woomera.h:819: warning: â?~class Woomera::ExternalCommandâ?T has virtual functions but non-virtual destructor /root/openh323/include/h4601.h: In member function â?~H460_FeatureContent::operator H460_FeatureTable*()â?T: /root/openh323/include/h4601.h:292: warning: type-punning to incomplete type might break strict-aliasing rules after repeating the lines above several times: g++ -D_REENTRANT -Wall -I/root/openh323/../pwlib/include -DPTRACING -I/root/openh323/include -Os -felide-constructors -Wr eorder -c wivr.cxx -o obj_linux_x86_r/wivr.o /root/openh323/../pwlib/include/ptclib/pwavfile.h:166: warning: â?~packedâ?T attribute ignored for field of type â?~char [4]â ?T /root/openh323/../pwlib/include/ptclib/pwavfile.h:172: warning: â?~packedâ?T attribute ignored for field of type â?~PWAV::Chu nkHeaderâ?T /root/openh323/../pwlib/include/ptclib/pwavfile.h:173: warning: â?~packedâ?T attribute ignored for field of type â?~char [4]â ?T /root/openh323/../pwlib/include/ptclib/pwavfile.h:178: warning: â?~packedâ?T attribute ignored for field of type â?~PWAV::Chu nkHeaderâ?T ./lib/woomera.h:819: warning: â?~class Woomera::ExternalCommandâ?T has virtual functions but non-virtual destructor g++ -o obj_linux_x86_r/woomera -L/root/openh323/../pwlib/lib -L/root/openh323/lib ./obj_linux_x86_r/main.o ./obj_linux_ x86_r/openh323.o ./obj_linux_x86_r/woomera.o ./obj_linux_x86_r/server.o ./obj_linux_x86_r/connection.o ./obj_linux_x86_r/ client.o ./obj_linux_x86_r/wivr.o -lh323_linux_x86_r -lpt_linux_x86_r -lpthread -lssl -lcrypto -lresolv -ldl ./obj_linux_x86_r/openh323.o: In function `OpenH323WoomeraCall::OnH323OpenAudioChannel(H323AudioCodec&, int)': openh323.cxx:(.text+0x2b49): undefined reference to `PVXMLSession::PVXMLSession(PTextToSpeech*, int)' openh323.cxx:(.text+0x2ba2): undefined reference to `PVXMLSession::SetTextToSpeech(PString const&)' ./obj_linux_x86_r/woomera.o: In function `WoomeraPlayableToneDevice::Open(PVXMLChannel&, PString const&, int, int, int)': woomera.cxx:(.text+0x1239): undefined reference to `PVXMLPlayableData::SetData(PBYTEArray const&)' woomera.cxx:(.text+0x1253): undefined reference to `PVXMLPlayableData::Open(PVXMLChannel&, PString const&, int, int, int)' ./obj_linux_x86_r/woomera.o: In function `PVXMLPlayable::~PVXMLPlayable()': woomera.cxx:(.text._ZN13PVXMLPlayableD2Ev[PVXMLPlayable::~PVXMLPlayable()]+0x10): undefined reference to `vtable for PVXMLPla yable' ./obj_linux_x86_r/woomera.o: In function `PVXMLPlayableData::~PVXMLPlayableData()': woomera.cxx:(.text._ZN17PVXMLPlayableDataD2Ev[PVXMLPlayableData::~PVXMLPlayableData()]+0x10): undefined reference to `vtable for PVXMLPlayableData' ./obj_linux_x86_r/woomera.o: In function `PVXMLPlayableFilename::~PVXMLPlayableFilename()': woomera.cxx:(.text._ZN21PVXMLPlayableFilenameD2Ev[PVXMLPlayableFilename::~PVXMLPlayableFilename()]+0x10): undefined reference to `vtable for PVXMLPlayableFilename' ./obj_linux_x86_r/woomera.o: In function `PVXMLPlayableURL::~PVXMLPlayableURL()': woomera.cxx:(.text._ZN16PVXMLPlayableURLD2Ev[PVXMLPlayableURL::~PVXMLPlayableURL()]+0x10): undefined reference to `vtable for PVXMLPlayableURL' ./obj_linux_x86_r/woomera.o: In function `PVXMLPlayable::PVXMLPlayable()': woomera.cxx:(.text._ZN13PVXMLPlayableC2Ev[PVXMLPlayable::PVXMLPlayable()]+0xe): undefined reference to `vtable for PVXMLPlaya ble' ./obj_linux_x86_r/woomera.o: In function `PVXMLPlayableData::PVXMLPlayableData()': woomera.cxx:(.text._ZN17PVXMLPlayableDataC2Ev[PVXMLPlayableData::PVXMLPlayableData()]+0x13): undefined reference to `vtable f or PVXMLPlayableData' ./obj_linux_x86_r/woomera.o: In function `PVXMLPlayableFilename::PVXMLPlayableFilename()': woomera.cxx:(.text._ZN21PVXMLPlayableFilenameC2Ev[PVXMLPlayableFilename::PVXMLPlayableFilename()]+0x16): undefined reference to `vtable for PVXMLPlayableFilename' ./obj_linux_x86_r/woomera.o: In function `PVXMLPlayableURL::PVXMLPlayableURL()': woomera.cxx:(.text._ZN16PVXMLPlayableURLC2Ev[PVXMLPlayableURL::PVXMLPlayableURL()]+0x16): undefined reference to `vtable for PVXMLPlayableURL' ./obj_linux_x86_r/woomera.o: In function `WoomeraPlayableFilename::OnStop()': woomera.cxx:(.text._ZN23WoomeraPlayableFilename6OnStopEv[WoomeraPlayableFilename::OnStop()]+0xf): undefined reference to `PVX MLPlayableFilename::OnStop()' ./obj_linux_x86_r/woomera.o:(.rodata._ZTV25WoomeraPlayableToneDevice[vtable for WoomeraPlayableToneDevice]+0x38): undefined r eference to `PVXMLPlayableData::Play(PVXMLChannel&)' ./obj_linux_x86_r/woomera.o:(.rodata._ZTV25WoomeraPlayableToneDevice[vtable for WoomeraPlayableToneDevice]+0x54): undefined r eference to `PVXMLPlayable::ReadFrame(PVXMLChannel&, void*, int)' ./obj_linux_x86_r/woomera.o:(.rodata._ZTV25WoomeraPlayableToneDevice[vtable for WoomeraPlayableToneDevice]+0x58): undefined r eference to `PVXMLPlayableData::Rewind(PChannel*)' ./obj_linux_x86_r/woomera.o:(.rodata._ZTV26WoomeraPlayableSoundDevice[vtable for WoomeraPlayableSoundDevice]+0x54): undefined reference to `PVXMLPlayable::ReadFrame(PVXMLChannel&, void*, int)' ./obj_linux_x86_r/woomera.o:(.rodata._ZTI25WoomeraPlayableToneDevice[typeinfo for WoomeraPlayableToneDevice]+0x10): undefined reference to `typeinfo for PVXMLPlayableData' ./obj_linux_x86_r/woomera.o:(.rodata._ZTI26WoomeraPlayableSoundDevice[typeinfo for WoomeraPlayableSoundDevice]+0x10): undefin ed reference to `typeinfo for PVXMLPlayable' ./obj_linux_x86_r/woomera.o:(.rodata._ZTV23WoomeraPlayableFilename[vtable for WoomeraPlayableFilename]+0x34): undefined refer ence to `PVXMLPlayableFilename::Open(PVXMLChannel&, PString const&, int, int, int)' ./obj_linux_x86_r/woomera.o:(.rodata._ZTV23WoomeraPlayableFilename[vtable for WoomeraPlayableFilename]+0x38): undefined refer ence to `PVXMLPlayableFilename::Play(PVXMLChannel&)' ./obj_linux_x86_r/woomera.o:(.rodata._ZTV23WoomeraPlayableFilename[vtable for WoomeraPlayableFilename]+0x54): undefined refer ence to `PVXMLPlayable::ReadFrame(PVXMLChannel&, void*, int)' ./obj_linux_x86_r/woomera.o:(.rodata._ZTV23WoomeraPlayableFilename[vtable for WoomeraPlayableFilename]+0x58): undefined refer ence to `PVXMLPlayableFilename::Rewind(PChannel*)' ./obj_linux_x86_r/woomera.o:(.rodata._ZTI23WoomeraPlayableFilename[typeinfo for WoomeraPlayableFilename]+0x10): undefined ref erence to `typeinfo for PVXMLPlayableFilename' ./obj_linux_x86_r/woomera.o:(.rodata._ZTV18WoomeraPlayableURL[vtable for WoomeraPlayableURL]+0x34): undefined reference to `P VXMLPlayableURL::Open(PVXMLChannel&, PString const&, int, int, int)' ./obj_linux_x86_r/woomera.o:(.rodata._ZTV18WoomeraPlayableURL[vtable for WoomeraPlayableURL]+0x38): undefined reference to `P VXMLPlayableURL::Play(PVXMLChannel&)' ./obj_linux_x86_r/woomera.o:(.rodata._ZTV18WoomeraPlayableURL[vtable for WoomeraPlayableURL]+0x54): undefined reference to `P VXMLPlayable::ReadFrame(PVXMLChannel&, void*, int)' ./obj_linux_x86_r/woomera.o:(.rodata._ZTI18WoomeraPlayableURL[typeinfo for WoomeraPlayableURL]+0x10): undefined reference to `typeinfo for PVXMLPlayableURL' ./obj_linux_x86_r/server.o: In function `Woomera::Call::SetVar(PString const&, PString const&)': server.cxx:(.text+0x59c): undefined reference to `PVXMLSession::SetTextToSpeech(PString const&)' ./obj_linux_x86_r/server.o: In function `Woomera::Call::OnCmdRecord(PStringArray const&, PMIMEInfo const&, PString const&)': server.cxx:(.text+0x70bc): undefined reference to `PVXMLChannel::EndRecording()' ./obj_linux_x86_r/server.o: In function `Woomera::Call::OnCmdSpeak(PStringArray const&, PMIMEInfo const&, PString const&)': server.cxx:(.text+0x7e79): undefined reference to `PVXMLSession::ConvertTextToFilenameList(PString const&, PTextToSpeech::Tex tType, PStringArray&, int)' server.cxx:(.text+0x8053): undefined reference to `PVXMLPlayableFilenameList::Open(PVXMLChannel&, PStringArray const&, int, i nt, int)' ./obj_linux_x86_r/server.o: In function `PVXMLPlayableFilenameList::~PVXMLPlayableFilenameList()': server.cxx:(.text._ZN25PVXMLPlayableFilenameListD2Ev[PVXMLPlayableFilenameList::~PVXMLPlayableFilenameList()]+0x10): undefine d reference to `vtable for PVXMLPlayableFilenameList' ./obj_linux_x86_r/server.o: In function `PVXMLRecordableFilename::~PVXMLRecordableFilename()': server.cxx:(.text._ZN23PVXMLRecordableFilenameD2Ev[PVXMLRecordableFilename::~PVXMLRecordableFilename()]+0x10): undefined refe rence to `vtable for PVXMLRecordableFilename' ./obj_linux_x86_r/server.o: In function `PVXMLPlayableFilenameList::PVXMLPlayableFilenameList()': server.cxx:(.text._ZN25PVXMLPlayableFilenameListC2Ev[PVXMLPlayableFilenameList::PVXMLPlayableFilenameList()]+0x13): undefined reference to `vtable for PVXMLPlayableFilenameList' ./obj_linux_x86_r/server.o: In function `WoomeraPlayableFilenameList::OnStop()': server.cxx:(.text._ZN27WoomeraPlayableFilenameList6OnStopEv[WoomeraPlayableFilenameList::OnStop()]+0xf): undefined reference to `PVXMLPlayableFilenameList::OnStop()' ./obj_linux_x86_r/server.o: In function `PVXMLRecordableFilename::PVXMLRecordableFilename()': server.cxx:(.text._ZN23PVXMLRecordableFilenameC2Ev[PVXMLRecordableFilename::PVXMLRecordableFilename()]+0x16): undefined refer ence to `vtable for PVXMLRecordableFilename' ./obj_linux_x86_r/server.o:(.rodata._ZTV27WoomeraPlayableFilenameList[vtable for WoomeraPlayableFilenameList]+0x3c): undefine d reference to `PVXMLPlayableFilenameList::OnRepeat(PVXMLChannel&)' ./obj_linux_x86_r/server.o:(.rodata._ZTV27WoomeraPlayableFilenameList[vtable for WoomeraPlayableFilenameList]+0x54): undefine d reference to `PVXMLPlayable::ReadFrame(PVXMLChannel&, void*, int)' ./obj_linux_x86_r/server.o:(.rodata._ZTI27WoomeraPlayableFilenameList[typeinfo for WoomeraPlayableFilenameList]+0x10): undefi ned reference to `typeinfo for PVXMLPlayableFilenameList' ./obj_linux_x86_r/server.o:(.rodata._ZTV25WoomeraRecordableFilename[vtable for WoomeraRecordableFilename]+0x30): undefined re ference to `PVXMLRecordableFilename::Open(PString const&)' . . . . . wivr.cxx:(.text+0x5464): undefined reference to `PXMLElement::GetElement(int) const' wivr.cxx:(.text+0x5529): undefined reference to `PXML::~PXML()' wivr.cxx:(.text+0x553a): undefined reference to `PXML::~PXML()' collect2: ld returned 1 exit status make: *** [obj_linux_x86_r/woomera] Error 1 root@icetech-server:~/woomera# What's the problem? Any help? Thanks a lot David

1 0

[OpenSER-Users] Replace Openser dns based sip location service by a DHT
by Victor Pascual Ávila 01 Dec '07

01 Dec '07

Hi all, we are working on a P2PSIP prototype and we are considering to couple a DHT Chord-based node with Openser. Current dns based sip location service would be replaced by a DHT, allowing several proxies/registrars to read/write overlays resource records. Any hint or guidelines would be appreciated. Thanks in advance and sorry for cross posting, I'm not sure this issue is related to devel or users. -- Victor Pascual Ávila

1 0

[OpenSER-Users] Changing From: and To: URIs...
by Phil D'Amore 30 Nov '07

30 Nov '07

Hi Everyone... I'm looking for some advice. Let's say I have a To: header in an initial INVITE: To: Bob <sip:8005551212@sip.example.com> Due to carrier requirements, it really needs to be: To: Bob <sip:+18005551212@sip.example.com> I'm not asking how to do it. I know I can use some textops functions to make this happen. I also know that doing this might break something. The uac module already nicely handles the From: header in a way that doesn't break things. I thought about extending this to handle To:, but I worried that the Record-Route header might get too long for some UAs if I wind up having to change both headers. The To tag must also be dealt with somehow, which I think might make it harder to do than From. Using a 302 response is not an option for me, and I'm really trying to avoid getting a B2BUA involved with this right now. Moving from openser 1.1.1 to 1.3 is enough for me without changing my architecture ;). I'm wondering what would be the best way given what openser can do right now (1.3) to re-write that header that doesn't break anything. I'm not adverse to writing some code to make it happen if that is what is needed. Any ideas? Thanks, Phil

3 5

[OpenSER-Users] OpenSER 1.3 - release name
by Bogdan-Andrei Iancu 30 Nov '07

30 Nov '07

Hi, I would like to make a survey to see if people will consider a nice policy to give to the further openser releases not only version numbers, but also names. If so, I would like to be the first to suggest a name for the upcoming openser 1.3 release -"blackcat" (mainly because of the 13 version :D ). Any other suggestions or comments on the topic are welcomed. Thanks and regards, Bogdan

7 11

[OpenSER-Users] OpenSER 1.3 - release date
by Bogdan-Andrei Iancu 30 Nov '07

30 Nov '07

Hi, There are still some bugs that need to be fixed before the release of 1.3. I think 2 weeks should from now on should be enough, so I suggest to try to set the release date to 13th of December. Please let me know your thoughts. Regards and a nice weekend, Bogdan

1 0

[OpenSER-Users] does CPL change SDP parameter on reply message?
by Daniel 30 Nov '07

30 Nov '07

Hi all, if I use <PROXY> in a CPL script, then, how can I change SDP parameter (I want to use media proxy ) in the reply message (200 OK) ? regards, daniel -- Daniel Grotti ________________________ e-mail : d.grotti(a)gmail.com

3 5

[OpenSER-Users] CPL and on reply route
by Daniel 30 Nov '07

30 Nov '07

Hi all, I use CPL script with "Proxy" element, like this: <cpl> <incoming> <lookup source="registration"> <success> <proxy ordering="sequential" /> </success> </lookup> </incoming> </cpl> and I use onreply_route(), where I make the changes on 180/200 reply messages in case of NAT (change callee's SDP parameter and change Callee's Contact hf). When an INVITE is forwarded, through the <PROXY> element, to the callee, then reply messagges (180 Ringing and 200OK) hasn't processed by Onreply_route. So I can't make my NAT control. Why? Regards, daniel -- Daniel Grotti ________________________ e-mail : d.grotti(a)gmail.com

2 1

[OpenSER-Users] openser 1.3 sometimes fails to start
by Robert Dyck 30 Nov '07

30 Nov '07

I am testing openser 1.3.0-pre1-notls svnversion 2:3201. I believe it is failing while starting the child processes for the modules. If it starts successfully it seems to perform normally. I believe the following excerpt from the console might hold the clue. Thanks Rob Nov 29 14:40:30 [10492] DBG:xlog:child_init: init_child [0] pid [10492] Nov 29 14:40:30 [10492] DBG:core:init_mod_child: type=PROC_MAIN, rank=0, module=avpops Nov 29 14:40:30 [10498] DBG:core:io_watch_add: io_watch_add(0x8160900, 6, 4, 0xb5f824a4), fd_no=0 Nov 29 14:40:30 [10498] DBG:core:io_watch_add: io_watch_add(0x8160900, 7, 4, 0xb5f82530), fd_no=1 Nov 29 14:40:30 [10498] DBG:core:io_watch_add: io_watch_add(0x8160900, 8, 4, 0xb5f825bc), fd_no=2 Nov 29 14:40:30 [10498] DBG:core:io_watch_add: io_watch_add(0x8160900, 9, 4, 0xb5f82648), fd_no=3 Nov 29 14:40:30 [10498] DBG:core:io_watch_add: io_watch_add(0x8160900, 12, 4, 0xb5f826d4), fd_no=4 Nov 29 14:40:30 [10498] DBG:core:io_watch_add: io_watch_add(0x8160900, 11, 4, 0xb5f82760), fd_no=5 Nov 29 14:40:30 [10498] ERROR:core:io_watch_add: epoll_ctl failed: Invalid argument [22] Nov 29 14:40:30 [10498] CRITICAL:core:tcp_main_loop: failed to add process 6 (TCP main) unix socket to the fd list Nov 29 14:40:30 [10498] CRITICAL:core:tcp_main_loop: exiting...Nov 29 14:40:30 [10497] INFO:nathelper:rtpp_test: rtp proxy <unix:/var/run/rt pproxy.sock> found, support for it enabled Nov 29 14:40:30 [10497] DBG:core:init_mod_child: type=CHILD, rank=3, module=xlog Nov 29 14:40:30 [10497] DBG:xlog:child_init: init_child [3] pid [10497] Nov 29 14:40:30 [10497] DBG:core:init_mod_child: type=CHILD, rank=3, module=avpops Nov 29 14:40:30 [10497] DBG:core:io_watch_add: io_watch_add(0x8160a60, 11, 1, (nil)), fd_no=0 Nov 29 14:40:30 [10492] INFO:core:handle_sigs: child process 10498 exited normally, status=255 Nov 29 14:40:30 [10492] INFO:core:handle_sigs: terminating due to SIGCHLD Nov 29 14:40:30 [10493] INFO:core:sig_usr: signal 15 received Memory status (pkg): qm_status (0x8181760): heap size= 1048576 used= 44448, used+overhead=71504, free=977072 max used (+overhead)= 71504 dumping all alloc'ed. fragments: 0. N address=0x8186908 frag=0x8186900 size=32 used=1 1. N address=0x8186938 frag=0x8186930 size=16 used=1 2. N address=0x8186958 frag=0x8186950 size=32 used=1 3. N address=0x8186988 frag=0x8186980 size=32 used=1 4. N address=0x81869b8 frag=0x81869b0 size=16 used=1 5. N address=0x81869d8 frag=0x81869d0 size=16 used=1 6. N address=0x81869f8 frag=0x81869f0 size=32 used=1 7. N address=0x8186a28 frag=0x8186a20 size=32 used=1 8. N address=0x8186a58 frag=0x8186a50 size=64 used=1 9. N address=0x8186aa8 frag=0x8186aa0 size=64 used=1 10. N address=0x8186af8 frag=0x8186af0 size=64 used=1

3 3

Re: [OpenSER-Users] auth_db module - get_ha1(): Error while querying database
by Daniel-Constantin Mierla 30 Nov '07

30 Nov '07

Hello, from the logs seems that the content of subscriber table is corrupted. Please attach /usr/local/etc/openser/dbtext/subscriber file and send it to me. Cheers, Daniel On 11/30/07 11:30, Mihail Gluhowchenko wrote: > Hello, > In file log on level 8 when try 9 openser down. > <list of dir(/usr/local/etc/openser/dbtext)> > acc > active_watchers > address > aliases > dbaliases > domaingrp > gw > gw_grp > lcr > location > missed_calls > pdt > presentity > pua > re_grp > silo > speed_dial > subscriber > trusted > uri > usr_preferences > version > watchers > xcap_xml > <end_list_of_dir(/usr/local/etc/openser/dbtext)> > In README file for dbtext error - > break; replace exit; > modparam("auth_db", "calculate_ha1", 1) > replace > modparam("auth_db", "calculate_ha1", yes) > > Regards, > Mihail Gluhowchenko. > > 2007/11/29, Daniel-Constantin Mierla <daniel(a)voice-system.ro > <mailto:daniel@voice-system.ro>>: > > Hello, > > can you list the content of directory: /usr/local/etc/openser/dbtext ? > > Also, if you can set the debug=9 in cofig, run again, get the > output and > send it to me, would help a lot. > > Thanks, > Daniel > > On 11/28/07 13:46, Mihail Gluhowchenko wrote: > > Hello All; > > I`m trying to tune openser-1.2.2 with dbtext data base > > But have some problems. > > I make db use - textdb.sh > > Then add users use - sc.dbtext > > and add to openser.cfg: > > #set module path > > mpath="/usr/local/lib/openser/modules/" > > > > _______________________________________________ > > Users mailing list > > Users(a)lists.openser.org <mailto:Users@lists.openser.org> > > http://lists.openser.org/cgi-bin/mailman/listinfo/users > > > >

1 0

[Serusers] fixup_hostport2proxy
by Tuan Nguyen 30 Nov '07

30 Nov '07

Hi everyone, i have a problem when i try with two version of SER: SER 0.9.6 and SER 2.1to connect with SEMS (the 1. SER proxy ). With SER 0.9.6 i don't have problem when start it, but with SER 2.1 it's so: 0(13446) ERROR: mk_proxy: could not resolve hostname: "localhost" 0(13446) ERROR: fixup_hostport2proxy: bad host name in URI <localhost> I guess, problem locate in this code: log("Forwarding to 5070"); rewritehostport("localhost:5070"); t_relay_to_udp("localhost","5070"); Anyone know that where can i fix this problem with new version of SER? Thanks for responce. Tuan.

2 2

[OpenSER-Users] FYI: [Fwd: [Sip] SIPit 21 summary]
by Klaus Darilion 30 Nov '07

30 Nov '07

-------- Original-Nachricht -------- Betreff: [Sip] SIPit 21 summary Datum: Mon, 19 Nov 2007 14:55:53 -0600 Von: Robert Sparks <rjsparks(a)nostrum.com> An: sip List <sip(a)ietf.org> SIPit 21 was hosted by the BII Group and the Beijing University of Posts and Telecommunications, November 5-9 in Beijing, China. The event was a little smaller than the most recent SIPits: There were 94 attendees from 38 companies visiting from 15 countries. There were 44 teams and around 70 distinct implementations. The majority of the testing I saw was focusing on advanced scenarios rather than basic registration and call setup. As with SIPit 20, the most common area of interoperability problems centered around offer/answer, particularly when attempting to negotiate alternate versions of streams or to explicitly state parameters to be used with a given stream. Forty of the attending teams completed the survey - from those answers: The roles represented (some implementations act in more than one role): 21 endpoints 10 proxy/registrars 3 standalone registrars 5 event servers 4 gateways 6 automaton UAs (voicemail, conference, appserver, etc) 8 b2bua/sbcs 4 UAs with signaling, but without media 1 test/monitoring tool Implementations using each transport for SIP messages: UDP 100% TCP 82% TLS 49% (server auth only) TLS 6% (mutual auth) SCTP 3% DTLS 0% 36% of the implementations supported SIP over IPv6 (up from 25% at SIPit20) 18% supported SIP over IPSec For DNS we had support for: Full RFC3263 : 61% SRV only : 21% A records only : 9% no DNS support : 9% Support for various items: 61% rport 15% sigcomp 22% enum 21% sending multiplexing STUN and SIP 28% receiving multiplexed STUN and SIP 22% RFC4320 fixes 12% identity 70% session-timer There was one implementation of parts of the session-policy framework. There was one implementation of the sip-consent framework. There were two implementations of parts of the sip-config framework (I do not know yet if they worked together). There were three implementations of outbound and four of GRUU. There were two implementations of MSRP present. The endpoints implemented these methods: 100% INVITE, CANCEL, ACK, BYE 87% REGISTER 87% OPTIONS 87% NOTIFY <- still a lot of unsolicted NOTIFYs 87% REFER 77% SUBSCRIBE 77% INFO 70% UPDATE 67% PRACK 47% MESSAGE 33% PUBLISH Support for various extensions in the endpoints: 43% RFC3323 privacy 41% RFC3327 path 13% RFC3840 pref 13% RFC3841 caller-prefs 59% RFC3891 replaces 20% RFC4488 norefersub 0% RFC4538 target-dialog <- There were several folks starting to talk about supporting this Support for various things in the endpoints: 10% ICE (but there was no interoperability - see below) 0% ICE-TCP 13% STUNbis 17% TURN (again, there was no interoperability) 75% symmetric RTP 25% SRTP 0% RTP over DTLS This is how the endpoints answered how they supported multipart/mime: 7% I break if someone sends me multipart/mime 30% I pretend multipart mime doesn't exist if someone sends it to me 20% I ignore multipart/mime, but will proxy it or hand it to my application if it shows up 17% I try to do something useful with multipart/mime I receive, but I never send it 3% I ignore multipart/mime I receive, but I try to send it to do something useful 20% I try to do something useful with multipart/mime I send and receive There were 4 endpoints that would send media over TCP - none of them supported RFC4145 comedia. One of those supported media over TLS. Implementation is all over the map for fork-loop-fix. However, only 3 of the proxy/b2buas present were still vulnerable to the simple form of the attack described in the draft. There were no implementations present with support for location- conveyance or the geopriv common-policy framework. There was one implementation present with support for the RFC4967 dial-string parameter, and one with support for the ecrit service-urn. Of the SIP-Events implementations, the following packages were supported: 62% refer 48% message-summary 38% presence 29% dialog 19% reg 19% conf There was one implementation of each of the following packages: ua-profile certificate/credentials vx-rtcpxp (sipping-rtcp-summary) There was only one implementation of event-lists present. Only 20% of the SIP-Events implementations supported winfo. We had a multiparty sesssion for a full morning focusing on NAT traversal. Basic use of STUN with SIP is hightly interoperable. No two implementations of TURN could even start trying to talk to each other (each having implemented to different points in the recent torrent of changes). I don't think we'll get much implementation feedback until the spec stops making big changes so frequently. No two implementations of ICE worked together. The closest was between two implementations that have worked in the past, but failed during this session when the connectivity checks arrived before the SDP. _______________________________________________ Sip mailing list https://www1.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors(a)cs.columbia.edu for questions on current sip Use sipping(a)ietf.org for new developments on the application of sip

2 1

[Serusers] Segmentation Fault (SER Not Starting)
by Alexandr Volkov 29 Nov '07

29 Nov '07

Hi All, I am having trouble when trying to start SER. I am using Ser 0.9.6 on centos4. When I am trying to start it gives: Segmentation Fault; but only if in 'location' table there is a row with callId starting by number: <field name="callid">49c72d7ed685500e7d844d1cf1357dbd</field> if I change this field in database (simple add any character), ser will start. <field name="callid">a49c72d7ed685500e7d844d1cf1357dbd</field> seems like a bug

1 0

[Serusers] ERROR: forward_reply: no 2nd via found in reply - via parsing error
by Tomasz Zieleniewski 29 Nov '07

29 Nov '07

Hi, I have a chcek via parameter set in the ser.cfg file When ser receives reply with such via header it returns ERROR: forward_reply: no 2nd via found in reply This Via seems to be ok? Via: SIP/2.0/UDP 192.168.0.165:7160;branch=z9hG4bK1589.3bc310b3.1,SIP/2.0/UDP 192.168.0.165:7060;branch=z9hG4bK1589.e1306596.0,SIP/2.0/UDP 192.168.129.74 ;rport=5060;branch=z9hG4bK1589.606a3e61.0,SIP/2.0/UDP 192.168.129.74:5160 ;branch=z9hG4bK1589.a5bd9fb4.0,SIP/2.0/UDP 192.168.129.74;branch= z9hG4bK1589.506a3e61.0,SIP/2.0/UDP 192.168.0.102:7060 ;rport=7060;branch=z9hG4bK-d87543-a228576fa32c0b22-1--d87543- What is wrong? Cheers tomasz

1 0

[Serusers] Unexpected disconnect - lost SIP packets?
by Jeremy A 29 Nov '07

29 Nov '07

Hello, I'm need some help with SIP protocol / SER configuration to resolve a problem. I have a system with a SER instance and a SIP client application running on the same box. SER is 10.50.32.10:5060 APP is 10.50.32.10:5070 Remote SIP server 10.1.39.10 Remote phone is 10.1.39.202 The user agent is registered with the SER instance as extension 1009. It has aliases 1001-1008 and is actually called as 231x which maps onto 100x which then connects to extension 1009. The remote phone makes a call to the user agent application via the remote SIP server and the SER instance. It dials 2311 which gets automagically converted to extension 1009 The call is established but the user application times out and detects a disconnect despite the calling phone not hanging up. In my wireshark trace it seems that SER is ignoring some form of keep-alive from the remote SIP server and this is causing the timeout. The lines of interest include 39, 42, 45, 50, 53, 56, 59 Lines 28 and others similar are on the loopback interface and are packets between port 5060 and 5070 Can someone please advise if the SIP protocol has problems and/or if SER configuration has problems? 22 0.218826 10.50.32.10 -> 127.0.0.1 SIP Request: REGISTER sip:localhost.localdomain 23 0.219570 127.0.0.1 -> 10.50.32.10 SIP Status: 200 OK (1 bindings) 24 19.472555 10.1.39.10 -> 10.50.32.10 SIP/SDP Request: INVITE sip:1001@butler.fesa.sto;transport=udp, with session description 25 19.473394 10.50.32.10 -> 10.1.39.10 SIP Status: 100 trying -- your call is important to us 26 19.473596 10.50.32.10 -> 10.50.32.10 SIP/SDP Request: INVITE sip:1009@10.50.32.10:5070;LINEID=1d5a67e38809, with session description 27 19.484244 10.50.32.10 -> 10.50.32.10 SIP Status: 100 Trying 28 19.725476 10.50.32.10 -> 10.50.32.10 SIP Status: 180 Ringing 29 19.725828 10.50.32.10 -> 10.1.39.10 SIP Status: 180 Ringing 32 21.770798 10.50.32.10 -> 10.50.32.10 SIP/SDP Status: 200 OK, with session description 33 21.782437 10.50.32.10 -> 10.1.39.10 SIP/SDP Status: 200 OK, with session description 38 21.789396 10.50.32.10 -> 10.1.39.202 RTCP Source port: 8001 Destination port: 16391 39 21.800069 10.1.39.10 -> 10.50.32.10 SIP Request: ACK sip:2311@10.50.32.10:5070;LINEID=1d5a67e38809 40 22.278096 10.50.32.10 -> 10.50.32.10 SIP/SDP Status: 200 OK, with session description 41 22.278713 10.50.32.10 -> 10.1.39.10 SIP/SDP Status: 200 OK, with session description 42 22.298101 10.1.39.10 -> 10.50.32.10 SIP Request: ACK sip:2311@10.50.32.10:5070;LINEID=1d5a67e38809 43 23.285536 10.50.32.10 -> 10.50.32.10 SIP/SDP Status: 200 OK, with session description 44 23.288988 10.50.32.10 -> 10.1.39.10 SIP/SDP Status: 200 OK, with session description 45 23.307839 10.1.39.10 -> 10.50.32.10 SIP Request: ACK sip:2311@10.50.32.10:5070;LINEID=1d5a67e38809 48 25.298214 10.50.32.10 -> 10.50.32.10 SIP/SDP Status: 200 OK, with session description 49 25.299105 10.50.32.10 -> 10.1.39.10 SIP/SDP Status: 200 OK, with session description 50 25.317892 10.1.39.10 -> 10.50.32.10 SIP Request: ACK sip:2311@10.50.32.10:5070;LINEID=1d5a67e38809 51 29.306496 10.50.32.10 -> 10.50.32.10 SIP/SDP Status: 200 OK, with session description 52 29.306758 10.50.32.10 -> 10.1.39.10 SIP/SDP Status: 200 OK, with session description 53 29.328420 10.1.39.10 -> 10.50.32.10 SIP Request: ACK sip:2311@10.50.32.10:5070;LINEID=1d5a67e38809 54 33.314736 10.50.32.10 -> 10.50.32.10 SIP/SDP Status: 200 OK, with session description 55 33.318736 10.50.32.10 -> 10.1.39.10 SIP/SDP Status: 200 OK, with session description 56 33.338302 10.1.39.10 -> 10.50.32.10 SIP Request: ACK sip:2311@10.50.32.10:5070;LINEID=1d5a67e38809 57 37.323175 10.50.32.10 -> 10.50.32.10 SIP/SDP Status: 200 OK, with session description 58 37.324791 10.50.32.10 -> 10.1.39.10 SIP/SDP Status: 200 OK, with session description 59 37.347936 10.1.39.10 -> 10.50.32.10 SIP Request: ACK sip:2311@10.50.32.10:5070;LINEID=1d5a67e38809 --> client detects disconnect here Thanks jeremy

3 8

[Serusers] Presence in SIP
by Carlos Angeles 29 Nov '07

29 Nov '07

Hello I have installed Ser-2.0 with the PA module.... I am testing the server with x-lite... When a user is NOTIFYING some event change the server is answering with a Status: 420 Bad Extension.... Is thst SER doesn´t support this kind of presence events? Thanks Carlos _________________________________________________________________ Discover the new Windows Vista http://search.msn.com/results.aspx?q=windows+vista&mkt=en-US&form=QBRE

1 0

[OpenSER-Users] Handling re-INVITES --hellp required
by srinivas Antarvedi 29 Nov '07

29 Nov '07

Hello all, i have users one is on global ip and another behind NAT am using asterisk as media server leg 1: caller : Global ip UAC. callee: asterisk leg2: caller :asterisk callee: NATed UAC. sdp of NATed client is handled at openser reply route at first stage when asterisk re-invites the NATed UAC to bridge the two call-Leg's the sdp from NATed UAC is not changed ,, even if i call t_on_reply in the loose route section of the script.. it is still showing privat ip so finally after 2 or 3 sec's there was an end to the dialog can anybody have any idea to handle re-invite's 200 ok SDP mangling? please help me out.. Thanks in advance regards srinivas -- Srinivas Antarvedi

3 3

[OpenSER-Users] auth_db module - get_ha1(): Error while querying database
by Mihail Gluhowchenko 29 Nov '07

29 Nov '07

Hello All; I`m trying to tune openser-1.2.2 with dbtext data base But have some problems. I make db use - textdb.sh Then add users use - sc.dbtext and add to openser.cfg: #set module path mpath="/usr/local/lib/openser/modules/" # use dbtext database loadmodule "dbtext.so" loadmodule "sl.so" loadmodule "tm.so" loadmodule "rr.so" loadmodule "maxfwd.so" loadmodule "usrloc.so" loadmodule "registrar.so" loadmodule "textops.so" loadmodule "mi_fifo.so" # Uncomment this if you want digest authentication loadmodule "auth.so" loadmodule "auth_db.so" # ----------------- setting module-specific parameters --------------- # -- mi_fifo params -- modparam("mi_fifo", "fifo_name", "/tmp/openser_fifo") # -- usrloc params -- #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) # -- auth params -- # use dbtext database for persistent storage modparam("usrloc", "db_mode", 2) modparam("usrloc|auth_db", "db_url", "dbtext:///usr/local/etc/openser/dbtext") # Uncomment if you are using auth module # modparam("auth_db", "calculate_ha1", yes) # # If you set "calculate_ha1" parameter to yes (which true in this config), # uncomment also the following parameter) modparam("auth_db", "user_column", "username") modparam("auth_db", "password_column", "password") modparam("auth_db", "domain_column", "domain") # -- rr params -- # add value to ;lr param to make some broken UAs happy modparam("rr", "enable_full_lr", 1) # ------------------------- request routing logic ------------------- # main routing logic route{ # initial sanity checks -- messages with # max_forwards==0, or excessively long requests if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); log(1, "Too Many Hops\n"); exit; }; if (msg:len >= 2048 ) { sl_send_reply("513", "Message too big"); log(1, "Message too big\n"); exit; }; # we record-route all messages -- to make sure that # subsequent messages will go through our proxy; that's # particularly good if upstream and downstream entities # use different transport protocol if (!method=="REGISTER") record_route(); # subsequent messages withing a dialog should take the # path determined by record-routing if (loose_route()) { # mark routing logic in request append_hf("P-hint: rr-enforced\r\n"); route(1); }; if (!uri==myself) { # mark routing logic in request append_hf("P-hint: outbound\r\n"); # if you have some interdomain connections via TLS #if(uri=~"@tls_domain1.net") { # t_relay("tls:domain1.net"); # exit; #} else if(uri=~"@tls_domain2.net") { # t_relay("tls:domain2.net"); # exit; #} route(1); }; # if the request is for other domain use UsrLoc # (in case, it does not work, use the following command # with proper names and addresses in it) if (uri==myself) { if (method=="REGISTER") { log(1, "this is a request REGISTER users\n"); if (!www_authorize("my.domain", "subscriber")) { log(1, "this is a www_challenge\n"); www_challenge("my.domain", "0"); exit; }; save("location"); exit; }; but when trying REGISTER user use(sjphone) in log i see: Nov 28 17:30:03 devel s-eltex[12797]: this is a request for my.domain users Nov 28 17:30:03 devel s-eltex[12797]: this is a request REGISTER users Nov 28 17:30:03 devel s-eltex[12797]: this is a www_challenge Nov 28 17:30:03 devel s-eltex[12794]: this is a request for my.domain users Nov 28 17:30:03 devel s-eltex[12794]: this is a request REGISTER users Nov 28 17:30:03 devel s-eltex[12794]: get_ha1(): Error while querying database In sjphone LOG i see: Service unavailable server error; What do I adjust not correctly?

2 1

[OpenSER-Users] t_relay can not handle PRACK retransmission
by Klaus Darilion 29 Nov '07

29 Nov '07

Hi! I have encountered this problem at an openser 1.1.1 proxy: Client Proxy Client ---PRACK------> ------PRACK-----> retansmission -----PRACK-------> here at this point (when openser receives the PRACK retransmission) t_relay fails: ERROR: t_newtran: transaction already in process 0xb66e7880 Is this a known problem? Were there some fixes to 1.1 or 1.2 branch? regards klaus

2 4

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