sr-users July 2012

sr-users@lists.kamailio.org

64 participants
92 discussions

TCP Forwarding error: cannot forward to af 2, proto 2 no correspondinglistening socket

by Omar Labs 188 Gmail

tried many versions in version 1.4 i have this error: Jun 29 21:25:04 [7309] ERROR:core:forward_request: cannot forward to af 2, proto 2 no correspondinglistening socket i do have the TCP port listen explicitly the line for disable-tcp is commented. listen=udp:192.168.169.169:5060 listen=udp:192.168.169.169:5060 if ( src_ip == 192.168.169.180 ) { forward("tcp:192.168.170.156:5060"); } I tried already many options related the forward command , using variables and using forward(); ``Listening on udp: 192.168.169.169 [192.168.169.169]:5060 tcp: 192.168.169.169 [192.168.169.169]:5060 Aliases: tcp: loghost:5060 tcp: kamtest01:5060 udp: loghost:5060 udp: kamtest01:5060 bash-3.00# telnet 192.168.169.169 5060 Trying 192.168.169.169... Connected to 192.168.169.169. Escape character is '^]'. Connection to 192.168.169.169 closed by foreign host. bash-3.00# kamctl ps Process:: ID=0 PID=4541 Type=attendant Process:: ID=1 PID=4542 Type=SIP receiver udp:192.168.169.169:5060 Process:: ID=2 PID=4543 Type=SIP receiver udp:192.168.169.169:5060 Process:: ID=3 PID=4544 Type=SIP receiver udp:192.168.169.169:5060 Process:: ID=4 PID=4545 Type=SIP receiver udp:192.168.169.169:5060 Process:: ID=5 PID=4546 Type=SIP receiver udp:192.168.169.169:5060 Process:: ID=6 PID=4547 Type=SIP receiver udp:192.168.169.169:5060 Process:: ID=7 PID=4548 Type=SIP receiver udp:192.168.169.169:5060 Process:: ID=8 PID=4549 Type=SIP receiver udp:192.168.169.169:5060 Process:: ID=9 PID=4550 Type=SIP receiver udp:192.168.169.169:5060 Process:: ID=10 PID=4551 Type=SIP receiver udp:192.168.169.169:5060 Process:: ID=11 PID=4552 Type=SIP receiver udp:192.168.169.169:5060 Process:: ID=12 PID=4553 Type=SIP receiver udp:192.168.169.169:5060 Process:: ID=13 PID=4554 Type=SIP receiver udp:192.168.169.169:5060 Process:: ID=14 PID=4555 Type=SIP receiver udp:192.168.169.169:5060 Process:: ID=15 PID=4556 Type=SIP receiver udp:192.168.169.169:5060 Process:: ID=16 PID=4557 Type=SIP receiver udp:192.168.169.169:5060 Process:: ID=17 PID=4558 Type=SIP receiver udp:192.168.169.169:5060 Process:: ID=18 PID=4559 Type=SIP receiver udp:192.168.169.169:5060 Process:: ID=19 PID=4560 Type=SIP receiver udp:192.168.169.169:5060 Process:: ID=20 PID=4561 Type=SIP receiver udp:192.168.169.169:5060 Process:: ID=21 PID=4562 Type=timer Process:: ID=22 PID=4563 Type=MI FIFO Process:: ID=23 PID=4564 Type=TCP receiver Process:: ID=24 PID=4565 Type=TCP receiver Process:: ID=25 PID=4566 Type=TCP receiver Process:: ID=26 PID=4567 Type=TCP receiver Process:: ID=27 PID=4568 Type=TCP receiver Process:: ID=28 PID=4569 Type=TCP receiver Process:: ID=29 PID=4570 Type=TCP receiver Process:: ID=30 PID=4571 Type=TCP receiver Process:: ID=31 PID=4572 Type=TCP receiver Process:: ID=32 PID=4573 Type=TCP receiver Process:: ID=33 PID=4574 Type=TCP main O

11 years, 9 months

How to access reason phrase of winning reply in failure_route

by Barthel Marco (CI/AFU1)

All, how do I access the reason phrase of winning reply in failure_route? The reply code can be accessed via $T_reply_code. Is there something similar for the reason phrase? Mit freundlichen Grüßen / Best regards Marco Barthel Robert Bosch GmbH (CI/AFU1) www.bosch.com Tel. +49 711 811-3602341 marco.barthel(a)de.bosch.com Sitz: Stuttgart, Registergericht: Amtsgericht Stuttgart, HRB 14000; Aufsichtsratsvorsitzender: Franz Fehrenbach; Geschäftsführung: Volkmar Denner, Siegfried Dais; Stefan Asenkerschbaumer, Bernd Bohr, Rudolf Colm, Dirk Hoheisel, Christoph Kübel, Uwe Raschke, Wolf-Henning Scheider, Werner Struth, Peter Tyroller

11 years, 9 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users July 2012