Feature Request: Show packets with non standard Methods

[hb9eue]

Hi and thank you for this exceptionally useful tool.

I manage a kamailio based VSP voice platform and we use DMQ (Sip Method KDMQ) to synchronize some information between nodes.

As KDMQ messages are shown by sngrep I assumed it would show any SIP Method even if not in an RFC.

We had the need to trigger some stuff from one node to another and it turned out the simples way is to use a 'internal' sip message for this purpose. Something like:

INTERNAL sip:node01:5060 SIP/2.0
To: <sip:functionXY@node01:5060>
From: <sip:FNtrigger@node02>;tag=19f84cb2cd8b466049b93aa9541a4ef9-95d36d9b
CSeq: 1 INTERNAL
Call-ID: 251e9b302d57fedb-1746803@node02
Max-Forwards: 70
Content-Length: 0

Actual use case: We use hash caching of call forwarding information. So if a customer changes call forwarding, all cached CFW data for this customer needs to be invalidated on all nodes to make changed CFW information active immediately.

SIP messages of method 'INTERNAL' are not shown by sngrep.

Would it be possible to create an option to also show SIP messages for unknown methods?

-Benoît-

[hb9eue]

Possibly a bug related to this. When initially starting without filters, sngrep show Method KDMQ. When opening the filter, this method is not shown, but when you then apply any filter, there is no way to get KDMQ method being displayed again.

[Kaian]

Hi,

Looks like an interesting feature, but it may have quite an impact in code, because methods are fixed right now.

Possibly a bug related to this. When initially starting without filters, sngrep show Method KDMQ. When opening the filter, this method is not shown, but when you then apply any filter, there is no way to get KDMQ method being displayed again.

Yep, we didn't update filters screen with KDMQ when we added it. It was required for a coworker so it was added a bit silently. You can still choose what methods you want to display using configuration file using filter.method setting:

$ sngrep -D | grep methods
SettingId: 40    SettingName: filter.methods       Value: REGISTER,INVITE,SUBSCRIBE,NOTIFY,OPTIONS,PUBLISH,MESSAGE,INFO,REFER,UPDATE,KDMQ

Best regards,

[hb9eue]

Hi thank you for the reply.

Just some off-topic comment on the topic why I considered using a customer sip method. With kamailio, there is a different method to make sure such information is in sync across nodes.

if you specify the attribute dmqreplicate=1 on the htable definition, updates are automatically synced via KDMQ to all nodes. So no need for the intended custom sip method 'hack'.