< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index  

Re: [reSIProcate] Issues with ClientSubscription issuing local 408 timeouts


Looking at the resip logs, the SUBSCRIBE/202 either never arrived, or failed the preparse. Furthermore, it appears that the other end is either not receiving the retransmissions of the SUBSCRIBE, or is failing to retransmit the 202 when they come in. You might want to do captures on both ends, and see whether they are consistent. Also, turning the log-level up to TRACE will let us know whether we are having a preparse failure or not.

My guess is that a firewall is biting you somehow.

Best regards,
Byron Campen

So our implementation with ClientSubscription works most of the time, however every now and then when we create a new ClientSubscription about half of the requests will generate a local 408 even though the subscription was already created and ACK’ed and NOTIFY’ied.

 

Attached is the resip log without DNS or STATS catagories (we don’t log those in our application) for a single SUBSCRIBE request from aron@xxxxxxxxxxxxxxxxxx to roger@xxxxxxxxxxxxxxxxxx .

Also attached is a pcap file showing the full transaction with our OpenSER presence server.

 

The pcap and log file shows all the behavior:

 

SUBSCRIBE -> 202 OK -> NOTIFY -> 200 OK behavior. However, you will keep seeing the client issuing retransmissions on the initial SUBSCRIBE request even though the 202OK and NOTIFY came in.

 

Any help would be appreciated. It seems like a second AppDialog set is getting created if you look at the resip log, but I can’t figure out why it wasn’t matching the first one, or why this is a transient issue that doesn’t happen all the time (or if it is an OpenSER issue)

 

Resiprocate version is 1.0 with most of the patches that made it into 1.1. Will try a fully up2date head version too see if this exists in the latest version

 

-Aron

 

 

 

 

 

<resip_subscribe.pcap>
<resip_log.txt>
_______________________________________________
resiprocate-devel mailing list

Attachment: smime.p7s
Description: S/MIME cryptographic signature