lib SRTP: Error 254 rtpw: no process found al ejecutar make runtest

[navaismo]

Debian no los tiene por defecto? Intentaste con apt-get install libsrtp libsrtp-dev?

[Christian Cabrera]

El archivo test/rtpw_test.sh hace referencia a un comando con una ruta equivocada. Aunque poco práctico, puedes editar el archivo y cambiarlo a la ruta absoluta. Yo acabo de probarlo y ponerlo así:

RTPW=/usr/src/srtp/test/rtpw

Simplemente pon la ruta completa y debe de funcionar. Es un problema de paths.

Saludos,

[ihrreynaga]

Ya hice de poner RTPW=/usr/src/srtp/test/rtpw y despues hago
./configure
make
make runtest (y aqui me vuelve salir esto)


root@PegasoTLC:~# cd /usr
root@PegasoTLC:/usr# cd /src
-bash: cd: /src: No existe el fichero o el directorio
root@PegasoTLC:/usr# cd src
root@PegasoTLC:/usr/src# cd srtp
root@PegasoTLC:/usr/src/srtp# ./configure
checking for ranlib... ranlib
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for a BSD-compatible install... /usr/bin/install -c
checking whether to build for Linux kernel context... no
checking for /dev/urandom... yes
checking which random device to use... /dev/urandom
checking how to run the C preprocessor... gcc -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for stdlib.h... (cached) yes
checking for unistd.h... (cached) yes
checking byteswap.h usability... yes
checking byteswap.h presence... yes
checking for byteswap.h... yes
checking for stdint.h... (cached) yes
checking sys/uio.h usability... yes
checking sys/uio.h presence... yes
checking for sys/uio.h... yes
checking for inttypes.h... (cached) yes
checking for sys/types.h... (cached) yes
checking machine/types.h usability... no
checking machine/types.h presence... no
checking for machine/types.h... no
checking sys/int_types.h usability... no
checking sys/int_types.h presence... no
checking for sys/int_types.h... no
checking sys/socket.h usability... yes
checking sys/socket.h presence... yes
checking for sys/socket.h... yes
checking netinet/in.h usability... yes
checking netinet/in.h presence... yes
checking for netinet/in.h... yes
checking arpa/inet.h usability... yes
checking arpa/inet.h presence... yes
checking for arpa/inet.h... yes
checking windows.h usability... no
checking windows.h presence... no
checking for windows.h... no
checking syslog.h usability... yes
checking syslog.h presence... yes
checking for syslog.h... yes
checking for int8_t... yes
checking for uint8_t... yes
checking for int16_t... yes
checking for uint16_t... yes
checking for int32_t... yes
checking for uint32_t... yes
checking for uint64_t... yes
checking for unsigned long... yes
checking size of unsigned long... 4
checking for unsigned long long... yes
checking size of unsigned long long... 8
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking for size_t... yes
checking for socket... yes
checking for inet_aton... yes
checking for usleep... yes
checking whether byte ordering is bigendian... no
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking whether to compile in debugging... yes
checking whether to use ISMAcryp code... no
checking whether to use syslog for error reporting... no
checking whether to use stdout for error reporting... yes
checking whether to use /dev/console for error reporting... no
checking whether to use GDOI key management... no
configure: creating ./config.status
config.status: creating Makefile
config.status: creating crypto/Makefile
config.status: creating doc/Makefile
config.status: creating crypto/include/config.h
config.status: crypto/include/config.h is unchanged
root@PegasoTLC:/usr/src/srtp# make
Build done. Please run 'make runtest' to run self tests.
root@PegasoTLC:/usr/src/srtp# make runtest
Build done. Please run 'make runtest' to run self tests.
running libsrtp test applications...
crypto/test/cipher_driver -v >/dev/null
crypto/test/kernel_driver -v >/dev/null
test/rdbx_driver -v >/dev/null
test/srtp_driver -v >/dev/null
test/roc_driver -v >/dev/null
test/replay_driver -v >/dev/null
test/dtls_srtp_driver >/dev/null
cd test; ./rtpw_test.sh >/dev/null
./rtpw_test.sh: 73: rtpw: not found
rtpw: no process found
2: no process found
make: *** [runtest] Error 254
root@PegasoTLC:/usr/src/srtp#

[Christian Cabrera]

El ejemplo que di es porque así lo instalé en mi servidor. Espero que hayas hecho los cambios acorde al tuyo.

¿Qué pasa si usas este comando ?

ls -la /usr/src/srtp/test/rtpw

Debería de darte las propiedades del archivo. Si no te las da, es porque tienes que corregir tu ruta a lo que tu tienes.

Saludos,

[ihrreynaga]

Gracias Christian si era eso ya quedo solucionado

Saludos!!

[MaruBasaju]

hola Cristian , Navaismo, todo habia salido bien hasta que me salio este Warning, me podrian ayudar por favor.....

== Problem setting up ssl connection: error:00000000:lib(0):func(0):reason(0)
[Sep 27 13:46:58] WARNING[1986]: tcptls.c:254 handle_tcptls_connection: FILE * o
pen failed!
== Problem setting up ssl connection: error:00000000:lib(0):func(0):reason(0)
[Sep 27 13:47:14] WARNING[1987]: tcptls.c:254 handle_tcptls_connection: FILE * o
pen failed!
== Problem setting up ssl connection: error:00000000:lib(0):func(0):reason(0)
[Sep 27 13:47:26] WARNING[1988]: tcptls.c:254 handle_tcptls_connection: FILE * o
pen failed!
== Problem setting up ssl connection: error:00000000:lib(0):func(0):reason(0)
[Sep 27 13:47:46] WARNING[1989]: tcptls.c:254 handle_tcptls_connection: FILE * o
pen failed!
TAPSA-ASTERISK*CLI>

[navaismo]

Como lo cometo Christian en otro post, se debe a que el equipo del cliente no tiene el CA.cert instalado, en windows se instala dandole doble click al certificado.

[Christian Cabrera]

Y si lo estás haciendo con un teléfono físico (como el Yealink T20P) debes de irte a la parte de seguridad e instalar el certificado ca.crt dentro del teléfono.