OUTGOING COLP

Post Reply
User avatar
selectt
Member
Posts: 158
Joined: 04 Jan 2010 05:50

OUTGOING COLP

Post by selectt »

We have an issue with oxo with outgoing CLI.

We have 22 incoming numbers into the oxo all with different LOCAL area codes.

Incoming calls are working fine using the DDI modification table.

The issue is ensuring the right user emits the correct telephone number and LOCAL area code.

Here is an example of the DDI modification table/PUBLIC numbering plan

INDEX EXTERNAL DDI INTERNAL DDI START END BASE
01 16422 1 SUB 1134568 2134568 200
01 19126 2 SUB 2245675 2245675 201
01 19088 3 SUB 3456765 3456765 202
01 17404 4 SUB 4772401 4772401 203
01 17745 5 SUB 5930366 2134568 204
01 18446 6 SUB 6208755 6208755 205
01 12317 7 SUB 7134500 7134500 206
01 19248 8 SUB 8568888 8568888 207
01 15679 9 SUB 9679879 9679879 208
01 14531 1 SUB 1997733 1997733 209
01 19942 2 SUB 2897713 2897713 210
01 12234 3 SUB 3891111 3891111 211
01 14566 4 SUB 4989892 4989892 212
01 17777 5 SUB 2568989 2568989 213


Like i said this is working fine routing incoming calls.

I have programmed user 209 with an alternative CLIP/COLP as 1997733

It SHOULD emit = 014531 997733 but it takes the FIRST INDEX LOCAL AREA code beginning with 1 as the internal number and emits 01642 997733,his actually comes up as a with held number but the trace states the wrong number.

Another example.

I have programmed user 213 with an alternative CLIP/COLP as 2568989

It SHOULD emit = 01777 2568989 but it takes the FIRST INDEX LOCAL AREA code beginning with 5 and emits 017455 2568989, this actually comes up as a with held number but the trace states the wrong number.


i have modified the internal number on the DDI medication table INTERNAL to 2 , 3 and 4 digits but it seems to look at the first digit of the ALT CLIP/COLP and attach the FIRST AREA code.

There are 250 entries allowed what is the purpose if can use 10 ( 0, 1-9) as the alternative COLP.

Any help would be appreciated.
Post Reply

Return to “MAIN”