THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#86 - dialplan reload, out of memory
User who did this - Kim Jakobsson (kjakobsson)
----------
Coming back to this issue, sorry for the delay.
Yes, I have read the README. I this in the openser.cfg:
modparam("dialplan", "fetch_rows", 5000)
and there are 1800 lines in the dialplan table.
Restarting the proxy loads all the data, but "sercmd mi dp_reload" fails with an error as described.
-Kim
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=86#comment152
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
Hi!
After rls subscription Kamailio sends out the following message:
SUBSCRIBE sip:asdfasf@domain SIP/2.0.
Via: SIP/2.0/UDP 83.136.32.148;branch=z9hG4bKa552.759c4dd5.0.
To: sip:asdfasf@domain.
From: sip:klaus3000@domain;tag=0ba80b241f8a9fa52b4df857d4681d35-1516.
CSeq: 10 SUBSCRIBE.
Call-ID: 7f9f6f80-17150(a)83.136.32.148.
Content-Length: 0.
User-Agent: kamailio (3.1.1 (i386/linux)).
Max-Forwards: 70.
Event: presence.
Contact: <sip:83.136.32.148:5060;transport=udp>.
Expires: 100.
Max-Forwards: 70.
Support: eventlist.
Seems there is a bug as it contains 2 Max-Forwards header. Seems like
the hard-coding in rls/subscribe.c in line 784 is needless.
In the same line, Support: eventlist should be replaced with
Supported: eventlist.
regards
Klaus
Hello,
I have experienced some crashes in the topoh module when someone ran a
scanner against the SIP server. Log and backtrace below (I've changed
the server ip to 192.168.31.45 intentionally).
Note: I'm not using local ip as topoh mask_ip.
version: kamailio 3.1.0 (i386/linux)
Dec 14 06:22:47 localhost /usr/local/sbin/kamailio[32348]: INFO:
<script>: [152309] REGISTER sip:abdol@192.168.31.45
From:sip:abdol@192.168.31.45,tag=6162646f6c0131323538353537353239
To:sip:abdol@192.168.31.45,tag=<null>
Call-ID:2502699686 Cseq:1 Contact:sip:abdol@192.168.31.45
<219.237.209.148:5063>
Dec 14 06:22:47 localhost /usr/local/sbin/kamailio[32347]: INFO:
<script>: [151941] REGISTER sip:abdul@192.168.31.45
From:sip:abdul@192.168.31.45,tag=616264756c01353930353937393039
To:sip:abdul@192.168.31.45,tag=<null> Call-ID:3690987863 Cseq:1
Contact:sip:abdul@192.168.31.45 <219.237.209.148:5063>
Dec 14 06:22:47 localhost /usr/local/sbin/kamailio[32341]: ALERT: <core>
[main.c:744]: core was generated
Core was generated by `/usr/local/sbin/kamailio -P /var/run/kamailio.pid'.
Program terminated with signal 11, Segmentation fault.
#0 0x00dc05ac in th_skip_msg (msg=0xbfced200) at th_msg.c:1043
1043 if((get_cseq(msg)->method_id)&(METHOD_REGISTER|METHOD_PUBLISH))
(gdb) bt
#0 0x00dc05ac in th_skip_msg (msg=0xbfced200) at th_msg.c:1043
#1 0x00dc1066 in th_msg_received (data=0xbfced5fc) at topoh_mod.c:198
#2 0x080864d5 in sr_event_exec (type=1, data=0xbfced5fc) at events.c:87
#3 0x080c1a3d in receive_msg (
buf=0x8276720 "ACK sip:aarti@192.168.31.45 SIP/2.0\r\nVia:
SIP/2.0/UDP
219.237.209.148:5063;branch=z9hG4bK-2573018079;rport\r\nContent-Length:
0\r\nFrom: \"aarti\"<sip:aarti@192.168.31.45>;
tag=616172746901313238373537393"..., len=399, rcv_info=0xbfced6ec) at
receive.c:117
#4 0x0813580e in udp_rcv_loop () at udp_server.c:532
#5 0x08098f43 in main_loop () at main.c:1554
#6 0x0809b62d in main (argc=3, argv=0xbfced9b4) at main.c:2398
Core was generated by `/usr/local/sbin/kamailio -P /var/run/kamailio.pid'.
Program terminated with signal 11, Segmentation fault.
#0 0x00dc05ac in th_skip_msg (msg=0xbfced200) at th_msg.c:1043
1043 if((get_cseq(msg)->method_id)&(METHOD_REGISTER|METHOD_PUBLISH))
(gdb) bt
#0 0x00dc05ac in th_skip_msg (msg=0xbfced200) at th_msg.c:1043
#1 0x00dc1066 in th_msg_received (data=0xbfced5fc) at topoh_mod.c:198
#2 0x080864d5 in sr_event_exec (type=1, data=0xbfced5fc) at events.c:87
#3 0x080c1a3d in receive_msg (
buf=0x8276720 "ACK sip:abdenace@192.168.31.45 SIP/2.0\r\nVia:
SIP/2.0/UDP
219.237.209.148:5063;branch=z9hG4bK-2970175437;rport\r\nContent-Length:
0\r\nFrom: \"abdenace\"<sip:abdenace@192.168.31.45>;
tag=616264656e61636501"..., len=422, rcv_info=0xbfced6ec) at receive.c:117
#4 0x0813580e in udp_rcv_loop () at udp_server.c:532
#5 0x08098f43 in main_loop () at main.c:1554
#6 0x0809b62d in main (argc=3, argv=0xbfced9b4) at main.c:2398
--
Sincerely,
Andrew Pogrebennyk
Dear Team,
I'm using rtpproxy-1.2.1 with SER to relay RTP in case of NATted
scenarios. I'm not been able to enable the logs in rtpproxy. Without the
logs, it's very hard to debug.
Corresponding details are as follows-
rtpproxy running with option "-d DBUG:LOG_LOCAL3"
Entry in syslog.conf is made as "local3.debug /rtpproxy/logs.log"
Log file is created at the mentioned path with write permission.
Please help me enabling the logs ASAP.
Regards,
--Piyush Bansal
The information contained in this e-mail message is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you should return it to the sender immediately. Please note that while we scan all e-mails for viruses we cannot guarantee that any e-mail is virus-free and accept no liability for any damage caused by any virus transmitted by this email.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#108 - UAC Outgoing Registration Failed Authentication
User who did this - bernhards (bernhards)
----------
Ok. The password could be wrong on the other side. But its OK.
About the "Asterisk Registration" problem I find something interessting:
SNOM 360 and Twinkle re-use the same "Call-ID" and "FROM-Tag" for the REGISTER with credentials but leave the "TO-Tag" blank. This does work with Asterisk.
Within the Asterisk source code I added some debug informations. Asterisk could not determine to which "dialog" (if this is the right terminology) the REGISTER with credentials belongs to.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=108#comment151
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.