Billing CDR prefix Error Billing CDR prefix Error Billing CDR prefix Error

Unanswered Question
Jan 8th, 2008

Thank you for your help.

i have this question, My AS5400 send CDR for my Billing System ... but the calls or CDR for incoming national calls (Mobile & Fix)to my network are coming without prefix for our local and national calls which is 00962, on other hand calls from my network to other local carriers include the prefix 00962...is it clear?

All other International calls include correct prefixes no problem.

Example:

Local Mobile= 0777223344

Local Fix= 064536543

my network= 063000000

Jordan Prefix= 962

Now call from o777223344 or 064536543

to 063000000 has the error where CDR at Billing system without 00962 it is only 063000000 it is not 96263000000 this take us that call comes from Phillipines Fix 63 and not from my network 63000000.

Remember calls from 063000000 to any destination is right prefix.

any help please at AS5400 or PGW2200??

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
scpage Tue, 01/08/2008 - 12:54

Hi,

Without knowing if you are using switched or nailed PGW config, I can say there are 2 solutions. One on the PGW

and one on the 5400. You can choose which solution fits you the best.

PGW Nailed solution:

Setup a bmoddig in a dialplan to prefix 962 to any number coming in starting with 63

Apply custgrpid to incoming ss7path.

#### creates the dialplan ####

numan-add:dialplan:custgrpid="lma3", OVERDEC="YES"

#### digits to prefix ####

numan-add:digmodstring:custgrpid="lma3",name="add962",digstring="962"

### result set for dialplan ####

numan-add:resultset:custgrpid="lma3",name="addpre"

#### modify the b number starting at the beginning and add the digits specified in digmodstring ####

numan-add:resulttable:custgrpid="lma3",name="addprefix",resulttype="BMODDIG",dw1="1",dw2="0",dw3="add962",setname="addpre"

#### Route based on B number starting with digits 63 ####

numan-add:bdigtree:custgrpid="lma3",callside="originating",digitstring="63",setname="addpre"

#### Apply custgrpid to incoming ss7path ####

prov-ed:sigsvcprop:name="ss7path",custgrpid="lma3"

### Deploy config ####

prov-dply

Restart of PGW software may be needed.

PGW switched solution:

Setup a bmoddig in a dialplan to prefix 962 to any number coming in starting with 63

Apply custgrpid to incoming ss7 trunkgrp.

#### creates the dialplan ####

numan-add:dialplan:custgrpid="lma3", OVERDEC="YES"

#### digits to prefix ####

numan-add:digmodstring:custgrpid="lma3",name="add962",digstring="962"

### result set for dialplan ####

numan-add:resultset:custgrpid="lma3",name="addpre"

#### modify the b number starting at the beginning and add the digits specified in digmodstring ####

numan-add:resulttable:custgrpid="lma3",name="addprefix",resulttype="BMODDIG",dw1="1",dw2="0",dw3="add962",setname="addpre"

#### Route based on B number starting with digits 63 ####

numan-add:bdigtree:custgrpid="lma3",callside="originating",digitstring="63",setname="addpre"

#### Apply custgrpid to incoming ss7 trunkgrp ####

prov-ed:trnkgrpprop:name="1000",custgrpid="lma3"

### Deploy config ####

prov-dply

Restart of PGW software may be needed.

NAS Solution:

Create a voice translation rule to prefix 962 to 63 number.

Apply to incoming pots voice port

voice translation-rule 1

rule 1 /\(^63\)/ /962\1/

!

!

voice translation-profile add962

translate called 1

!

!

voice-port 2:D

translation-profile incoming add962

Actions

This Discussion