[prev in list] [next in list] [prev in thread] [next in thread]
List: sems
Subject: [Sems] IVR: recording don't stop
From: rco () iptel ! org (Raphael Coeffic)
Date: 2004-01-15 16:27:48
Message-ID: 003001c3db7c$310ae0d0$0100a8c0 () rafland
[Download RAW message or body]
Hello Samy,
the IVR plug-in is still experimental but we enjoy it having users testing it.
I forwarded your mail to the developer of IVR. He may have more detailed informations \
about that problem.
-Raphael.
----- Original Message -----
From: Samy Touati
To: 'Raphael Coeffic'
Sent: Thursday, January 15, 2004 5:55 AM
Subject: RE: [Sems] Error from sems: parse_sdp_line : parameter 'm=' was notfound
Hi,
I reverted to an old firmwawre version for my snom and the sdp parameters are now \
ok.
I enabled the ivr on sems and configure it and here is what I'm experiencing:
* I can call a number and the ivr plugin will activate, it will prompt me to leave \
a message. I do leave a message but the recroding never stop.
* When I call my own number to retrieve messages, I get prompted to press one 2 and \
3, I do press 1, and python complain about the wrong payload 101, but from the logs \
it looks like it's reading my messages then playing the no more messages, but I don't \
hear these messages, I get disconnected.
Is the ivr plugin supposed to work? Or is this the correct state for the code?
Thanks.
Samy.
------------------------------------------------------------------------------
From: Raphael Coeffic [mailto:rco@iptel.org]
Sent: Wednesday, January 14, 2004 7:30 AM
To: Samy Touati; sems@iptel.org
Subject: Re: [Sems] Error from sems: parse_sdp_line : parameter 'm=' was notfound
Hi Samy!
what is the client that you use ? The SDP messsage generated is not conform to the \
RFC 2327...
the problem is, that the 't=0 0' line should be after the 'c=..' line. Look at \
Appendix A (SDP grammar).
The SDP parser implemented within Sems is really strict, it doesn't allow \
non-conform SDP messages.
-Raphael.
----- Original Message -----
From: Samy Touati
To: sems@iptel.org
Sent: Monday, January 12, 2004 6:19 AM
Subject: [Sems] Error from sems: parse_sdp_line : parameter 'm=' was notfound
Hi,
I'm running ser 0-8-12 along with the latest sems out of cvs.
I'm trying to use vm, and I'm getting an error from sems related to parsing the \
SDP part of a message.
Sems is complaining about the media description missing: parameter m= not found.
But I traced the call and the line is there, it's also shown in the debug extract \
included here.
What could be the problem ?
Thanks.
Samy.
Debug output from sems:
(5947) DEBUG: execute (AmServer.cpp:252): cmd.route= \
<<sip:4504195801@142.133.80.100;ftag=4hb9kqjbi0;lr=on>>
(5947) DEBUG: execute (AmServer.cpp:253): cmd.next_hop= \
<sip:4504195801@142.133.80.100;ftag=4hb9kqjbi0;lr=on>
(5947) DEBUG: execute (AmServer.cpp:259): hdrs: `P-MsgFlags: 0
Session-Expires: 7200
'
(5947) DEBUG: execute (AmServer.cpp:266): body: `v=0
o=root 224048977 224048977 IN IP4 142.133.80.30
s=call
t=0 0
c=IN IP4 142.133.80.30
m=audio 10024 RTP/AVP 18 3 0 8 101
a=rtpmap:18 g729/8000
a=rtpmap:3 gsm/8000
a=rtpmap:0 pcmu/8000
a=rtpmap:8 pcma/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv
'
(5947) DEBUG: execute (AmServer.cpp:277): everything is OK !
(5947) DEBUG: onInvite (AnswerMachine.cpp:121): email address for user \
'4504195801': samy@tunix.com
(5947) DEBUG: startSession (AmSession.cpp:431): Starting session... \
(hash=3c2688e4a835-mctiz0n0rf3d@142-133-80-304hb9kqjbi0,sess_key=0000173B2D08CEBD)
(5947) ERROR: parse_sdp_line_ex (AmSdp.cpp:374): parse_sdp_line : parameter 'm=' \
was not found
(5947) ERROR: run (AmSession.cpp:155): 400 session description parsing failed
(5947) DEBUG: sendToFIFO (AmRequest.cpp:194): msg=<:vm_reply:0000173B5228DBE2
400
session description parsing failed
6396:1742900507
0000173B2D08CEBD
Contact: <sip:4504195801@142.133.80.100:5071>
.
.
>
(5947) DEBUG: openReplyFifo (AmRequest.cpp:358): flags=800
(5947) DEBUG: openReplyFifo (AmRequest.cpp:360): flags=0
(5947) DEBUG: write_to_fifo (AmRequest.cpp:705): Write to fifo: completed
(5947) DEBUG: getReturnCode (AmRequest.cpp:413): response from Ser: 200 \
fifo_t_reply succeeded
(5947) DEBUG: getReturnCode (AmRequest.cpp:434): n_cmd.from_uri= <>
(5947) DEBUG: getReturnCode (AmRequest.cpp:437): n_cmd.next_hop= <>
(5947) DEBUG: getReturnCode (AmRequest.cpp:440): n_cmd.route= <>
(5947) DEBUG: sendToFIFO (AmRequest.cpp:213): sendToFifo returns \
ret=getReturnCode=0
(5947) DEBUG: sadSession (AmSession.cpp:305): searching for session to destroy \
(hash=3c2688e4a835-mctiz0n0rf3d@142-133-80-304hb9kqjbi0,sess_key=0000173B2D08CEBD)
(5947) DEBUG: findSession (AmSession.cpp:369): session found with key
(5947) DEBUG: destroySession (AmSession.cpp:327): sess_it != a_sessions.end()
(5947) DEBUG: destroySession (AmSession.cpp:330): it != sess_it->second.end()
(5947) DEBUG: destroySession (AmSession.cpp:337): session found: stopping session
(5947) DEBUG: stopAndQueue (AmSession.cpp:285): session cleaner trying to stop \
80c7258
(5947) DEBUG: postEvent (AmEventQueue.cpp:47): AmEventQueue: trying to post event
(5947) DEBUG: postEvent (AmEventQueue.cpp:55): AmEventQueue: event posted
(5947) DEBUG: destroySession (AmSession.cpp:339): session stopped and destroyed \
(#sessions=0)
(5947) DEBUG: run (AmSession.cpp:238): Session cleaner starting its work
(5947) DEBUG: run (AmSession.cpp:252): session 80c7258 has been destroyed'
(5947) DEBUG: run (AmSession.cpp:275): Session cleaner finished
(5946) WARNING: sig_usr (sems.cpp:72): signal 2 received
(5946) WARNING: sig_usr (sems.cpp:72): signal 17 received
(5946) INFO: sig_usr (sems.cpp:80): finished
----------------------------------------------------------------------------
_______________________________________________
Sems mailing list
Sems@iptel.org
http://mail.iptel.org/cgi-bin/mailman/listinfo/sems
-------------- next part --------------
An HTML attachment was scrubbed...
URL: /pipermail/sems/attachments/20040115/1191202d/attachment.html
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic