[VoiceOps] Diversion header with counter=99

[Joseph Jackson]

Hi Matt,

>From rfc5806

   The Redirection Counter value minus 1 SHOULD be stored in the
   diversion- counter associated with the top-most Diversion header.
   Presence of the diversion-counter for the bottom-most Diversion
   header is optional.  If present, the diversion-counter of the bottom-
   most Diversion header SHOULD be 1.


If it's the bottom diversion header then anything not with 1 is going to have problems.

Why are you setting the counter to 99?

From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Matthew Yaklin
Sent: Wednesday, February 03, 2021 3:01 PM
To: voiceops at voiceops.org
Subject: [VoiceOps] Diversion header with counter=99

All,

Has anyone ran into an issue where the diversion parameter "counter" is causing some calls to fail to an error message?

Diversion: <sip:+1585xxxxxxx at 10.x.x.40:5060>;reason=unknown;counter=99

Basically we have a customer who forwards a call to their ATT cell. ATT plays an error message yet the customer's setup will pull the call back to our switch's voicemail after 30 seconds. This actually works if you let the error message play long enough. This setup works everywhere else like Verizon for example with no error message played. It rings as expected.

Our invite goes out with two diversion headers and the top one simply duplicates the bottom but with the counter param added.

I guess Level3 used to have this issue as well in the past? Because I found a Meta doc talking about this exact problem.

Any advice is welcome. Thanks,

Matt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20210203/569e87b3/attachment.htm>