sr-users

sr-users@lists.kamailio.org

37 participants
37547 discussions

RE: [Serusers] error ser-0.10.99-dev35-pa-4_src or the last cvs versionof ser
by İlker Aktuna (Koç.net) 24 May '06

24 May '06

Hi Laurent, I also have this error when compiling. On which linux distribution you are installing it ? Did you find a solution ? Btw, do you also have problems with presence and watcherinfo. These features are not working on my installation. I keep getting "t_uac: no socket found" and "Can't send watcherinfo notification" errors. Thanks, ilker ________________________________ From: serusers-bounces(a)iptel.org [mailto:serusers-bounces@iptel.org] On Behalf Of Laurent Schweizer Sent: Tuesday, May 02, 2006 10:58 AM To: serusers(a)iptel.org; serdev(a)iptel.org Subject: [Serusers] error ser-0.10.99-dev35-pa-4_src or the last cvs versionof ser Hello, i try to compile ser-0.10.99-dev35-pa-4_src or the last cvs version of ser and i have always rhis error : Laurent gcc -g -O9 -funroll-loops -Wcast-align -Wall -minline-all-stringops -falign-loops -DNAME='"sercmd"' -DVERSION='"0.1"' -DARCH='"x86_64"' -DOS='"linux"' -D__CPU_x86_64 -D__OS_linux -DUSE_READLINE -c sercmd.c -o sercmd.o gcc -Wl,-O2 -Wl,-E parse_listen_id.o sercmd.o -lresolv -lreadline -o sercmd /usr/lib/gcc/x86_64-redhat-linux/3.4.5/../../../../lib64/libreadline.so: undefined reference to `tgetnum' /usr/lib/gcc/x86_64-redhat-linux/3.4.5/../../../../lib64/libreadline.so: undefined reference to `tgoto' /usr/lib/gcc/x86_64-redhat-linux/3.4.5/../../../../lib64/libreadline.so: undefined reference to `tgetflag' /usr/lib/gcc/x86_64-redhat-linux/3.4.5/../../../../lib64/libreadline.so: undefined reference to `BC' /usr/lib/gcc/x86_64-redhat-linux/3.4.5/../../../../lib64/libreadline.so: undefined reference to `tputs' /usr/lib/gcc/x86_64-redhat-linux/3.4.5/../../../../lib64/libreadline.so: undefined reference to `PC' /usr/lib/gcc/x86_64-redhat-linux/3.4.5/../../../../lib64/libreadline.so: undefined reference to `tgetent' /usr/lib/gcc/x86_64-redhat-linux/3.4.5/../../../../lib64/libreadline.so: undefined reference to `UP' /usr/lib/gcc/x86_64-redhat-linux/3.4.5/../../../../lib64/libreadline.so: undefined reference to `tgetstr' collect2: ld returned 1 exit status make[1]: *** [sercmd] Error 1 make[1]: Leaving directory `/home/installsrc/ser_cvs/sip_router/utils/sercmd' ERROR: utils/sercmd/sercmd not compiled <http://387555.sigclick.mailinfo.com/sigclick/030A0700/05074D0E/07034C07/902…> _____________________________________________________________________________________________________________________________________________ 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] real loading
by unplug 24 May '06

24 May '06

I am using sipp to test the openser with the following result. It will create message 481 after a certain traffic. In what conditioin that openser will send 2 BYE to CISCO? When I increase the concurrent call to about 50, the system becomes unstable and almost hanged. I am concerning about the real loading of the openser. Does anyone can help me? --------------my scenario---------- call: 3 / sec concurrent call: 30 total call made: 1002 failed call: 21 failure rate: 21/1002 >From the log shown below, most of the error are created with message 481. SIP/2.0 481 Call Leg/Transaction Does Not Exist 10.30.18.235 10.30.18.234 10.30.0.211 UA-------------------BYE--> openser -- BYE--> CISCO -- BYE --> CISCO <-- 481 -- CISCO UA <------------------- 481--openser U 10.30.18.235:5060 -> 10.30.18.234:5060 BYE sip:936418703@10.30.0.211:5060 SIP/2.0. Via: SIP/2.0/UDP 10.30.18.235:5060;branch=z9hG4bK-104-10. Route: <sip:10.30.18.234;ftag=104;lr=on;nat=yes>. From: sipp <sip:889642688756@10.30.18.235:5060>;tag=104. To: sut <sip:36418703@10.30.18.234:5060>;tag=145085F8-1DF8. Call-ID: 104-13187(a)10.30.18.235. CSeq: 2 BYE. Contact: sip:889642688756@10.30.18.235:5060. Max-Forwards: 70. Subject: Performance Test. Content-Length: 0. U 10.30.18.234:5060 -> 10.30.0.211:5060 BYE sip:936418703@10.30.0.211:5060 SIP/2.0. Record-Route: <sip:10.30.18.234;ftag=104;lr=on>. Via: SIP/2.0/UDP 10.30.18.234;branch=z9hG4bKadce.370d22c5.0. Via: SIP/2.0/UDP 10.30.18.235:5060;rport=5060;branch=z9hG4bK-104-10. From: sipp <sip:889642688756@10.30.18.235:5060>;tag=104. To: sut <sip:36418703@10.30.18.234:5060>;tag=145085F8-1DF8. Call-ID: 104-13187(a)10.30.18.235. CSeq: 2 BYE. Contact: sip:889642688756@10.30.18.235:5060. Max-Forwards: 69. Subject: Performance Test. Content-Length: 0. U 10.30.18.234:5060 -> 10.30.0.211:5060 BYE sip:936418703@10.30.0.211:5060 SIP/2.0. Record-Route: <sip:10.30.18.234;ftag=104;lr=on>. Via: SIP/2.0/UDP 10.30.18.234;branch=z9hG4bKadce.370d22c5.0. Via: SIP/2.0/UDP 10.30.18.235:5060;rport=5060;branch=z9hG4bK-104-10. From: sipp <sip:889642688756@10.30.18.235:5060>;tag=104. To: sut <sip:36418703@10.30.18.234:5060>;tag=145085F8-1DF8. Call-ID: 104-13187(a)10.30.18.235. CSeq: 2 BYE. Contact: sip:889642688756@10.30.18.235:5060. Max-Forwards: 69. Subject: Performance Test. Content-Length: 0. U 10.30.0.211:53419 -> 10.30.18.234:5060 SIP/2.0 481 Call Leg/Transaction Does Not Exist. Via: SIP/2.0/UDP 10.30.18.234;branch=z9hG4bKadce.370d22c5.0,SIP/2.0/UDP 10.30.18.235:5060;rport=5060;branch=z9hG4bK-104-10. From: sipp <sip:889642688756@10.30.18.235:5060>;tag=104. To: sut <sip:36418703@10.30.18.234:5060>;tag=145085F8-1DF8. Call-ID: 104-13187(a)10.30.18.235. CSeq: 2 BYE. Content-Length: 0. U 10.30.18.234:5060 -> 10.30.18.235:5060 SIP/2.0 481 Call Leg/Transaction Does Not Exist. Via: SIP/2.0/UDP 10.30.18.235:5060;rport=5060;branch=z9hG4bK-104-10. From: sipp <sip:889642688756@10.30.18.235:5060>;tag=104. To: sut <sip:36418703@10.30.18.234:5060>;tag=145085F8-1DF8. Call-ID: 104-13187(a)10.30.18.235. CSeq: 2 BYE. Content-Length: 0.

2 2

[Users] Mediaproxy module, Symmetric RTP and softphone client
by Antoine Fressancourt 24 May '06

24 May '06

Hello, I wish to set up Openser in order to use the mediaproxy module to perform NAT traversal. I have tried to figure out which client to use, as it is required that the client is able to perform symmetric RTP operations. So I ask you all about which kind of softphone client you use in conjunction with the mediaproxy module, in which configuration... I wish to use X-lite or an open-source client, do you have any clue ? Thanks in advance for your help. Antoine Fressancourt

4 5

[Serusers] route certain sip invites to a certain sip server
by Gould, Aaron 23 May '06

23 May '06

How do I tell ser to route invites for every sip uri beginning with the number 1 to another sip server? I would want to route 1000(a)domain.com , 1001(a)domain.com and 1002(a)domain.com all to 5.0.0.10 my ser box is 0.8.12 on solaris 10 (5.0.0.12) 5.0.0.10 is a cisco call manager 4.0 with a sip trunk this sccp (skinny) to sip bridging is working a little bit but not completely. i get one-way audio then the calls disconnect after about 10 seconds if i dial sip to sccp. but if i dial sccp to sip, then the call rings through, but media (rtp) never flows either way and call drops after ~33 seconds in debugging a little with the cisco tac, we've seen that the TO: field in a invite to the ccm box is coming in with the wrong address...it's coming in 1001(a)5.0.0.12 but it seems that it should say 1001(a)5.0.0.10 is there a way to fix this? aaron

1 0

[Serusers] DEBUG: retransmission_handler : request resending (t=0x2a9753a648, INVITE si ... )
by rusl 23 May '06

23 May '06

Hello, I'm having a problem.... Upon successful connection of a call, these messages appear, the SER server then automatically sends BYE to the main switch after exactly 30 seconds. Any ideas? Rusl. May 23 20:26:39 ex openser[6277]: DEBUG: timer routine:1,tl=0x2a9753fde8 next=(nil) May 23 20:26:39 ex openser[6277]: DEBUG: timer routine:4,tl=0x2a9753a828 next=(nil) May 23 20:26:39 ex openser[6277]: DEBUG: retransmission_handler : request resending (t=0x2a9753a648, INVITE si ... ) May 23 20:26:39 ex openser[6277]: DEBUG: add_to_tail_of_timer[5]: 0x2a9753a828 May 23 20:26:39 ex openser[6277]: DEBUG: retransmission_handler : done May 23 20:26:41 ex openser[6277]: DEBUG: timer routine:5,tl=0x2a9753a828 next=(nil) May 23 20:26:41 ex openser[6277]: DEBUG: retransmission_handler : request resending (t=0x2a9753a648, INVITE si ... ) May 23 20:26:41 ex openser[6277]: DEBUG: add_to_tail_of_timer[6]: 0x2a9753a828 May 23 20:26:41 ex openser[6277]: DEBUG: retransmission_handler : done May 23 20:26:43 ex openser[6277]: DEBUG: timer routine:2,tl=0x2a9753fc68 next=(nil) May 23 20:26:43 ex openser[6277]: DEBUG: wait_handler : removing 0x2a9753fbe8 from table May 23 20:26:43 ex openser[6277]: DEBUG: delete transaction 0x2a9753fbe8 May 23 20:26:43 ex openser[6277]: DEBUG: wait_handler : done May 23 20:26:43 ex openser[6276]: udp_rcv_loop: probing packet received from 193.4.117.138 57875 May 23 20:26:45 ex openser[6277]: DEBUG: timer routine:6,tl=0x2a9753a828 next=(nil) May 23 20:26:45 ex openser[6277]: DEBUG: retransmission_handler : request resending (t=0x2a9753a648, INVITE si ... ) May 23 20:26:45 ex openser[6277]: DEBUG: add_to_tail_of_timer[7]: 0x2a9753a828 May 23 20:26:45 ex openser[6277]: DEBUG: retransmission_handler : done May 23 20:26:49 ex openser[6277]: DEBUG: timer routine:7,tl=0x2a9753a828 next=(nil) May 23 20:26:49 ex openser[6277]: DEBUG: retransmission_handler : request resending (t=0x2a9753a648, INVITE si ... ) May 23 20:26:49 ex openser[6277]: DEBUG: add_to_tail_of_timer[7]: 0x2a9753a828 May 23 20:26:49 ex openser[6277]: DEBUG: retransmission_handler : done May 23 20:26:53 ex openser[6277]: DEBUG: timer routine:7,tl=0x2a9753a828 next=(nil) May 23 20:26:53 ex openser[6277]: DEBUG: retransmission_handler : request resending (t=0x2a9753a648, INVITE si ... ) May 23 20:26:53 ex openser[6277]: DEBUG: add_to_tail_of_timer[7]: 0x2a9753a828 May 23 20:26:53 ex openser[6277]: DEBUG: retransmission_handler : done May 23 20:26:53 ex openser[6276]: udp_rcv_loop: probing packet received from 193.4.117.138 57875 May 23 20:26:57 ex openser[6277]: DEBUG: timer routine:7,tl=0x2a9753a828 next=(nil) May 23 20:26:57 ex openser[6277]: DEBUG: retransmission_handler : request resending (t=0x2a9753a648, INVITE si ... ) May 23 20:26:57 ex openser[6277]: DEBUG: add_to_tail_of_timer[7]: 0x2a9753a828 May 23 20:26:57 ex openser[6277]: DEBUG: retransmission_handler : done May 23 20:27:01 ex openser[6277]: DEBUG: timer routine:7,tl=0x2a9753a828 next=(nil) May 23 20:27:01 ex openser[6277]: DEBUG: retransmission_handler : request resending (t=0x2a9753a648, INVITE si ... ) May 23 20:27:01 ex openser[6277]: DEBUG: add_to_tail_of_timer[7]: 0x2a9753a828 May 23 20:27:01 ex openser[6277]: DEBUG: retransmission_handler : done May 23 20:27:04 ex openser[6276]: udp_rcv_loop: probing packet received from 193.4.117.138 57875 May 23 20:27:05 ex openser[6277]: DEBUG: timer routine:7,tl=0x2a9753a828 next=(nil) May 23 20:27:05 ex openser[6277]: DEBUG: retransmission_handler : request resending (t=0x2a9753a648, INVITE si ... ) May 23 20:27:05 ex openser[6277]: DEBUG: add_to_tail_of_timer[7]: 0x2a9753a828 May 23 20:27:05 ex openser[6277]: DEBUG: retransmission_handler : done May 23 20:27:08 ex openser[6277]: DEBUG: timer routine:0,tl=0x2a9753a848 next=(nil) May 23 20:27:08 ex openser[6277]: DEBUG: final_response_handler:stop retr. and send CANCEL (0x2a9753a648) May 23 20:27:08 ex openser[6277]: DEBUG:tm:t_should_relay_response: T_code=100, new_code=408 May 23 20:27:08 ex openser[6277]: DEBUG:tm:relay_reply: branch=0, save=0, relay=0 May 23 20:27:08 ex openser[6277]: parse_headers: flags=ffffffffffffffff

1 0

[Serusers] RE: PA error sending notifies
by İlker Aktuna (Koç.net) 23 May '06

23 May '06

So you are not able to use presence but other traffic (IM, voice etc.) is fine ? Do you know the xml parser library that your system has installed ? Vaclav, which library version do you use ? Thanks, ilker -----Original Message----- From: samuel [mailto:samu60@gmail.com] Sent: Tuesday, May 23, 2006 5:05 PM To: İlker Aktuna (Koç.net) Cc: Vaclav Kubart; serusers(a)lists.iptel.org Subject: Re: PA error sending notifies Unfortunately I had no more time to look into it, so I have no more progress..I just saw that the contact header was not properly parsed and there were problems when selecting the local socket where to send the notifies from...I hope in the following weeks I find some more time to spend on it. Samuel. 2006/5/23, İlker Aktuna (Koç. net ) <ilkera(a)koc.net>: > > > > > Hi Samuel, > > Did you solve the issue where sending notifies would fail with error > code -7 ? > > "Can't send watcherinfo notification (-7)" > > If you solved it can you tell me how ? > > I believe the problem is occuring while creating the headers. Because > in "notify.c" I see that -7 is returned only while creating headers. > > Regards, > 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. > ______________________________________________________________________ > ______________________________________________________________________ > _ > <http://387555.sigclick.mailinfo.com/sigclick/0A090704/070D4E06/0F034C03/191…> _____________________________________________________________________________________________________________________________________________ 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

[Serusers] PA error sending notifies
by İlker Aktuna (Koç.net) 23 May '06

23 May '06

Hi Samuel, Did you solve the issue where sending notifies would fail with error code -7 ? "Can't send watcherinfo notification (-7)" If you solved it can you tell me how ? I believe the problem is occuring while creating the headers. Because in "notify.c" I see that -7 is returned only while creating headers. Regards, ilker <http://387555.sigclick.mailinfo.com/sigclick/01090E01/07014F06/07084506/121…> _____________________________________________________________________________________________________________________________________________ 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

RE: [Serusers] SER cannot receives sip messages
by Pletli Antal 23 May '06

23 May '06

I also use 0.8.14, and this version is stable... -----Original Message----- From: serusers-bounces(a)iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Cesc Sent: Tuesday, May 23, 2006 3:57 PM To: Andrey Kouprianov Cc: serusers(a)lists.iptel.org Subject: Re: [Serusers] SER cannot receives sip messages No, didn't try 0.9.4 ... at least not extensibly enough to say it stops responding. The thing is that only sockets stop working ... serctl moni keeps doing its job ... Cesc On 5/23/06, Andrey Kouprianov <andrey.kouprianov(a)gmail.com> wrote: > > Did you guys use 0.9.4? How did it work? Im using 0.9.6 as well > (migrated like a couple of months back). Should I downgrade back to 0.9.4? > > Im also facing many problems with serweb. I cant do CTD or IM from it. > :( I've been told it's some kind of socket selection problem, and > they're currently working on it. > > > On 5/23/06, Cesc <cesc.santa(a)gmail.com> wrote: > > Actually, i am suffering from the same ... i guess. I use 0.9.6. It > > is not once a month, but every few days ... i use a monitor script > > which pings with bogus register messages to the SER every few seconds. > > And after a while, no more messages are processed (not udp, not tcp) ... > > For me restarting ser is all is needed, but is annoying ... > > any idea on how to "investigate" this? > > > > Cesc > > > > On 5/23/06, Pletli Antal <a.pletli(a)euromacc.hu> wrote: > > > > > > > > > Hi list! > > > > > > I use ser version 0.9.5-pre4. > > > > > > About once in a month SER doesn't reveive SIP messages. The udp > > > buffer > of > > > port number 5060 become full. In this case i switch ser to debug > > > mode, > but i > > > cannot see any incoming message. Restarting ser sometimes helps, > > > but in > some > > > cases i have to restart the server machine. I cannot see any error > message > > > in syslog file. The databese connection and radius server works > correctly. > > > > > > Is this a network problem or any known problem? > > > > > > Best regards: > > > > > > Antal > > > _______________________________________________ > > > 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 > > > > > _______________________________________________ > 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

1 0

[Serusers] SER cannot receives sip messages
by Pletli Antal 23 May '06

23 May '06

Hi list! I use ser version 0.9.5-pre4. About once in a month SER doesn't reveive SIP messages. The udp buffer of port number 5060 become full. In this case i switch ser to debug mode, but i cannot see any incoming message. Restarting ser sometimes helps, but in some cases i have to restart the server machine. I cannot see any error message in syslog file. The databese connection and radius server works correctly. Is this a network problem or any known problem? Best regards: Antal

3 3

[Users] AVP/pseudo variables support for core
by Klaus Darilion 23 May '06

23 May '06

Hi! Is this supported (planned)? E.g. I need it for force_send_socket("$avp(s:socket)") regards klaus

2 1

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