We have a setup where one of the E1s is connected to a SIP<-->E1 Gateway. And other E1s are connected to PSTN.

This allows our SIP clients to send external calls to PSTN as the COT configured for this "gateway" E1 is configured with TIE.

The problem we are having is regarding CDR. We expect that the CDR for this kind of call shows the calling party (SIP Extension) as the chargee.
But currently CDR is showing as chargee number 69000 which is coming from AMO TLZO.

This is the actual TLZO configuration:
ADD-TLZO:INC,                 69000;
ADD-TLZO:INT,                 69000;
ADD-TLZO:OUTG,                 69000;

We are trying to find out how to have CDR showing the information we expect. Anyone can help with this issue?

Display-SELS;     and see which Select Group(s) are active - usually only 1.

Display-SELG:X;   where "X" is the number of the active Select Group(s) from above.

In the SELG output, look for the parameter "FORMBAS", and see which form table is being used for your Base CDR output.

Last, REGEN-FTBL:Z;    where "Z" is the Form Table from above.

Post the results of the REGEN-FTBL here.  I may be able to give you an alternative solution.

Good luck.
 

Iamnothere,

I have FORM01 for Outgoing and FORM02 for Incoming. Here are the REGEN result for both:

  <REGENERATE-FTBL:1;
REGENERATE-FTBL:1;
H500:  AMO FTBL  STARTED
ADD-FTBL:1,B,FORM,1,N,"#@#@#@#@#@#@#@#@#@#@@@@@@@@@@@#@@@@@#@@@@@@@@@#@@@";
ADD-FTBL:1,B,FORM,2,N,"@@@@@@@@@@@@@@@@@@#@@@#@@@@@@@@@@@#@@#@@@#@@#@@#@#";
ADD-FTBL:1,B,FORM,3,N,"@#@@@#@@@@@@@";
ADD-FTBL:1,B,CTRL,4,N,LF;
ADD-FTBL:1,B,CTRL,5,Y,CR;
ADD-FTBL:1,B,FIELD,1,STHOUR,CHAR,"0",R;
ADD-FTBL:1,B,FIELD,2,STMIN,CHAR,"0",R;
ADD-FTBL:1,B,FIELD,3,STSEC,CHAR,"0",R;
ADD-FTBL:1,B,FIELD,4,STDAY,CHAR,"0",R;
ADD-FTBL:1,B,FIELD,5,STMONTH,CHAR,"0",R;
ADD-FTBL:1,B,FIELD,6,STYEAR,CHAR,"0",R;
ADD-FTBL:1,B,FIELD,7,CONHOUR,CHAR,"0",R;
ADD-FTBL:1,B,FIELD,8,CONMIN,CHAR,"0",R;
ADD-FTBL:1,B,FIELD,9,CONSEC,CHAR,"0",R;
ADD-FTBL:1,B,FIELD,10,CHRGEE,CHAR," ",R;
ADD-FTBL:1,B,FIELD,11,TKNOLIST,CHAR," ",R;
ADD-FTBL:1,B,FIELD,12,ROUTCN,CHAR," ",L;
ADD-FTBL:1,B,FIELD,13,CALLEPTY,CHAR," ",L;
ADD-FTBL:1,B,FIELD,14,CHRGUNIT,CHAR," ",R;
ADD-FTBL:1,B,FIELD,15,PIN,CHAR," ",L;
ADD-FTBL:1,B,FIELD,16,SERVICE,CHAR," ",L;
ADD-FTBL:1,B,FIELD,17,PPLV0,CHAR," ",L;
ADD-FTBL:1,B,FIELD,18,RINGDUR,CHAR," ",L;
ADD-FTBL:1,B,FIELD,19,CAUSE,CHAR," ",L;
ADD-FTBL:1,B,FIELD,20,SUPLSERV,CHAR,"0",R;
ADD-FTBL:1,B,FIELD,21,CONNTYPE,CHAR," ",L;
ADD-FTBL:1,B,FIELD,22,GLOBLV0,CHAR," ",L;
ADD-FTBL:1,B,FIELD,23,GLOBSEQ,CHAR," ",L;

AMO-FTBL -111       SMDR/DMDR TABLE FORMATS                                     
REGENERATE COMPLETED;
  <REGENERATE-FTBL:2;
REGENERATE-FTBL:2;
H500:  AMO FTBL  STARTED
ADD-FTBL:2,B,FORM,1,N,"#@#@#@#@#@#@#@#@#@#@@@@@@@@@@@#@@@@@#@@@@@@@@@#@@@";
ADD-FTBL:2,B,FORM,2,N,"@@@@@@@@@@@@@@@@@@#@@@#@@@@@@@@@@@#@@#@@@#@@#@@#@#";
ADD-FTBL:2,B,FORM,3,N,"@#@@@#@@@@@@@";
ADD-FTBL:2,B,CTRL,4,N,LF;
ADD-FTBL:2,B,CTRL,5,Y,CR;
ADD-FTBL:2,B,FIELD,1,STHOUR,CHAR,"0",R;
ADD-FTBL:2,B,FIELD,2,STMIN,CHAR,"0",R;
ADD-FTBL:2,B,FIELD,3,STSEC,CHAR,"0",R;
ADD-FTBL:2,B,FIELD,4,STDAY,CHAR,"0",R;
ADD-FTBL:2,B,FIELD,5,STMONTH,CHAR,"0",R;
ADD-FTBL:2,B,FIELD,6,STYEAR,CHAR,"0",R;
ADD-FTBL:2,B,FIELD,7,CONHOUR,CHAR,"0",R;
ADD-FTBL:2,B,FIELD,8,CONMIN,CHAR,"0",R;
ADD-FTBL:2,B,FIELD,9,CONSEC,CHAR,"0",R;
ADD-FTBL:2,B,FIELD,10,CHRGEE,CHAR," ",R;
ADD-FTBL:2,B,FIELD,11,TKNOLIST,CHAR," ",R;
ADD-FTBL:2,B,FIELD,12,ROUTCN,CHAR," ",L;
ADD-FTBL:2,B,FIELD,13,DESTPTY,CHAR," ",L;
ADD-FTBL:2,B,FIELD,14,CHRGUNIT,CHAR," ",R;
ADD-FTBL:2,B,FIELD,15,PIN,CHAR," ",L;
ADD-FTBL:2,B,FIELD,16,SERVICE,CHAR," ",L;
ADD-FTBL:2,B,FIELD,17,PPLV0,CHAR," ",L;
ADD-FTBL:2,B,FIELD,18,RINGDUR,CHAR," ",L;
ADD-FTBL:2,B,FIELD,19,CAUSE,CHAR," ",L;
ADD-FTBL:2,B,FIELD,20,SUPLSERV,CHAR,"0",R;
ADD-FTBL:2,B,FIELD,21,CONNTYPE,CHAR," ",L;
ADD-FTBL:2,B,FIELD,22,GLOBLV0,CHAR," ",L;
ADD-FTBL:2,B,FIELD,23,GLOBSEQ,CHAR," ",L;

AMO-FTBL -111       SMDR/DMDR TABLE FORMATS                                     
REGENERATE COMPLETED;

Try working on Form Table 1 first.  I suggest that you change Field 10 from "CHRGEE" (Paying Party) to "CALLIPTY" (Calling Party).  I am not certain whether this will resolve the issue, but it's worth a try.
But, you cannot change a Form Table after it has been added via AMO; therefore, perform a REG-FTBL:1;  and copy all of the AMOs, then Paste them into a Notepad file.  Save it to your local PC as "FTBL_1_original.txt".  Now do a "Save As", and save the same file as "FTBL_1_modified.txt", and let's work with the "modified" file.
Using Notepad, change the "modified" file for this line:
ADD-FTBL:1,B,FIELD,10,CHRGEE,CHAR," ",R;

    ....change "CHRGEE" to "CALLIPTY"

Do not make any other changes.

To implement this new version of Form Table 1, you must either delete Form Table 1 in the HiPath 4000, then add the "modified" FTBL as the "new" Form Table 1, OR you can create a new Form Table, such as number "11".  I recommend adding a new Form Table "11".  

Using Notepad, change the "modified" file to reflect the new Form Table number "11" (or whichever number you prefer to use) in EACH line:

ADD-FTBL:11,B,FORM,1,N,"#@#@#@#@#@#@#@#@#@#@@@@@@@@@@@#@@@@@#@@@@@@@@@#@@@";
ADD-FTBL:11,B,FORM,2,N,"@@@@@@@@@@@@@@@@@@#@@@#@@@@@@@@@@@#@@#@@@#@@#@@#@#";
ADD-FTBL:11,B,FORM,3,N,"@#@@@#@@@@@@@";
ADD-FTBL:11,B,CTRL,4,N,LF;
ADD-FTBL:11,B,CTRL,5,Y,CR;
ADD-FTBL:11,B,FIELD,1,STHOUR,CHAR,"0",R;
ADD-FTBL:11,B,FIELD,2,STMIN,CHAR,"0",R;
ADD-FTBL:11,B,FIELD,3,STSEC,CHAR,"0",R;
ADD-FTBL:11,B,FIELD,4,STDAY,CHAR,"0",R;
ADD-FTBL:11,B,FIELD,5,STMONTH,CHAR,"0",R;
ADD-FTBL:11,B,FIELD,6,STYEAR,CHAR,"0",R;
ADD-FTBL:11,B,FIELD,7,CONHOUR,CHAR,"0",R;
ADD-FTBL:11,B,FIELD,8,CONMIN,CHAR,"0",R;
ADD-FTBL:11,B,FIELD,9,CONSEC,CHAR,"0",R;
ADD-FTBL:11,B,FIELD,10,CALLIPTY,CHAR," ",R;
ADD-FTBL:11,B,FIELD,11,TKNOLIST,CHAR," ",R;
ADD-FTBL:11,B,FIELD,12,ROUTCN,CHAR," ",L;
ADD-FTBL:11,B,FIELD,13,CALLEPTY,CHAR," ",L;
ADD-FTBL:11,B,FIELD,14,CHRGUNIT,CHAR," ",R;
ADD-FTBL:11,B,FIELD,15,PIN,CHAR," ",L;
ADD-FTBL:11,B,FIELD,16,SERVICE,CHAR," ",L;
ADD-FTBL:11,B,FIELD,17,PPLV0,CHAR," ",L;
ADD-FTBL:11,B,FIELD,18,RINGDUR,CHAR," ",L;
ADD-FTBL:11,B,FIELD,19,CAUSE,CHAR," ",L;
ADD-FTBL:11,B,FIELD,20,SUPLSERV,CHAR,"0",R;
ADD-FTBL:11,B,FIELD,21,CONNTYPE,CHAR," ",L;
ADD-FTBL:11,B,FIELD,22,GLOBLV0,CHAR," ",L;
ADD-FTBL:11,B,FIELD,23,GLOBSEQ,CHAR," ",L;

You can actually use Copy & Paste from here.  Copy this entire new Form Table, and use the ComWin feature "Execute Clipboard - AMO by AMO" to implement this new Form Table 11.

After it adds successfully, perform REG-FTBL:11; just to ensure that it looks good.

To activate and test this new Form Table, in the correct Select Group, use CHA-SELG to change the parameter "FORMBAS" to "11".

Place some test calls and see if the correct calling party is now shown.

Please post the results.

Good luck!

Iamnothere,

It works this way. (Changing Field 10 from "CHRGEE" (Paying Party) to "CALLIPTY" (Calling Party)).

Do you think this can broke something else?

Not likely, since you stated that this form table is used for Outgoing records only.  Never attempt to change CDR fields without knowing what you are doing.  The format of the CDR record is established by all of the "#" and "@" characters in the first few lines of the AMO FTBL commands.  The field that we changed is field 10, which is shown below (if the Tek-Tips website properly aligns the characters!!):

ADD-FTBL:11,B,FORM,1,N,"#@#@#@#@#@#@#@#@#@#@@@@@@@@@@@...
                                          ^^^^^^^^^^^^
Field 10 consists of twelve characters. Your station numbers are restricted to a max of 6 characters, unless you are using Virtual numbering (VNR).  The max length of a VNR station number is twelve characters - so field 10's length SHOULD be OK.  There COULD be an issue if there is a transit call, where a PUBLIC call tandems thru your system on its way to another "node".  In that case, the incoming ANI number may be displayed in your field 10 as being the Calling Party.  If the public number exceeds twelve characters, then you would lose some of that data.  However, this is rare. IF THERE IS A PROBLEM WITH THE FIELD 10, you can shorten it or lengthen it by deleting or adding  "@" characters.  But you should create a new form table to accomplish this, as we did above, because you cannot change an existing form table.
 
If there are problems, then immediately switch your SELG back to the original Form Table "1".  Then post here with the problem.  I usually check this site a few times a week.

Good luck!!!!

You can add a few more characters to field 10     

The Tek-Tips website's format did not align the characters in my last post.  Field 10 is represented by the following characters:

#@@@@@@@@@@@

Please ignore all of the "^" characters in the previous post, as they are out of place!