Hello,
few clarifications about siptrace, see inline ...
On 5/22/12 9:31 AM, Marius Zbihlei wrote:
On 05/22/2012 10:07 AM, Klaus Darilion wrote:
In my opinion it would be cool if core has a feature to log every
received and every sent message. The logging should include
timestamp+proto+sourceI
On 05/22/2012 10:07 AM, Klaus Darilion wrote:
In my opinion it would be cool if core has a feature to log every
received and every sent message. The logging should include
timestamp+proto+sourceIP:port+receivedIP:port for received messages and
timestamp+proto+sourceIP:port+destinationIP:port for
I second that.
Siptrace doesn't log everything, but workarounds can be done, such as using
a combination of setting a flag and using the sip_trace( ) function, and
using them as well from the onsend_route for some outgoing messages, with
careful handling to prevent duplicate logging.
Reda
On T
In my opinion it would be cool if core has a feature to log every
received and every sent message. The logging should include
timestamp+proto+sourceIP:port+receivedIP:port for received messages and
timestamp+proto+sourceIP:port+destinationIP:port for sent messages. For
TLS of course it should l
Hi Knostantin,
I have looked at your patch and it seems that you use a module that
registers a response function which returns 0. The problem is not
actually in the forward.c file but with that function.
Can you please tell me which is the list of modules that you are using?
Regards,
Anca
Hi Anca,
I fixed this problem with your help. A modified patch is attached.
Thanks!
2012/5/16 Konstantin M.
> Hi Anca,
>
>
> Yes, I will explain.
>
> Let's assume we have a kamailio config, attached as main.cfg (it's a very
> simplified, I have excluded a lot of customization here).
>
> Debug
Hi Konstantin,
Can you tell me exactly what you are calling in onsend_route and how you
observe it is not working?
Regards,
Anca
On 05/15/2012 04:55 PM, Konstantin M. wrote:
Hi Anca,
I've tested your patch and I don't think it's working.
At least I was noticed that a logic is going to 'sk
Hi Anca,
I've tested your patch and I don't think it's working.
At least I was noticed that a logic is going to 'skip' label on 183 sdp:
/* check modules response_f functions */
for (r=0; r
> **
> Hi Konstantin,
>
>
> I have attached the patch that allows calling onsend route also
Hi Konstantin,
I have attached the patch that allows calling onsend route also for
replies. After the 3.3 release is done, I will commit it also upstream.
Regards,
Anca
On 05/14/2012 09:00 PM, Konstantin M. wrote:
Hi Marius,
My opinion that a replies should be routed to onsend_route after
Hello,
there is no particular reason to avoid extending the code so that
onsend_route is executed for replies. It wasn't done because no
developer/contributed needed it (or didn't make the code public).
I had it in mind, but lack of time and no real need for myself set lower
priority.
If M
Hi Marius,
My opinion that a replies should be routed to onsend_route after
onreply_route in order unless they are dropped in onreply_route.
It's by a common sense I think. All the traffic that is being
sent/replied/forwarded and so on (in a short, all outgoing traffic) should
trigger some callbac
On 05/11/2012 11:24 PM, Konstantin M. wrote:
Hi Daniel,
For some reasons, onsend_route doesn't triggered when transfering
100,180,183, etc...
Hello,
Normally, onsend_route is not triggered for replies, only for messages.
If there are some good reasons behind it, I don't know, as we have a
Hi Daniel,
For some reasons, onsend_route doesn't triggered when transfering
100,180,183, etc...
2012/5/11 Daniel-Constantin Mierla
> Hello,
>
> debug messages printed to syslog from the source code are because the
> developer needed/wanted them for troubleshooting.
>
> As an admin, you have
Hello,
On 5/9/12 11:45 PM, Bruno Bresciani wrote:
Hi all,
Why kamailio send to syslog only received SIP messages? I want see
the messages that kamailio send to the UAs, it's possible?
On TCP/TLS SIP messages there is a degub of buffer with the message
that will be send, but a strange content
14 matches
Mail list logo
