Call Diversion Using Diversion Header

1. General
1

Hello everyone,

We would like to seek assistance on configuring call diversion in ProSBC using the Diversion header.

Call Scenario
Calling Party: +1XXXXXXX (External number)
Called Party: +2XXXXXXX (Registered in ProSBC and part of an inbound/outbound route)
Forward-To Party: +3XXXXXXX (External number)

Call Flow Description
1.) The external caller +1XXXXXXX places a call to +2XXXXXXX.
2.) The number +2XXXXXXX, after receiving the call, initiates a call forward/diversion to another external number +3XXXXXXX.
3.) During this diversion process, a Diversion header is correctly included in the SIP INVITE and contains the value +2XXXXXXX.
4.) However, the call fails with a 404 Not Found.

Observation and Issue

  • The From header remains as +1XXXXXXX, which is expected and desired by the client (i.e., the forwarded call should appear as if it’s coming from the original caller).
  • However, since +1XXXXXXX is not part of the outbound routes(Calling Field) in ProSBC, the call is being rejected.
  • The Diversion header, which correctly indicates the internal party +2XXXXXXX (the one triggering the diversion), is present, but ProSBC does not seem to route based on it.

Inquiry
1.) How can we configure ProSBC to allow call diversion where the From header remains as the orignal calling party (i.e +1XXXXXXX), but the routing decision is based on the Diversion header (i.e., +2XXXXXXX, the number that initiated the diversion)?

2.) Is it possible to apply this configuration only to a specific NAP or set of Routes in ProSBC, rather than system-wide?

1 Like
2

We have already reply this question via Email.

To answer this question:
Yes, this can be done with custom scripting. However, we don’t have a sample script for this yet. It needs custom development with Professional Services.