I'll try first with the debug in kamailio... I'll let you know in a few minutes...
2009/6/27 Raúl Alexis Betancor Santana rabs@dimension-virtual.com
On Saturday 27 June 2009 02:10:36 Uriel Rozenbaum wrote:
Oki doki... how can I do that? I really don't know how to do it.
I don't know witch server are you using, but on PostgreSQL, you have to set an option on the postgresql.conf file that allow your to dump by syslog all the DDL statements the server receives.
I also beleive that kamailio, if you put it on debug level 6 or more, will dump the SQL statements it's sending out.
-- Raúl Alexis Betancor Santana Dimensión Virtual
Sorry Raul, I get the same output on the debug from Kamailio.
I'm using mysql, how can I dump DDL statements on that?
On Sat, Jun 27, 2009 at 11:45 AM, Uriel Rozenbaum <uriel.rozenbaum@gmail.com
wrote:
I'll try first with the debug in kamailio... I'll let you know in a few minutes...
2009/6/27 Raúl Alexis Betancor Santana rabs@dimension-virtual.com
On Saturday 27 June 2009 02:10:36 Uriel Rozenbaum wrote:
Oki doki... how can I do that? I really don't know how to do it.
I don't know witch server are you using, but on PostgreSQL, you have to set an option on the postgresql.conf file that allow your to dump by syslog all the DDL statements the server receives.
I also beleive that kamailio, if you put it on debug level 6 or more, will dump the SQL statements it's sending out.
-- Raúl Alexis Betancor Santana Dimensión Virtual
On Saturday 27 June 2009 15:51:32 Uriel Rozenbaum wrote:
Sorry Raul, I get the same output on the debug from Kamailio.
I'm using mysql, how can I dump DDL statements on that?
If you run Kamailio with debug level set to 6 and stdErr output, with kamailio -D you should view the output in the console with the SQL statements.
With MySQL I don't know, I use PostgreSQL, take a look at mysql manual or search on google.
Hi,
I have an old openser13x which is used only to control my sems voicemail and voice service.
Some may know that speex payload format was published as an rfc last week and the last change before publication was the addition of the "quote" for the mode parameter.
a=fmtp:98 mode="6,any"
It's pretty clear that the '"' character is messing up the mi_datagram exchange.
Jun 28 15:12:14 ns26829 Sems[30885]: Debug: (AmUtils.cpp)(write_to_socket)(588): sending: <:t_reply: 200 OK 56471:1271880648 784D98C0-4A476C2E000F397\ 7-B6C56BB0 "Contact: sip:welcome@91.121.81.212:5070^M Content-Type: application/sdp^M " "v=0^M o=- 0 0 IN IP4 91.121.81.212^M s=session^M c=IN IP4 \ 91.121.81.212^M t=0 0^M m=audio 11066 RTP/AVP 98 0 8 101^M a=rtpmap:98 speex/8000^M a=fmtp:98 mode="6,any";cng=on^M a=rtpmap:0 PCMU/8000^M a=rtpmap:8\ PCMA/8000^M a=rtpmap:101 telephone-event/8000^M a=fmtp:101 0-15^M " > Jun 28 15:12:14 ns26829 Sems[30885]: Debug: (AmUtils.cpp)(write_to_socket)(614): write to unix socket: completed Jun 28 15:12:15 ns26829 /home/jack/install13x/sbin/openser[3328]: ERROR:mi_datagram:mi_datagram_parse_node: didn't find newline case1 Jun 28 15:12:15 ns26829 /home/jack/install13x/sbin/openser[3328]: ERROR:mi_datagram:mi_datagram_parse_node: parse error around 6 Jun 28 15:12:15 ns26829 /home/jack/install13x/sbin/openser[3328]: ERROR:mi_datagram:mi_datagram_parse_tree: parse error! Jun 28 15:12:15 ns26829 /home/jack/install13x/sbin/openser[3328]: ERROR:mi_datagram:mi_datagram_server: failed to parse the MI tree Jun 28 15:12:15 ns26829 Sems[30885]: Debug: (UnixSocketAdapter.cpp)(cacheMsg)(90): recv-ed: <<400 parse error in command>> Jun 28 15:12:15 ns26829 Sems[30885]: Error: (UnixSocketAdapter.cpp)(send_msg)(531): SER answered: 400 parse error in command Jun 28 15:12:15 ns26829 Sems[30885]: Error: (AmSession.cpp)(onInvite)(695): 500 could not send response
Question is: what's the best option for me to workaround this!
Aymeric MOIZARD / ANTISIP amsip - http://www.antisip.com osip2 - http://www.osip.org eXosip2 - http://savannah.nongnu.org/projects/exosip/
On Sun, 28 Jun 2009, Aymeric Moizard wrote:
Hi,
I have an old openser13x which is used only to control my sems voicemail and voice service.
I just checked with kamailio15x and the same error happens in mi_datagram.
tks Aymeric
Some may know that speex payload format was published as an rfc last week and the last change before publication was the addition of the "quote" for the mode parameter.
a=fmtp:98 mode="6,any"
It's pretty clear that the '"' character is messing up the mi_datagram exchange.
Jun 28 15:12:14 ns26829 Sems[30885]: Debug: (AmUtils.cpp)(write_to_socket)(588): sending: <:t_reply: 200 OK 56471:1271880648 784D98C0-4A476C2E000F397\ 7-B6C56BB0 "Contact: sip:welcome@91.121.81.212:5070^M Content-Type: application/sdp^M " "v=0^M o=- 0 0 IN IP4 91.121.81.212^M s=session^M c=IN IP4 \ 91.121.81.212^M t=0 0^M m=audio 11066 RTP/AVP 98 0 8 101^M a=rtpmap:98 speex/8000^M a=fmtp:98 mode="6,any";cng=on^M a=rtpmap:0 PCMU/8000^M a=rtpmap:8\ PCMA/8000^M a=rtpmap:101 telephone-event/8000^M a=fmtp:101 0-15^M " > Jun 28 15:12:14 ns26829 Sems[30885]: Debug: (AmUtils.cpp)(write_to_socket)(614): write to unix socket: completed Jun 28 15:12:15 ns26829 /home/jack/install13x/sbin/openser[3328]: ERROR:mi_datagram:mi_datagram_parse_node: didn't find newline case1 Jun 28 15:12:15 ns26829 /home/jack/install13x/sbin/openser[3328]: ERROR:mi_datagram:mi_datagram_parse_node: parse error around 6 Jun 28 15:12:15 ns26829 /home/jack/install13x/sbin/openser[3328]: ERROR:mi_datagram:mi_datagram_parse_tree: parse error! Jun 28 15:12:15 ns26829 /home/jack/install13x/sbin/openser[3328]: ERROR:mi_datagram:mi_datagram_server: failed to parse the MI tree Jun 28 15:12:15 ns26829 Sems[30885]: Debug: (UnixSocketAdapter.cpp)(cacheMsg)(90): recv-ed: <<400 parse error in command>> Jun 28 15:12:15 ns26829 Sems[30885]: Error: (UnixSocketAdapter.cpp)(send_msg)(531): SER answered: 400 parse error in command Jun 28 15:12:15 ns26829 Sems[30885]: Error: (AmSession.cpp)(onInvite)(695): 500 could not send response
Question is: what's the best option for me to workaround this!
Aymeric MOIZARD / ANTISIP amsip - http://www.antisip.com osip2 - http://www.osip.org eXosip2 - http://savannah.nongnu.org/projects/exosip/
Kamailio (OpenSER) - Users mailing list Users@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
Hello,
On 06/28/2009 05:35 PM, Aymeric Moizard wrote:
On Sun, 28 Jun 2009, Aymeric Moizard wrote:
Hi,
I have an old openser13x which is used only to control my sems voicemail and voice service.
I just checked with kamailio15x and the same error happens in mi_datagram.
can you capture the packet sent over the datagram and paste it here? Since I do not have a sems instance now, I am not able to test it without a sample.
Thanks, Daniel
tks Aymeric
Some may know that speex payload format was published as an rfc last week and the last change before publication was the addition of the "quote" for the mode parameter.
a=fmtp:98 mode="6,any"
It's pretty clear that the '"' character is messing up the mi_datagram exchange.
Jun 28 15:12:14 ns26829 Sems[30885]: Debug: (AmUtils.cpp)(write_to_socket)(588): sending: <:t_reply: 200 OK 56471:1271880648 784D98C0-4A476C2E000F397\ 7-B6C56BB0 "Contact: sip:welcome@91.121.81.212:5070^M Content-Type: application/sdp^M " "v=0^M o=- 0 0 IN IP4 91.121.81.212^M s=session^M c=IN IP4 \ 91.121.81.212^M t=0 0^M m=audio 11066 RTP/AVP 98 0 8 101^M a=rtpmap:98 speex/8000^M a=fmtp:98 mode="6,any";cng=on^M a=rtpmap:0 PCMU/8000^M a=rtpmap:8\ PCMA/8000^M a=rtpmap:101 telephone-event/8000^M a=fmtp:101 0-15^M " > Jun 28 15:12:14 ns26829 Sems[30885]: Debug: (AmUtils.cpp)(write_to_socket)(614): write to unix socket: completed Jun 28 15:12:15 ns26829 /home/jack/install13x/sbin/openser[3328]: ERROR:mi_datagram:mi_datagram_parse_node: didn't find newline case1 Jun 28 15:12:15 ns26829 /home/jack/install13x/sbin/openser[3328]: ERROR:mi_datagram:mi_datagram_parse_node: parse error around 6 Jun 28 15:12:15 ns26829 /home/jack/install13x/sbin/openser[3328]: ERROR:mi_datagram:mi_datagram_parse_tree: parse error! Jun 28 15:12:15 ns26829 /home/jack/install13x/sbin/openser[3328]: ERROR:mi_datagram:mi_datagram_server: failed to parse the MI tree Jun 28 15:12:15 ns26829 Sems[30885]: Debug: (UnixSocketAdapter.cpp)(cacheMsg)(90): recv-ed: <<400 parse error in command>> Jun 28 15:12:15 ns26829 Sems[30885]: Error: (UnixSocketAdapter.cpp)(send_msg)(531): SER answered: 400 parse error in command Jun 28 15:12:15 ns26829 Sems[30885]: Error: (AmSession.cpp)(onInvite)(695): 500 could not send response
Question is: what's the best option for me to workaround this!
Aymeric MOIZARD / ANTISIP amsip - http://www.antisip.com osip2 - http://www.osip.org eXosip2 - http://savannah.nongnu.org/projects/exosip/
Kamailio (OpenSER) - Users mailing list Users@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
Kamailio (OpenSER) - Users mailing list Users@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
On Mon, 29 Jun 2009, Daniel-Constantin Mierla wrote:
Hello,
On 06/28/2009 05:35 PM, Aymeric Moizard wrote:
On Sun, 28 Jun 2009, Aymeric Moizard wrote:
Hi,
I have an old openser13x which is used only to control my sems voicemail and voice service.
I just checked with kamailio15x and the same error happens in mi_datagram.
can you capture the packet sent over the datagram and paste it here? Since I do not have a sems instance now, I am not able to test it without a sample.
Here is the capture:
http://sip.antisip.com/call-sdp-with-quote.pcap
The line where the problem shows is this one:
a=fmtp:98 mode="6,any";cng=on
The above comes directly from the newest rfc ;)
http://www.ietf.org/rfc/rfc5574.txt
Those " can appear in any a att-value where: (rfc4566)
att-value = byte-string byte-string = 1*(%x01-09/%x0B-0C/%x0E-FF) ;any byte except NUL, CR, or LF
I'm now using sipctrl plugin with sems to avoid the issue! So I'm not in a hurry for the fix...
Tks Aymeric
Thanks, Daniel
tks Aymeric
Some may know that speex payload format was published as an rfc last week and the last change before publication was the addition of the "quote" for the mode parameter.
a=fmtp:98 mode="6,any"
It's pretty clear that the '"' character is messing up the mi_datagram exchange.
Jun 28 15:12:14 ns26829 Sems[30885]: Debug: (AmUtils.cpp)(write_to_socket)(588): sending: <:t_reply: 200 OK 56471:1271880648 784D98C0-4A476C2E000F397\ 7-B6C56BB0 "Contact: sip:welcome@91.121.81.212:5070^M Content-Type: application/sdp^M " "v=0^M o=- 0 0 IN IP4 91.121.81.212^M s=session^M c=IN IP4 \ 91.121.81.212^M t=0 0^M m=audio 11066 RTP/AVP 98 0 8 101^M a=rtpmap:98 speex/8000^M a=fmtp:98 mode="6,any";cng=on^M a=rtpmap:0 PCMU/8000^M a=rtpmap:8\ PCMA/8000^M a=rtpmap:101 telephone-event/8000^M a=fmtp:101 0-15^M " > Jun 28 15:12:14 ns26829 Sems[30885]: Debug: (AmUtils.cpp)(write_to_socket)(614): write to unix socket: completed Jun 28 15:12:15 ns26829 /home/jack/install13x/sbin/openser[3328]: ERROR:mi_datagram:mi_datagram_parse_node: didn't find newline case1 Jun 28 15:12:15 ns26829 /home/jack/install13x/sbin/openser[3328]: ERROR:mi_datagram:mi_datagram_parse_node: parse error around 6 Jun 28 15:12:15 ns26829 /home/jack/install13x/sbin/openser[3328]: ERROR:mi_datagram:mi_datagram_parse_tree: parse error! Jun 28 15:12:15 ns26829 /home/jack/install13x/sbin/openser[3328]: ERROR:mi_datagram:mi_datagram_server: failed to parse the MI tree Jun 28 15:12:15 ns26829 Sems[30885]: Debug: (UnixSocketAdapter.cpp)(cacheMsg)(90): recv-ed: <<400 parse error in command>> Jun 28 15:12:15 ns26829 Sems[30885]: Error: (UnixSocketAdapter.cpp)(send_msg)(531): SER answered: 400 parse error in command Jun 28 15:12:15 ns26829 Sems[30885]: Error: (AmSession.cpp)(onInvite)(695): 500 could not send response
Question is: what's the best option for me to workaround this!
Aymeric MOIZARD / ANTISIP amsip - http://www.antisip.com osip2 - http://www.osip.org eXosip2 - http://savannah.nongnu.org/projects/exosip/
Kamailio (OpenSER) - Users mailing list Users@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
Kamailio (OpenSER) - Users mailing list Users@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
-- Daniel-Constantin Mierla http://www.asipto.com/
Hello,
can you get the packet sent via mi_datagram? if you use udp inet socket in mi_datagram you should be able to get it with network sniffer/ngrep. Hope sems support net datagram socket as well.
Thanks, Daniel
On 06/30/2009 01:35 AM, Aymeric Moizard wrote:
On Mon, 29 Jun 2009, Daniel-Constantin Mierla wrote:
Hello,
On 06/28/2009 05:35 PM, Aymeric Moizard wrote:
On Sun, 28 Jun 2009, Aymeric Moizard wrote:
Hi,
I have an old openser13x which is used only to control my sems voicemail and voice service.
I just checked with kamailio15x and the same error happens in mi_datagram.
can you capture the packet sent over the datagram and paste it here? Since I do not have a sems instance now, I am not able to test it without a sample.
Here is the capture:
http://sip.antisip.com/call-sdp-with-quote.pcap
The line where the problem shows is this one:
a=fmtp:98 mode="6,any";cng=on
The above comes directly from the newest rfc ;)
http://www.ietf.org/rfc/rfc5574.txt
Those " can appear in any a att-value where: (rfc4566)
att-value = byte-string byte-string = 1*(%x01-09/%x0B-0C/%x0E-FF) ;any byte except NUL, CR, or LF
I'm now using sipctrl plugin with sems to avoid the issue! So I'm not in a hurry for the fix...
Tks Aymeric
Thanks, Daniel
tks Aymeric
Some may know that speex payload format was published as an rfc last week and the last change before publication was the addition of the "quote" for the mode parameter.
a=fmtp:98 mode="6,any"
It's pretty clear that the '"' character is messing up the mi_datagram exchange.
Jun 28 15:12:14 ns26829 Sems[30885]: Debug: (AmUtils.cpp)(write_to_socket)(588): sending: <:t_reply: 200 OK 56471:1271880648 784D98C0-4A476C2E000F397\ 7-B6C56BB0 "Contact: sip:welcome@91.121.81.212:5070^M Content-Type: application/sdp^M " "v=0^M o=- 0 0 IN IP4 91.121.81.212^M s=session^M c=IN IP4 \ 91.121.81.212^M t=0 0^M m=audio 11066 RTP/AVP 98 0 8 101^M a=rtpmap:98 speex/8000^M a=fmtp:98 mode="6,any";cng=on^M a=rtpmap:0 PCMU/8000^M a=rtpmap:8\ PCMA/8000^M a=rtpmap:101 telephone-event/8000^M a=fmtp:101 0-15^M " > Jun 28 15:12:14 ns26829 Sems[30885]: Debug: (AmUtils.cpp)(write_to_socket)(614): write to unix socket: completed Jun 28 15:12:15 ns26829 /home/jack/install13x/sbin/openser[3328]: ERROR:mi_datagram:mi_datagram_parse_node: didn't find newline case1 Jun 28 15:12:15 ns26829 /home/jack/install13x/sbin/openser[3328]: ERROR:mi_datagram:mi_datagram_parse_node: parse error around 6 Jun 28 15:12:15 ns26829 /home/jack/install13x/sbin/openser[3328]: ERROR:mi_datagram:mi_datagram_parse_tree: parse error! Jun 28 15:12:15 ns26829 /home/jack/install13x/sbin/openser[3328]: ERROR:mi_datagram:mi_datagram_server: failed to parse the MI tree Jun 28 15:12:15 ns26829 Sems[30885]: Debug: (UnixSocketAdapter.cpp)(cacheMsg)(90): recv-ed: <<400 parse error in command>> Jun 28 15:12:15 ns26829 Sems[30885]: Error: (UnixSocketAdapter.cpp)(send_msg)(531): SER answered: 400 parse error in command Jun 28 15:12:15 ns26829 Sems[30885]: Error: (AmSession.cpp)(onInvite)(695): 500 could not send response
Question is: what's the best option for me to workaround this!
Aymeric MOIZARD / ANTISIP amsip - http://www.antisip.com osip2 - http://www.osip.org eXosip2 - http://savannah.nongnu.org/projects/exosip/
Kamailio (OpenSER) - Users mailing list Users@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
Kamailio (OpenSER) - Users mailing list Users@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
-- Daniel-Constantin Mierla http://www.asipto.com/
Kamailio (OpenSER) - Users mailing list Users@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users