Re: [sipX-dev] Query regarding CDR - Jasper Reports

Wed, 26 Aug 2009 05:32:26 -0700

Hi Chris ,

I tried a "true" Tandem call (a branch office user calls PSTN number using head office gateway) , but still it doesn't work.

Steps followed :
1. In branch office created a dial plan which directs calls (4 followed by any number) to head office.
2. In head office configured bridge - which directs calls (91 followed by 10 digits) to respective user

3. Dialed 491 followed by mobile number (9972832539) , and established call between 700 (branch office user) and mobile .

Result : Call Direction page does not show Tandem calls category . In branch office call is listed as outgoing call and in head office listed as incoming call.

Also tried another scenario using two gateways (sipXbridge and mediant)

1. Configured both sipXbridge and mediant on machine
2. For SCS user 387 gave call forward to number as mobile no (9845186164).
3. Made inbound call to 387 using bridge and without intervention call is forwarded to mobile number through the mediant  gateway.

Still I am getting same result (Tandem category is not seen in Call direction page). Calls are listed as incoming and outgoing calls.

Please advise whether to raise a Jira issue for this or is there any other configuration setup is to be done ?

Thank you ,
Navven


Chris Parfitt wrote:

Naveen have you tried a “true” tandem call, I mean one that has no user intervention, so an incoming gateway call then just routes straight back out on another Gateway as per the dial plan?

 

From: [email protected] [mailto:[email protected]] On Behalf Of Naveen Krishna
Sent: 25 August 2009 10:54
To: Raymond Dans
Cc: [email protected]
Subject: Re: [sipX-dev] Query regarding CDR - Jasper Reports

 

Raymond Dans wrote:

Naveen wrote:

 

 > Subject: [sipX-dev] Query regarding CDR - Jasper Reports
 > Per the new improvement in CDR couple of new dropdown reports namely  Call Direction and Long Distance have been added into Reports page (Diagnostic - Call Detail 

 Records - Reports) .
 > 
 > When we select Call Direction option and click on the HTML link next to Refresh button , call direction page opens with a new window. This page is filters out the calls in three  sections .
 > 
 > 1. Incoming Calls
 > 2. Internal Calls
 > 3. Outgoing Calls
 > 
 > As per my knowledge Incoming calls section should contain call came to the SUT from other SUT , or from PSTN (gateway phone). In general all the calls coming into the SCS box.
 > Internal Calls section should contain all the calls made within that SUT (normal , hunt group , ACD , paging , Intercom , conference ... etc.) ie, amoung SCS users.
 > Outgoing Calls section should contain calls made from the SUT to other SUT , or to PSTN number (gateway phone).Calls going out of SCS box.
 > 
 > But the following deviation is seen: 
 > 
 >     Scenario : Dialed no to                                                Call direction page display
 > 1. Normal calls         ----------------------------------           Internal calls
 > 2. Hunt group within SUT -----------------------------           Internal calls
 > 3. Intercom within SUT     -----------------------------           Internal calls
 > 4. Conference within SUT -----------------------------           Outgoing calls
 > 5. ACD within the SUT     -----------------------------           Outgoing calls
 > 6. Paging within SUT         -----------------------------           Both in Incoming and Outgoing calls (attached screenshot)
 > 7. Voicemail (101) and AA (100) ------------------------              Internal calls
 > 8. PSTN inbound and call from other SUT ------------            Incoming calls 
 > 8. PSTN outbound and to other SUT -----------------            Outgoing calls
 > 
 > Hence IMHO when we dial conference extension , ACD extension , Paging  within the SUT the calls should be listed as internal calls in the Call Direction page . 
 > 
 > Please advise whether to raise Jira issue for this.
 > 
 > Thank you ,
 > Naveen
 

Yes, please raise a Jira issue for this.  Conference, ACD calls and Paging from an internal user should be classified as Internal.  There may be a flaw in how the Call Direction is being calculated by the Reporting or it may be a flaw in the CDR record.

 

BTW.  There is another category of call that can be reported in the Call Direction report.  The type is "Tandem" and occurs when an external incoming call is "passing through" the system.  Also note, that categories which have no calls will not be shown in the report.  For example, if no Internal calls were made during the time period of the report, the Internal category will not be shown.

 

Raymond

Hi Raymond ,

Thank you for the reply . I raised Jira issue XX-6384 for above the scenarios (ACD , Paging & Conference calls).

Today I tried hairpin transfer scenario to find out the 4th category "Tandem" . Steps followed as below ,

1.Dialed 384 (SCS user) from PSTN phone (08041315953)
2.Answer the call from SCS user (384) , and from 384 do a blind transfer to another PSTN number (9845186164).
3.PSNT phone (9845186164) starts ringing and 384 got disconnected.
4.Answer the call from PSTN phone (9845186164) , now call established between two PSTN phones .
5.Hangup the call.

After this navigated to Call Direction page , but not found "Tandem" category . Transfered call is listed under "Incoming calls" and completed calls are listed under "Outgoing calls" (screenshot attached - tandem1.png & tandem2.png).

Categories which have no calls are not shown in the report , and works as expected. When there is no calls in any of the category a null table displayed (I think this also works as expected - attached screenshot - null.png).

Please advise whether to raise a Jira issue for this also .

Thank you ,
Naveen 


_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to