Retrieving pcap for call with SIP REFER does not show the NOTIFY

[davehorton]

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?

[adubovikov]

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.

[spacetourist]

Hi Alexandr,

I am encountering something similar where NOTIFY messages for REFER events is ending up in hep_proto_1_default and is uncorrelated with the call with matching Call-ID which is stored in hep_proto_1_call.

Please let me know how I would approach getting these transactions merged with the matching dialogs. I've documented an example for a referred call below.

Many thanks,

Callum

 SIP/2.0 200 OK
 Via: SIP/2.0/UDP 192.168.153.111;received=192.168.153.111;rport=5060;branch=z9hG4bK8a7H6U8D8K6DB\r+
 Record-Route: <sip:192.168.153.21;lr;ftag=DNBHNmyr0a6pc>
 From: <sip:[email protected]>;tag=DNBHNmyr0a6pc
 To: <sip:[email protected]>;tag=834135821
 Call-ID: 27246aa6-2e29-4e8c-a28e-91e7f4d51f45
 CSeq: 92614224 NOTIFY
 Contact: <sip:[email protected]:41924>
 User-Agent: Yealink SIP-T31G 124.86.0.40
 Content-Length: 0
 
 
 SIP/2.0 200 OK
 Via: SIP/2.0/UDP 1.1.1.30:5060;branch=z9hG4bKc2b3.440a6856.0
 Via: SIP/2.0/UDP 192.168.153.111;received=192.168.153.111;rport=5060;branch=z9hG4bK8a7H6U8D8K6DB\r+
 Record-Route: <sip:1.1.1.30;lr;ftag=DNBHNmyr0a6pc>
 From: <sip:[email protected]>;tag=DNBHNmyr0a6pc
 To: <sip:[email protected]>;tag=834135821
 Call-ID: 27246aa6-2e29-4e8c-a28e-91e7f4d51f45
 CSeq: 92614224 NOTIFY
 Contact: <sip:[email protected]:5060>
 User-Agent: Yealink SIP-T31G 124.86.0.40
 Content-Length: 0
 
 
 NOTIFY sip:[email protected]:41924 SIP/2.0
 Record-Route: <sip:1.1.1.30;lr;ftag=DNBHNmyr0a6pc>
 Via: SIP/2.0/UDP 1.1.1.30:5060;branch=z9hG4bKc2b3.440a6856.0
 Via: SIP/2.0/UDP 192.168.153.111;received=192.168.153.111;rport=5060;branch=z9hG4bK8a7H6U8D8K6DB\r+
 Max-Forwards: 69
 From: <sip:[email protected]>;tag=DNBHNmyr0a6pc
 To: <sip:[email protected]>;tag=834135821
 Call-ID: 27246aa6-2e29-4e8c-a28e-91e7f4d51f45
 CSeq: 92614224 NOTIFY
 Contact: <sip:[email protected]:5060;transport=udp;gw=registrar>
 User-Agent: X-on
 Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REFER, NOTIFY
 Supported: timer, path, replaces
 Event: refer;id=3
 Allow-Events: talk, hold, conference, refer
 Subscription-State: terminated;reason=noresource
 Content-Type: message/sipfrag
 Content-Length: 16
 
 SIP/2.0 200 OK
 
 NOTIFY sip:[email protected]:41924 SIP/2.0
 Via: SIP/2.0/UDP 192.168.153.111;rport;branch=z9hG4bK8a7H6U8D8K6DB
 Route: <sip:192.168.153.21;lr;ftag=DNBHNmyr0a6pc;hyfr=d75.4b432814>
 Max-Forwards: 69
 From: <sip:[email protected]>;tag=DNBHNmyr0a6pc
 To: <sip:[email protected]>;tag=834135821
 Call-ID: 27246aa6-2e29-4e8c-a28e-91e7f4d51f45
 CSeq: 92614224 NOTIFY
 Contact: <sip:[email protected]:5060;transport=udp;gw=registrar>
 User-Agent: X-on
 Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REFER, NOTIFY
 Supported: timer, path, replaces
 Event: refer;id=3
 Allow-Events: talk, hold, conference, refer
 Subscription-State: terminated;reason=noresource
 Content-Type: message/sipfrag
 Content-Length: 16
 
 SIP/2.0 200 OK