You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using homer and have noticed that when we retrieve the pcap for a call which ends with a SIP REFER - 202 - NOTIFY, where the NOTIFY tells us the final status of the transferred call, that the pcap for the call showing the INVITE...REFER does not include the NOTIFY-200 OK. We see that the NOTIFY messages are kept in a different table in postgres, but we hoped that when pulling the sip trace/pcap for a call we would have all the in-dialog requests included, but we don't see the NOTIFY.
Are we possibly doing something wrong, or is this a bug of sorts? If so, is there any suggested workaround?
The text was updated successfully, but these errors were encountered:
yeah, this is not a bug, just a feature ;-) we don't have transactions tracking therefore all NOTIFY messages go to "_rest" table. Can you please share one of this NOTIFY (you can do topoh) and we can add an exception for such NOTIFY messages.
We are using homer and have noticed that when we retrieve the pcap for a call which ends with a SIP REFER - 202 - NOTIFY, where the NOTIFY tells us the final status of the transferred call, that the pcap for the call showing the INVITE...REFER does not include the NOTIFY-200 OK. We see that the NOTIFY messages are kept in a different table in postgres, but we hoped that when pulling the sip trace/pcap for a call we would have all the in-dialog requests included, but we don't see the NOTIFY.
Are we possibly doing something wrong, or is this a bug of sorts? If so, is there any suggested workaround?
The text was updated successfully, but these errors were encountered: