Dmitry S Posted June 26, 2020 Report Posted June 26, 2020 Good day! We are facing an issue with diversion. Everything was correct earlier, when we had Kazoo version 4.3.34, but after update to 4.3.105, we are facing the issue with diversion. Nothing was changed, we have "should_add_diversion_header"true in 'system_config/kazoo_endpoint' . But in the final we do not have diversion header. Did somebody face the same? Or maybe somebody know what to check additionally? Quote
svisst Posted August 26, 2021 Report Posted August 26, 2021 I have the same problem on version 4.3.140. Did you manage to solve the problem? Quote
Guest DanH Posted August 31, 2021 Report Posted August 31, 2021 Hi @svisst, if you could provide some call logs with as many details as possible, we can try taking a look to see what stands out! Quote
svisst Posted September 10, 2021 Report Posted September 10, 2021 Hello! On 8/31/2021 at 9:16 PM, DanH said: Hi @svisst, if you could provide some call logs with as many details as possible, we can try taking a look to see what stands out! For the moment, What I did is: - Setting "should_add_diversion_header": "true" to system_config -> Kazoo_endpoint - On monster-ui, on device that have "Call Forwarding" enabled, have "Keep Original Caller-ID" checked In the ecallmgr log, I see: Sep 10 07:30:04 kazoo-db1 2600hz[1318]: |SBC4294681f9102c2e11e99b335659f9e36@10.200.66.5|ecallmgr_util:116(<0.29176.100>) building xferext on node freeswitch@kazoo-fs2.kazoo: bridge {call_timeout=20,originate_timeout=20,outbound_redirect_fatal='false',ignore_early_media='true',bridge_export_vars='hold_music',local_var_clobber='true'}[^^!presence_id='1001@fa6d8f.sip.kazoo'!ignore_early_media='true'!leg_timeout='20'!sip_h_X-KAZOO-AOR=sip:user_jMw53S@fa6d8f.sip.kazoo!sip_h_X-KAZOO-INVITE-FORMAT=username!sip_h_Diversion=<sip:4991234567@1.2.3.20>;reason=unconditional!ecallmgr_Retain-CID='true'!ecallmgr_Owner-ID='3cd8bee8727eea0c115e7da10c029b0a'!ecallmgr_Account-ID='2d9d413fd1f11a21fe3eef9e5e8b552f'!ecallmgr_Call-Forward='true'!ecallmgr_Authorizing-Type='device'!ecallmgr_Authorizing-ID='1fd877f07293518bef9dd6f9b28f4948'!ecallmgr_Call-Forward-From='offnet'!ecallmgr_Require-Ignore-Early-Media='true'!ignore_early_media='true'!loopback_bowout_on_execute='false'!loopback_bowout='true'!sdp_secure_savp_only='false'!sip_invite_domain='fa6d8f.sip.kazoo']loopback/89161234567/context_2 I see the same thing in the log FS. But the invite message is sent to the vendor without a field Diversion. Quote
svisst Posted November 19, 2021 Report Posted November 19, 2021 Hello everyone) maybe someone has encountered something like this. It is not possible to solve the problem yet. Quote
Guest DanH Posted November 29, 2021 Report Posted November 29, 2021 Hi @svisst circling back to this, I was chatting with the team and they asked for the following: Confirmation that you're on the latest 4.3 version Can you generate another call example where the diversion is in the logs but not on the INVITE I'll check back in here to see how this is coming, and as always the more detail you provide the better, thanks! Quote
svisst Posted December 6, 2021 Report Posted December 6, 2021 Hi @DanH! At the moment I have version 4.3.140. Within a few days I will update to 4.3.141. And provide the necessary data. Thanks for your reply. Quote
svisst Posted December 7, 2021 Report Posted December 7, 2021 Hi @DanH. I have updated the system. FS: Kazoo-applications: Kazoo-ecallmgr I sent the information with logs by a personal message. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.