DIVERSION AFTER PELPI

[aau2]

Hi, I have a client with a repeated diverssion, and one of the answering position is an extension that can divert her phone to other, but the call doesn´t progress to the diverted position.
The list is :
<pelpp:dir=89645;
PERSONAL NUMBER LISTS INFORMATION

PERSONAL NUMBER:89645
LIST CHO ANSPOS TIME BSYCHO ONECAL ORGSEL SMSSEL
1 1 21502 18 - 1 111 0
1 2 89999 60 - 1 111 0

And the 89999 diverts the phone to other phone, and the call doesn´t continue to the diverted position.
How can I do that this works?

Thanks

 

[velovooma]

Your BSYCHO setting for the first line needs to be same as the second lines CHO number so
for ANSPOS=21502 the BSYCHO=2

 

[aau2]

The bsycho is 0 in both choices. th problem is that when the 89999 diverts to other number, the call doesn´t continue to the diverted position.

 

[parnum]

it won't, it will only go to the positions listed

 

[lalrl]

In my AS (BC12 SP9) it works. I have the profile 1 active. anspos=1 goes to a digital phone. If I make there *21*DECT-Phone# - Diversion follows. I do not know why because so far I also thought, that individual diversion will be ignored by PN, but it works indeed...

 

[fouesnant]

Hi Lalrl

I agree with parnum : it must not work.
A diversion of an extension within a profile exclude this position from the profile
Here is an example from my exchange
[tt]
<pelpp:dir=10111;
PERSONAL NUMBER LISTS INFORMATION

PERSONAL NUMBER:10111
LIST CHO ANSPOS TIME BSYCHO ONECAL ORGSEL SMSSEL
1 1 10111 6 - 1 111 0
1 2 20002 6 - 1 111 0
1 3 10003 6 - 1 111 0


END

<susip:dir=20002;
STATUS INFORMATION AT 11:13:35 22JUN06
DIR TYPE TRAFFIC STATE/PTR LINE STATE/PTR DIV STATE ADD INFO
20002 DTS IDLE #027A FREE #03D6 BSY,NAN
ODN1:IDLE FME DIV=78005
ODN2:IDLE
ODN3:IDLE
END
[/tt]
Doing this make extension 20002 not ringing within the profile, nor the call presented to extension 78005.

I guess that in your case, you make the diversion on the phone that support the profile; then it could work as the diversion feature override the profile feature.

 

[lalrl]

No, I do the FME to the anspos, and not to the called Number. Believe me, it works. Maybe a patch is the prolbem, multidiv or whatever...

 

[parnum]

i am interested in how this is working lalrl, as i have many customers who would like this but it has never happened at any site using pelpi at any SP from BC10 up to latest BC including BC13?????

 

[rfpui]

Solution

From BC 12.1 (SP4) command PELCS (and PELCP) is allowed with parameter SERV.
Where SERV=D1 or SERV=D1D2. and
D1=
0=Repeated deflection after diversion/follow me is NOT allowed.
1=Repeated deflection after diversion/follow me is allowed.

It work fine in BC 13 but not in 12 SP9 Application Standard.
May be somebody can test it in BC 12 SP9 and send to forum result of test?


----------------------------------
If anything can go wrong, it will.
(Murphy's Law)

 

[lalrl]

to rfpui

you speak about an other traffic-case. With serv=d1 you decide this question:

- A makes fme to B.
- B has active PN-list

If A is called: Shall PN be ignored or not?

My case means:

- A has active PN, with anspos B
- B has fme to C

If A is called, C is ringing

And this is the problem. So far I thought, any diversions of the anspos-members are ignored, if MD carry out the active PN-List