Mailing List Archive: UCCX Callback Call Redirect Adding Diversion Header

UCCX Callback Call Redirect Adding Diversion Header

Apr 21, 2020, 10:39 AM

Post #1 of 4 (893 views)

Hey everyone,

I'm working on a UCCX Callback deployment which seems to be a weekly thing
lately.

But in this customer's environment, I'm noticing the outbound Call Redirect
Step is actually causing a diversion header to be sent out the Customer SIP
Trunk on the Outgoing Invite. The phone number is actually the destination
number we're doing the callback to.

Diversion: <sip:915555551212@10.0.0.1
>;reason=deflection;privacy=off;screen=yes

They've got Redirecting number outbound checked on the SIP Trunk for
call-forwarding/SNR to preserve the original calling number correctly.

The carrier is not accepting the call because of the Diversion header and
the agent gets a message from the carrier "call cannot be completed as
dialed".

I've tried sending the call through a translation pattern but that didn't
seem to strip out the redirecting number.

I'm curious if anyone has seen this with a callback script because I don't
remember a Diversion header being normal but maybe I've just always missed
it.

I can't turn off the Diversion header completely without breaking
call-forwarding.

Only thing I can think of would be a LUA script to strip the Diversion
header if the Calling Number is for an agent extension since those
shouldn't be ever forwarded anyways.

Anyone got any ideas on how to strip off this Diversion header just for
these callback calls?

Thanks,
Brian Meade

Re: UCCX Callback Call Redirect Adding Diversion Header [ In reply to ]

kent at fredf

Apr 21, 2020, 12:00 PM

Post #2 of 4 (893 views)

Permalink

Can you prepend an access code on it and use a different trunk port/dial peer and strip it that way?

Kent

> On Apr 21, 2020, at 11:41, Brian Meade <bmeade90@vt.edu> wrote:
>
> ?
> Hey everyone,
>
> I'm working on a UCCX Callback deployment which seems to be a weekly thing lately.
>
> But in this customer's environment, I'm noticing the outbound Call Redirect Step is actually causing a diversion header to be sent out the Customer SIP Trunk on the Outgoing Invite. The phone number is actually the destination number we're doing the callback to.
>
> Diversion: <sip:915555551212@10.0.0.1>;reason=deflection;privacy=off;screen=yes
>
> They've got Redirecting number outbound checked on the SIP Trunk for call-forwarding/SNR to preserve the original calling number correctly.
>
> The carrier is not accepting the call because of the Diversion header and the agent gets a message from the carrier "call cannot be completed as dialed".
>
> I've tried sending the call through a translation pattern but that didn't seem to strip out the redirecting number.
>
> I'm curious if anyone has seen this with a callback script because I don't remember a Diversion header being normal but maybe I've just always missed it.
>
> I can't turn off the Diversion header completely without breaking call-forwarding.
>
> Only thing I can think of would be a LUA script to strip the Diversion header if the Calling Number is for an agent extension since those shouldn't be ever forwarded anyways.
>
> Anyone got any ideas on how to strip off this Diversion header just for these callback calls?
>
> Thanks,
> Brian Meade
> _______________________________________________
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip

Re: UCCX Callback Call Redirect Adding Diversion Header [ In reply to ]

bmeade90 at vt

Apr 21, 2020, 12:39 PM

Post #3 of 4 (890 views)

Permalink

I think that should work! I can strip it on the dial-peer side to remove
the Diversion header for those new dial-peers.

On Tue, Apr 21, 2020 at 3:01 PM Kent Roberts <kent@fredf.org> wrote:

> Can you prepend an access code on it and use a different trunk port/dial
> peer and strip it that way?
>
>
> Kent
>
> On Apr 21, 2020, at 11:41, Brian Meade <bmeade90@vt.edu> wrote:
>
> ?
> Hey everyone,
>
> I'm working on a UCCX Callback deployment which seems to be a weekly thing
> lately.
>
> But in this customer's environment, I'm noticing the outbound Call
> Redirect Step is actually causing a diversion header to be sent out the
> Customer SIP Trunk on the Outgoing Invite. The phone number is actually
> the destination number we're doing the callback to.
>
> Diversion: <sip:915555551212@10.0.0.1
> >;reason=deflection;privacy=off;screen=yes
>
> They've got Redirecting number outbound checked on the SIP Trunk for
> call-forwarding/SNR to preserve the original calling number correctly.
>
> The carrier is not accepting the call because of the Diversion header and
> the agent gets a message from the carrier "call cannot be completed as
> dialed".
>
> I've tried sending the call through a translation pattern but that didn't
> seem to strip out the redirecting number.
>
> I'm curious if anyone has seen this with a callback script because I don't
> remember a Diversion header being normal but maybe I've just always missed
> it.
>
> I can't turn off the Diversion header completely without breaking
> call-forwarding.
>
> Only thing I can think of would be a LUA script to strip the Diversion
> header if the Calling Number is for an agent extension since those
> shouldn't be ever forwarded anyways.
>
> Anyone got any ideas on how to strip off this Diversion header just for
> these callback calls?
>
> Thanks,
> Brian Meade
> _______________________________________________
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>

Re: UCCX Callback Call Redirect Adding Diversion Header [ In reply to ]

bmeade90 at vt

Apr 21, 2020, 9:27 PM

Post #4 of 4 (887 views)

Permalink

Ended up switching to a Consult Transfer step instead. Now it's hold music
rather than true ringback but works pretty well. I can change the hold
music to fake ringback if it becomes an issue.

On Tue, Apr 21, 2020 at 3:39 PM Brian Meade <bmeade90@vt.edu> wrote:

> I think that should work! I can strip it on the dial-peer side to remove
> the Diversion header for those new dial-peers.
>
> On Tue, Apr 21, 2020 at 3:01 PM Kent Roberts <kent@fredf.org> wrote:
>
>> Can you prepend an access code on it and use a different trunk port/dial
>> peer and strip it that way?
>>
>>
>> Kent
>>
>> On Apr 21, 2020, at 11:41, Brian Meade <bmeade90@vt.edu> wrote:
>>
>> ?
>> Hey everyone,
>>
>> I'm working on a UCCX Callback deployment which seems to be a weekly
>> thing lately.
>>
>> But in this customer's environment, I'm noticing the outbound Call
>> Redirect Step is actually causing a diversion header to be sent out the
>> Customer SIP Trunk on the Outgoing Invite. The phone number is actually
>> the destination number we're doing the callback to.
>>
>> Diversion: <sip:915555551212@10.0.0.1
>> >;reason=deflection;privacy=off;screen=yes
>>
>> They've got Redirecting number outbound checked on the SIP Trunk for
>> call-forwarding/SNR to preserve the original calling number correctly.
>>
>> The carrier is not accepting the call because of the Diversion header and
>> the agent gets a message from the carrier "call cannot be completed as
>> dialed".
>>
>> I've tried sending the call through a translation pattern but that didn't
>> seem to strip out the redirecting number.
>>
>> I'm curious if anyone has seen this with a callback script because I
>> don't remember a Diversion header being normal but maybe I've just always
>> missed it.
>>
>> I can't turn off the Diversion header completely without breaking
>> call-forwarding.
>>
>> Only thing I can think of would be a LUA script to strip the Diversion
>> header if the Calling Number is for an agent extension since those
>> shouldn't be ever forwarded anyways.
>>
>> Anyone got any ideas on how to strip off this Diversion header just for
>> these callback calls?
>>
>> Thanks,
>> Brian Meade
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip@puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>