06-16-2018 01:37 PM - edited 03-17-2019 01:01 PM
I'm attempting to modify the diversion header when calling one specific number. I want to modify the reason=unconditional to reason=deflection. I've made a single peer that I confirmed is matched, and assigned a sip profile to the outgoing peer which I also confirmed I saw matched in the debugs. It doesn't appear to be matching the sip profile or at least it definitely isn't modifying the header like I'd want. The call flow is on prem -> first number on RP -> forward all to second number -> CUBE -> SIP trunk. Currently seeing reason=unconditional. I either need help understanding the sip diversion header matching/modification, and/or a better explanation for when a call gets set as unconditional versus deflection.
06-17-2018 11:12 AM
06-17-2018 02:56 PM
We believe this is causing problems with our carrier and want to prove it out. We eventually would want to change it the other way too, or at least understand better the circumstances around this message.
06-18-2018 07:28 AM
06-19-2018 10:35 AM
Didn't see your response...I need to scroll down more.
The SIP profile should work per testing with the test tool: https://cway.cisco.com/tools/SipProfileTest/
06-19-2018 10:30 AM
Can you post the initial INVITE message?
04-28-2024 08:56 PM
When you send to PSTN gateway. DIVERSION heder since you have the user@host part. You also need to add user=phone. Which I see is not there. Maybe thats the format your PSTN expects. May help
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide