Hi Daniel.
Seems yes, it is captured properly.
--
Best regards,
Sergey Basov e-mail: sergey.v.ba...@gmail.com
tel: (+38067) 403-62-54
2016-01-13 23:14 GMT+02:00 Daniel-Constantin Mierla :
> Hi Sergey,
>
> thanks for testing and the feedback. The patch is also useful to have
Hi Sergey,
thanks for testing and the feedback. The patch is also useful to have
around for those than want to get the feature in 4.3 by one step, not
cherry picking each commit.
One more thing: are the local message properly captured? I mean the
replies generated with sl_send_reply()/t_reply() a
Hi Daniel.
I just build with latest commit.
It work as expected now.
Now I can see captured packets as they was send and received by
kamailio via network interfaces.
Thank you very match.
I make patch which backports your commits to kamailio 4.3.4
please find it in attach
--
Best regards,
Sergey
Earlier today I pushed the patch to catch the incoming traffic before
topoh gets the chance to decode it. If you can try with latest master
and report the results, it will be appreciated.
Cheers,
Daniel
On 12/01/16 11:02, Sergey Basov wrote:
> I am sorry.
> I have missed commit 4fc969760d8eec6355
You should see the received packets if you use latest master, but they
are not yet captured before topoh decodes them.
Cheers,
Daniel
On 12/01/16 09:45, Sergey Basov wrote:
> Thank you for commits.
>
> I just try it and now I can see that sending packets captured properly..
>
> Now there is a pro
I am sorry.
I have missed commit 4fc969760d8eec6355ce661ccd3c5fd9ad2a36f0...
Now all works as I had expected.
Than you so match.
If you are interesting, I now try to backport changes to kamailio 4.3.4.
When it will be done I can email patch file to you.
--
Best regards,
Sergey Basov
Thank you for commits.
I just try it and now I can see that sending packets captured properly..
Now there is a problem with receiving packets, I does not see Initial
invite from client into the capture.
--
Best regards,
Sergey Basov e-mail: sergey.v.ba...@gmail.com
tel: (+
On 06/01/16 11:49, Daniel-Constantin Mierla wrote:
> [...]
>> But Packet which is send by siptrace module to homer capture server is
>> send before topoh modifications.
>>
>> If you can correct this flow it will be great.
> I will look into it as I said before.
Can you try with master branch? I p
On 06/01/16 11:00, Sergey Basov wrote:
> Thank you for patch.
>
> I have applied patches from your commits
> 526fb4cdc2246284ecbd7de9ed65678da2dbe357 and
> 284c11ed16bdc5afcc9abf49c9f5c1749ce831e0
> to kamailio 4.3.4 it was applied and build successfully.
>
> There is no more errors in kamailio.l
Thank you for patch.
I have applied patches from your commits
526fb4cdc2246284ecbd7de9ed65678da2dbe357 and
284c11ed16bdc5afcc9abf49c9f5c1749ce831e0
to kamailio 4.3.4 it was applied and build successfully.
There is no more errors in kamailio.log.
But Packet which is send by siptrace module to hom
On 06/01/16 09:19, Sergey Basov wrote:
> Sorry, not only ACK.
> There is ACK, INVITE, ACK and BYE
OK.
I pushed two patches to master branch that should fix the issue with the
error log messages. Can you test with master branch? If all goes fine,
then I will consider backporting.
For capturing
Sorry, not only ACK.
There is ACK, INVITE, ACK and BYE
I am using kamailio as statefull proxy.
So in case of normal callflow there is REGISTER and so on..
And with sip_trace enabled in onsend_route errors in kamailio.log still persist.
Jan 6 10:12:01 sip1 /usr/sbin/kamailio[30545]: INFO:
No other SIP requests? Only the ACK?
Cheers,
Daniel
On 06/01/16 07:55, Sergey Basov wrote:
> I just try it.
> I got only last ACK when call was finished.
>
> I think than siptrace must catch and send duplicate message after topoh
> module.
> Because in other case we can see message as it is ins
I just try it.
I got only last ACK when call was finished.
I think than siptrace must catch and send duplicate message after topoh module.
Because in other case we can see message as it is inside kamailio,
not message that will be send to upstream or client...
WBR.
--
Best regards,
Sergey Basov
If you try to use the sip_trace() function inside onsend_route{ }, what
messages do you get?
Cheers,
Daniel
On 05/01/16 15:38, Sergey Basov wrote:
> It will be great, because I am using sip TLS in production environment.
> This is why I can not using homer capture agent...
--
Daniel-Constantin
It will be great, because I am using sip TLS in production environment.
This is why I can not using homer capture agent...
--
Best regards,
Sergey Basov e-mail: sergey.v.ba...@gmail.com
SATB-RIPE
SATB-UANIC
tel: (+38067) 403-62-54
2016-01-05 15:37 GMT+02:00 Daniel-Constantin
On 05/01/16 14:05, Sergey Basov wrote:
> And one more thing.
>
> In captured packet from Homer, I see original SIP packets, without
> topoh modifications.
> But in dump from network interface by wireshark i see that packets was
> modified...
sip_trace module is taking the sip message as it is pro
On 05/01/16 13:44, Sergey Basov wrote:
> Thanks for reply.
>
> I check one more time, and does not see any non SIP (HEP) packets
> received on port 5060 of kamailio.
>
> May bee parser trying to parse (HEP) packet when it going out via
> socket to capture server?
>
> When I turn of topoh module I
And one more thing.
In captured packet from Homer, I see original SIP packets, without
topoh modifications.
But in dump from network interface by wireshark i see that packets was
modified...
--
Best regards,
Sergey Basov e-mail: sergey.v.ba...@gmail.com
SATB-RIPE
SATB-UANIC
te
Thanks for reply.
I check one more time, and does not see any non SIP (HEP) packets
received on port 5060 of kamailio.
May bee parser trying to parse (HEP) packet when it going out via
socket to capture server?
When I turn of topoh module I does not see any errors in log.
And in both cases I se
Hello,
if you look at network trace on port 5060 for Kamailio, what packets do
you see being received? Be sure you wantch all sockets kamailio is
listening on (including loopback interface, if it is the case).
Cheers,
Daniel
On 05/01/16 09:33, Sergey Basov wrote:
> Hi, All.
>
> I have a strange
Hi, All.
I have a strange issue occuring, when I enable the siptrace
functionality within the routing logic, I begin to get a lot of
parser error as show below. Is this normal behavior?
This errors appears only when topoh module is enabled...
As I see with wireshark, there is no duplicates or re
22 matches
Mail list logo
