19 Apr
2007
19 Apr
'07
9:24 a.m.
Hi Sumin,
Thanx for replying my mail.
I failed to compile ivr module.
btw I'm using sems.0.10.0-rc2 as media server. Below is the error log:
python2.2 py_comp -l py &&\
cp py/*.pyc ../../core/lib
Listing py ...
make[1]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/ivr'
g++ -MM IvrAudio.cpp -I ../../core -Wall -Wno-reorder -fPIC -g -O2 -D_DEBUG
-D_THREAD_SAFE -D_REENTRANT -DVERSION='"0.10.0-rc2"'
-DARCH='"i386"' -DOS='"linux"'
-I/usr/include/python2.2 -fno-strict-aliasing > IvrAudio.d
g++ -MM Ivr.cpp -I ../../core -Wall -Wno-reorder -fPIC -g -O2 -D_DEBUG -D_THREAD_SAFE
-D_REENTRANT -DVERSION='"0.10.0-rc2"' -DARCH='"i386"'
-DOS='"linux"' -I/usr/include/python2.2 -fno-strict-aliasing >
Ivr.d
g++ -MM IvrDialogBase.cpp -I ../../core -Wall -Wno-reorder -fPIC -g -O2 -D_DEBUG
-D_THREAD_SAFE -D_REENTRANT -DVERSION='"0.10.0-rc2"'
-DARCH='"i386"' -DOS='"linux"'
-I/usr/include/python2.2 -fno-strict-aliasing > IvrDialogBase.d
g++ -MM IvrSipDialog.cpp -I ../../core -Wall -Wno-reorder -fPIC -g -O2 -D_DEBUG
-D_THREAD_SAFE -D_REENTRANT -DVERSION='"0.10.0-rc2"'
-DARCH='"i386"' -DOS='"linux"'
-I/usr/include/python2.2 -fno-strict-aliasing > IvrSipDialog.d
g++ -MM IvrSipReply.cpp -I ../../core -Wall -Wno-reorder -fPIC -g -O2 -D_DEBUG
-D_THREAD_SAFE -D_REENTRANT -DVERSION='"0.10.0-rc2"'
-DARCH='"i386"' -DOS='"linux"'
-I/usr/include/python2.2 -fno-strict-aliasing > IvrSipReply.d
g++ -MM IvrSipRequest.cpp -I ../../core -Wall -Wno-reorder -fPIC -g -O2 -D_DEBUG
-D_THREAD_SAFE -D_REENTRANT -DVERSION='"0.10.0-rc2"'
-DARCH='"i386"' -DOS='"linux"'
-I/usr/include/python2.2 -fno-strict-aliasing > IvrSipRequest.d
g++ -MM IvrUAC.cpp -I ../../core -Wall -Wno-reorder -fPIC -g -O2 -D_DEBUG -D_THREAD_SAFE
-D_REENTRANT -DVERSION='"0.10.0-rc2"' -DARCH='"i386"'
-DOS='"linux"' -I/usr/include/python2.2 -fno-strict-aliasing >
IvrUAC.d
make[1]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/ivr'
make[1]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/ivr'
g++ -I ../../core -Wall -Wno-reorder -fPIC -g -O2 -D_DEBUG -D_THREAD_SAFE -D_REENTRANT
-DVERSION='"0.10.0-rc2"' -DARCH='"i386"'
-DOS='"linux"' -I/usr/include/python2.2 -fno-strict-aliasing -c
IvrAudio.cpp -o IvrAudio.o
g++ -I ../../core -Wall -Wno-reorder -fPIC -g -O2 -D_DEBUG -D_THREAD_SAFE -D_REENTRANT
-DVERSION='"0.10.0-rc2"' -DARCH='"i386"'
-DOS='"linux"' -I/usr/include/python2.2 -fno-strict-aliasing -c
Ivr.cpp -o Ivr.o
Ivr.cpp:54: 'PyGILState_STATE' is used as a type, but is not defined as a type.
Ivr.cpp: In constructor `PythonGIL::PythonGIL()':
Ivr.cpp:56: `gst' undeclared (first use this function)
Ivr.cpp:56: (Each undeclared identifier is reported only once for each function
it appears in.)
Ivr.cpp:56: `PyGILState_Ensure' undeclared (first use this function)
Ivr.cpp: In destructor `PythonGIL::~PythonGIL()':
Ivr.cpp:57: `PyGILState_Release' undeclared (first use this function)
Ivr.cpp: In member function `bool IvrFactory::loadScript(const std::string&)':
Ivr.cpp:363: invalid conversion from `const char*' to `char*'
Ivr.cpp: In member function `bool IvrDialog::callPyEventHandler(char*, char*,
...)':
Ivr.cpp:640: `PyBool_Check' undeclared (first use this function)
make[1]: *** [Ivr.o] Error 1
make[1]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/ivr'
make: [all] Error 2 (ignored)
echo "Installing Python object files..."
Installing Python object files...
for f in log.pyc ; do \
if [ -n "py/$f" ]; then \
touch /usr/local/lib/sems/plug-in//$f; \
install -m 755 py/$f /usr/local/lib/sems/plug-in//$f; \
fi ; \
done
mkdir -p /usr/local/lib/sems/plug-in/
touch /usr/local/lib/sems/plug-in//ivr.so ; \
install -m 755 ivr.so /usr/local/lib/sems/plug-in/
install: cannot stat `ivr.so': No such file or directory
make: *** [install] Error 1
I used "make install" to compile the module.
I'd like to ask another question too...Where does SEMS voicemail usually store voice
message? And what is the type of the message store (wav or text file)?
Thanx before
Regards,
Meidiana
seo <giganti71(a)gmail.com> wrote:
Hi Meidiana,
Do you mean that you failed to compile ivr module OR you failed to load ivr plug-in for
mailbox application?
If you failed to compile ivr module, could you send compile error log?
If you didn't see any compile error , I think you have to check if there is ivr.so
file on your system and then check if ivr.so file is in the plug-in path which is defined
in sems.conf file.
If you still have an issue even though all plug-in files are in the plug-in path, could
you attach sems logs?
Thanks.
Sumin
On 4/17/07, Meidiana Ten <gotcha_em(a)yahoo.com> wrote: Hi there,
Thanx before for my past questions.
Now, I want to add mailbox application on my server but I cannot find IVR plugin
Then, I read some tutorial that I must make the plugin itself
I've followed the step but it failed.
What should I do then?
Please advise
Thanx
Regards,
Meidiana
---------------------------------
Ahhh...imagining that irresistible "new car" smell?
Check out new cars at Yahoo! Autos.
_______________________________________________
Sems mailing list
Sems(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/sems
---------------------------------
Ahhh...imagining that irresistible "new car" smell?
Check outnew cars at Yahoo! Autos.
19 Apr
19 Apr
9:44 a.m.
New subject: [Serusers] Help: I can't hear audio although I receive the RTP packets
Hello all,
My problem is one of the most strange problems I have ever found.
I am using a SER (v0.8.14) configured to support Nated endpoints.
I make a call from a NATed SIP endpoint towards another endpoint which is
not NATed (static NAT IP to IP translation).
Everything seems to work well, as all the mechanism to solve NAT are
triggered and all the packets (SDP part) are correctly translated by the
SER.
I captured all the SIP packets and the call is correctly established. I can
see how the NATed endpoint send and receive RTP packets with no problem
(aparently). Even all RTP ports are correct according to the previous
negotiation (SDP) between both endpoints. Moreover, the negotiated codecs
are fully supported.
What is happening is REALLY rare... I CAN'T HEAR ANYTHING AT ALL.
All audio is well configured and enable. What's more, as soon as I take out
the NAT, I make the same call to the same destination and voila! RTP packets
are received and HEARD!!! The voice codecs used for communications are
exactly the same as the ones used with NAT.
I have checked every single packet and SIP message and everything seems
OK... I don't what I can do.
Any idea? I have packet captures. Anyone who wants to have a look, please
tell me.
Thank you very much for your attention.
Victor
_________________________________________________________________
Moda para esta temporada. Ponte al día de todas las tendencias.
http://www.msn.es/Mujer/moda/default.asp
20 Apr
20 Apr
2:24 a.m.
New subject: [Serusers] Help: I can't hear audio although I receive the RTP packets
Think in straight lines: If you remove the NAT and it works, then the
NAT is the problem. It also means that if both RTP and SIP signalling
looks the same in both cases, you have either overlooked a difference,
or they are really the same, but the NAT is doing something and your
tests haven't revealed it.
So, have you captured signalling and RTP on both end-points? So you know
the NAT is not dropping RTP?
If you see streams both ways on BOTH end-points, then I would say the
NAT either garbles SIP messages (and you have overlooked something) or
it garbles RTP (which in case you should probably see something in the
user agents' error logs?)
g-)
Victor Huertas Garcia wrote:
Hello all,
My problem is one of the most strange problems I have ever found.
I am using a SER (v0.8.14) configured to support Nated endpoints.
I make a call from a NATed SIP endpoint towards another endpoint which
is not NATed (static NAT IP to IP translation).
Everything seems to work well, as all the mechanism to solve NAT are
triggered and all the packets (SDP part) are correctly translated by
the SER.
I captured all the SIP packets and the call is correctly established.
I can see how the NATed endpoint send and receive RTP packets with no
problem (aparently). Even all RTP ports are correct according to the
previous negotiation (SDP) between both endpoints. Moreover, the
negotiated codecs are fully supported.
What is happening is REALLY rare... I CAN'T HEAR ANYTHING AT ALL.
All audio is well configured and enable. What's more, as soon as I
take out the NAT, I make the same call to the same destination and
voila! RTP packets are received and HEARD!!! The voice codecs used for
communications are exactly the same as the ones used with NAT.
I have checked every single packet and SIP message and everything
seems OK... I don't what I can do.
Any idea? I have packet captures. Anyone who wants to have a look,
please tell me.
Thank you very much for your attention.
Victor
_________________________________________________________________
Moda para esta temporada. Ponte al día de todas las tendencias.
http://www.msn.es/Mujer/moda/default.asp
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
3:35 a.m.
New subject: [Serusers] Help: I can't hear audio although I receive the RTP packets
Firt of all, thank you very much for your answer.
I tell you the rarest. With NAT enabled, I call a normal endpoint (SIP
softphone) in located in a PC and it works fine. Audio is heared in both
endpoints. But when I call to PSTN through a VoIP GW it happens what I told
in the last e-mail. I can see how the RTP packets trespasses the NAT and
reach the enpoint behind the NAT (exactly the same as with the normal
endpoint) but no audio is heard. What's more, no ICMPs are generated by the
PC so I interprehet that the destination RTP port is correct. I have tried
it with three different endpoints (Cisco SIP phone, and two different
softphones, one of both is Eyebeam) with the same result.
That is what is misleading me the most... Why does it work if I call to a
normal endpoint? If it is NAT fault, it should happen the same as when I
call to PSTN.
Obviously that NAT is somehow responsible for this problem but I can't
figure out what's going on. I have compared with Ethereal every sigle packet
for calls to normal endpoint and VoIP GW and all the translations in SDP are
preformed identically.
I just wonder if there has been cases in which the RTP reaches and endpoint
(with no ICMPs at all, remember) and no sound is heared.
Thanks in advance.
Victor
From: "Greger V. Teigre"
<greger(a)teigre.com>
To: Victor Huertas Garcia <vhuertas(a)hotmail.com>
CC: serusers(a)iptel.org
Subject: Re: [Serusers] Help: I can't hear audio although I receive the RTP
packets
Date: Fri, 20 Apr 2007 08:24:54 +0200
Think in straight lines: If you remove the NAT and it works, then the NAT
is the problem. It also means that if both RTP and SIP signalling looks the
same in both cases, you have either overlooked a difference, or they are
really the same, but the NAT is doing something and your tests haven't
revealed it.
So, have you captured signalling and RTP on both end-points? So you know
the NAT is not dropping RTP?
If you see streams both ways on BOTH end-points, then I would say the NAT
either garbles SIP messages (and you have overlooked something) or it
garbles RTP (which in case you should probably see something in the user
agents' error logs?)
g-)
Victor Huertas Garcia wrote:
>
>
>
>Hello all,
>
>My problem is one of the most strange problems I have ever found.
>I am using a SER (v0.8.14) configured to support Nated endpoints.
>I make a call from a NATed SIP endpoint towards another endpoint which is
>not NATed (static NAT IP to IP translation).
>Everything seems to work well, as all the mechanism to solve NAT are
>triggered and all the packets (SDP part) are correctly translated by the
>SER.
>I captured all the SIP packets and the call is correctly established. I
>can see how the NATed endpoint send and receive RTP packets with no
>problem (aparently). Even all RTP ports are correct according to the
>previous negotiation (SDP) between both endpoints. Moreover, the
>negotiated codecs are fully supported.
>
>What is happening is REALLY rare... I CAN'T HEAR ANYTHING AT ALL.
>
>All audio is well configured and enable. What's more, as soon as I take
>out the NAT, I make the same call to the same destination and voila! RTP
>packets are received and HEARD!!! The voice codecs used for communications
>are exactly the same as the ones used with NAT.
>
>I have checked every single packet and SIP message and everything seems
>OK... I don't what I can do.
>
>Any idea? I have packet captures. Anyone who wants to have a look, please
>tell me.
>
>Thank you very much for your attention.
>
>Victor
>
>_________________________________________________________________
>Moda para esta temporada. Ponte al día de todas las tendencias.
>http://www.msn.es/Mujer/moda/default.asp
>
>_______________________________________________
>Serusers mailing list
>Serusers(a)lists.iptel.org
>http://lists.iptel.org/mailman/listinfo/serusers
>
>
_________________________________________________________________
Horóscopo, tarot, numerología... Escucha lo que te dicen los astros.
http://astrocentro.msn.es/
19 Apr
19 Apr
10:20 a.m.
Hello,
Python 2.2 won't work, you need at least Python 2.3, but I would
recommend 2.4 or 2.5.
If you have various versions installed, you can choose the version to
build with
PYTHON_VERSION=2.4 make all
voicemail application does send the voicemail as attachment to a
(configurable) email via SMTP server. mailbox application stores the
voicemail in an IMAP server and the users can dial in to check the
messages. have a look at the modules documentation:
http://ftp.iptel.org/pub/sems/doc/current/AppDoc.html
hth
Stefan
Meidiana Ten wrote:
Hi Sumin,
Thanx for replying my mail.
I failed to compile ivr module.
btw I'm using sems.0.10.0-rc2 as media server. Below is the error log:
python2.2 py_comp -l py &&\
cp py/*.pyc ../../core/lib
Listing py ...
make[1]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/ivr'
g++ -MM IvrAudio.cpp -I ../../core -Wall -Wno-reorder -fPIC -g -O2
-D_DEBUG -D_THREAD_SAFE -D_REENTRANT -DVERSION='"0.10.0-rc2"'
-DARCH='"i386"' -DOS='"linux"'
-I/usr/include/python2.2
-fno-strict-aliasing > IvrAudio.d
g++ -MM Ivr.cpp -I ../../core -Wall -Wno-reorder -fPIC -g -O2 -D_DEBUG
-D_THREAD_SAFE -D_REENTRANT -DVERSION='"0.10.0-rc2"'
-DARCH='"i386"'
-DOS='"linux"' -I/usr/include/python2.2 -fno-strict-aliasing >
Ivr.d
g++ -MM IvrDialogBase.cpp -I ../../core -Wall -Wno-reorder -fPIC -g -O2
-D_DEBUG -D_THREAD_SAFE -D_REENTRANT -DVERSION='"0.10.0-rc2"'
-DARCH='"i386"' -DOS='"linux"'
-I/usr/include/python2.2
-fno-strict-aliasing > IvrDialogBase.d
g++ -MM IvrSipDialog.cpp -I ../../core -Wall -Wno-reorder -fPIC -g -O2
-D_DEBUG -D_THREAD_SAFE -D_REENTRANT -DVERSION='"0.10.0-rc2"'
-DARCH='"i386"' -DOS='"linux"'
-I/usr/include/python2.2
-fno-strict-aliasing > IvrSipDialog.d
g++ -MM IvrSipReply.cpp -I ../../core -Wall -Wno-reorder -fPIC -g -O2
-D_DEBUG -D_THREAD_SAFE -D_REENTRANT -DVERSION='"0.10.0-rc2"'
-DARCH='"i386"' -DOS='"linux"'
-I/usr/include/python2.2
-fno-strict-aliasing > IvrSipReply.d
g++ -MM IvrSipRequest.cpp -I ../../core -Wall -Wno-reorder -fPIC -g -O2
-D_DEBUG -D_THREAD_SAFE -D_REENTRANT -DVERSION='"0.10.0-rc2"'
-DARCH='"i386"' -DOS='"linux"'
-I/usr/include/python2.2
-fno-strict-aliasing > IvrSipRequest.d
g++ -MM IvrUAC.cpp -I ../../core -Wall -Wno-reorder -fPIC -g -O2
-D_DEBUG -D_THREAD_SAFE -D_REENTRANT -DVERSION='"0.10.0-rc2"'
-DARCH='"i386"' -DOS='"linux"'
-I/usr/include/python2.2
-fno-strict-aliasing > IvrUAC.d
make[1]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/ivr'
make[1]: Entering directory `/usr/local/src/sems-0.10.0-rc2/apps/ivr'
g++ -I ../../core -Wall -Wno-reorder -fPIC -g -O2 -D_DEBUG
-D_THREAD_SAFE -D_REENTRANT -DVERSION='"0.10.0-rc2"'
-DARCH='"i386"'
-DOS='"linux"' -I/usr/include/python2.2 -fno-strict-aliasing -c
IvrAudio.cpp -o IvrAudio.o
g++ -I ../../core -Wall -Wno-reorder -fPIC -g -O2 -D_DEBUG
-D_THREAD_SAFE -D_REENTRANT -DVERSION='"0.10.0-rc2"'
-DARCH='"i386"'
-DOS='"linux"' -I/usr/include/python2.2 -fno-strict-aliasing -c
Ivr.cpp -o Ivr.o
Ivr.cpp:54: 'PyGILState_STATE' is used as a type, but is not defined as
a type.
Ivr.cpp: In constructor `PythonGIL::PythonGIL()':
Ivr.cpp:56: `gst' undeclared (first use this function)
Ivr.cpp:56: (Each undeclared identifier is reported only once for each
function
it appears in.)
Ivr.cpp:56: `PyGILState_Ensure' undeclared (first use this function)
Ivr.cpp: In destructor `PythonGIL::~PythonGIL()':
Ivr.cpp:57: `PyGILState_Release' undeclared (first use this function)
Ivr.cpp: In member function `bool IvrFactory::loadScript(const
std::string&)':
Ivr.cpp:363: invalid conversion from `const char*' to `char*'
Ivr.cpp: In member function `bool IvrDialog::callPyEventHandler(char*,
char*,
...)':
Ivr.cpp:640: `PyBool_Check' undeclared (first use this function)
make[1]: *** [Ivr.o] Error 1
make[1]: Leaving directory `/usr/local/src/sems-0.10.0-rc2/apps/ivr'
make: [all] Error 2 (ignored)
echo "Installing Python object files..."
Installing Python object files...
for f in log.pyc ; do \
if [ -n "py/$f" ]; then \
touch /usr/local/lib/sems/plug-in//$f; \
install -m 755 py/$f /usr/local/lib/sems/plug-in//$f; \
fi ; \
done
mkdir -p /usr/local/lib/sems/plug-in/
touch /usr/local/lib/sems/plug-in//ivr.so ; \
install -m 755 ivr.so /usr/local/lib/sems/plug-in/
install: cannot stat `ivr.so': No such file or directory
make: *** [install] Error 1
I used "make install" to compile the module.
I'd like to ask another question too...Where does SEMS voicemail usually
store voice message? And what is the type of the message store (wav or
text file)?
Thanx before
Regards,
Meidiana
*/seo <giganti71(a)gmail.com>/* wrote:
Hi Meidiana,
Do you mean that you failed to compile ivr module OR you failed to
load ivr plug-in for mailbox application?
If you failed to compile ivr module, could you send compile error log?
If you didn't see any compile error , I think you have to check if
there is ivr.so file on your system and then check if ivr.so file is
in the plug-in path which is defined in sems.conf file.
If you still have an issue even though all plug-in files are in the
plug-in path, could you attach sems logs?
Thanks.
Sumin
On 4/17/07, *Meidiana Ten* <gotcha_em(a)yahoo.com
<mailto:gotcha_em@yahoo.com>> wrote:
Hi there,
Thanx before for my past questions.
Now, I want to add mailbox application on my server but I cannot
find IVR plugin
Then, I read some tutorial that I must make the plugin itself
I've followed the step but it failed.
What should I do then?
Please advise
Thanx
Regards,
Meidiana
------------------------------------------------------------------------
Ahhh...imagining that irresistible "new car" smell?
Check out new cars at Yahoo! Autos.
<http://us.rd.yahoo.com/evt=48245/*http://autos.yahoo.com/new_cars.html;_ylc=X3oDMTE1YW1jcXJ2BF9TAzk3MTA3MDc2BHNlYwNtYWlsdGFncwRzbGsDbmV3LWNhcnM->
_______________________________________________
Sems mailing list
Sems(a)lists.iptel.org <mailto:Sems@lists.iptel.org>
http://lists.iptel.org/mailman/listinfo/sems
------------------------------------------------------------------------
Ahhh...imagining that irresistible "new car" smell?
Check out new cars at Yahoo! Autos.
<http://us.rd.yahoo.com/evt=48245/*http://autos.yahoo.com/new_cars.html;_ylc=X3oDMTE1YW1jcXJ2BF9TAzk3MTA3MDc2BHNlYwNtYWlsdGFncwRzbGsDbmV3LWNhcnM->
------------------------------------------------------------------------
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
--
Stefan Sayer
Media Services Development
stefan.sayer(a)iptego.de
www.iptego.de
iptego GmbH
Am Borsigturm 40
13507 Berlin
Germany
Amtsgericht Charlottenburg, HRB 101010
Geschaeftsfuehrer: Alexander Hoffmann
10:35 a.m.
Hi,
Thanx for replying so fast. I'll try it..(I have my server in campus)
Beside, I have another question =)
If the attachement send by SMTP server to client, do client need some device to download
the attachement? What can I use then? And how to configure the device?
Btw, I don't use serweb. Please advise.
Thanx
Regards,
Meidiana
---------------------------------
Ahhh...imagining that irresistible "new car" smell?
Check outnew cars at Yahoo! Autos.
1:39 p.m.
It depends on how you encode the attachment. If it's a wav file, they need some
software that plays wav files on the computer/device they use to read email (most
internet-capable devices can play wav files). If it's an mp3 file, they need an mp3
player on their email computer/device.
N.
On Thu, 19 Apr 2007 07:35:11 -0700 (PDT), Meidiana Ten wrote
Hi,
Thanx for replying so fast. I'll try it..(I have my server in campus)
Beside, I have another question =)
If the attachement send by SMTP server to client, do client need some device to download
the attachement? What can I use then? And how to configure the device?
Btw, I don't use serweb. Please advise.
Thanx
Regards,
Meidiana
-----------------------------------------------------------------------
Ahhh...imagining that irresistible "new car" smell?
Check outnew cars at Yahoo! Autos.
6277
days inactive
6278
days old
6 comments
5 participants
participants (5)
-
Greger V. Teigre -
Meidiana Ten -
sip -
Stefan Sayer -
Victor Huertas Garcia