Project

General

Profile

Wiki » FAQ »

Caller ID sending when forwarding call to mobile

1. Depending on the telephone service provider:

1.1. ORANGE ROMANIA

Feature activation request at Orange

Orange is requested to activate the call forward identity presentation configuration for SIP Trunk.

Call forward identity presentation:

If a call forward is activated on the customer's IP-PBX (B party), using this service the C party user will see the identity of the A party.
It is mandatory to receive the Call Forward information from the customer's IP-PBX! Call Forward scenarios based on the INVITE message sent by the customer, as a response to the initial INVITE, with no forward information available is not allowed.

Call Forward information can be sent in the following headers:
  1. History-Info header
  2. Diversion header
  3. History-Info and Diversion

While1 is using Diversion header, together with P-Asserted-Identity:

P-Asserted-Identity: <tel:${CALLER_NUMBER}>
Diversion: <tel:${CALLED_EXTEN}>;reason=no-answer;screen=no;privacy=off

1.2. RCS RDS

Changing DNS

To forward the CallerID to the mobile phone, it is necessary to change the DNS from: 82.76.7.30, 82.76.7.26 to 81.196.197.132, 81.196.197.164.
All other settings remain unchanged.

Request for changes to RCS RDS

When you made the change, please contact , so that it can also be changed on the SIP server.

2. Edit files

For fallback numbers:

Access PBX :: Users :: Edit User and set the value FALLBACK_NUMBERS_OUTBOUND_NUMBER from the Variables area:

For Forwards (Inbound route):

extensions.conf

FORWARDS_USE_CALLER_NUMBER=1 ; set Diversion header (HEADER_DIVERSION) for forwarded calls - Orange only

3. Build Users

PBX :: Users - Fallback number - Ring simultaneously ON & Build now

Available in other languages: RO