Transit calls calling number display in Omnivista.

Post Reply
User avatar
pavel
Member
Posts: 18
Joined: 13 Jul 2010 06:11

Transit calls calling number display in Omnivista.

Post by pavel »

Hello,

My question is somewhat similar to the one is this topic viewtopic.php?f=274&t=11728, but I still have some lack of understanding. I have an OXE with a lot of transit traffic and a customer whants to have Omnivista records about this calls. Although I have records collected and displayed in Omnivista but there is a meaninig of FSxxx (where xxx is the an in coming trunk group numer) in the "Extension" field. The custmer whants to see an original calling number somwhere in this rescord. Is there anything what can be done to realise that ?

Btw, the transit call ticker looks like:

----[/DHS3dyn/account/TAXARZGF.DAT : Ticket number 5/5/6]----------------------
(00) TicketVersion = ED5.2 (01) CalledNumber = 6789
(02) ChargedNumber = FS022 (03) ChargedUserName = ISDN
(04) ChargedCostCenter = (05) ChargedCompany =
(06) ChargedPartyNode = 1 (07) Subaddress =
(08) CallingNumber = (09) CallType = Unspecified
(10) CostType = ISDNCircuitSwitchedCall (11) EndDateTime = 20060112 14:12:29
(12) ChargeUnits = 0 (13) CostInfo = 0
(14) Duration = 0 (15) TrunkIdentity = 0
(16) TrunkGroupIdentity = 2 (17) TrunkNode = 1
(18) PersonalOrBusiness = Normal (19) AccessCode =
(20) SpecificChargeInfo = (21) BearerCapability = 3Audio
(22) HighLevelComp = Unspecified (23) DataVolume = 0
(24) UserToUserVolume = 0
(25) ExternFacilities = CallingLineIdentificationPresentation
(26) InternFacilities = Transit CentralAbbreviatedNumbering
(27) CallReference = 0 (28) SegmentsRate1 = 0
(29) SegmentsRate2 = 0 (30) SegmentsRate3 = 0
(31) ComType = Voice (32) X25IncomingFlowRate = Unspecified
(33) X25OutgoingFlowRate = Unspecified (34) Carrier = 0
(35) InitialDialledNumber = (36) WaitingDuration = 0
(37) EffectiveCallDuration = 0 (38) RedirectedCallIndicator = 0
(39) StartDateTime = 20060112 14:12:29 (40) ActingExtensionNumber =
(41) CalledNumberNode = 9999 (42) CallingNumberNode = 9999
(43) InitialDialledNumberNode = 9999 (44) ActingExtensionNumberNode = 9999
(45) TransitTrunkGroupIdentity = 32767 (46) NodeTimeOffset = 0
(47) TimeDlt = 0


As you can see the field "(08) CallingNumber = " is empty which confuses me a bit. As I understand Omnivista uses this ticket's information to display call records. So I guess I need to have a some calling number here at first ?

I don't know whether this affects CN or not but External Callback Translator DEF is configured.

Thanks for your attention.

Regards,
Pavel.
onetwo
Member
Posts: 17
Joined: 24 Apr 2013 02:36

Re: Transit calls calling number display in Omnivista.

Post by onetwo »

Hi Pavel,
Did you find number in "callingnumber" field yet? I have this problem in my system and can not see Calling Number.
User avatar
tgn
Member
Posts: 802
Joined: 30 Dec 2009 17:59
Location: Germany

Re: Transit calls calling number display in Omnivista.

Post by tgn »

i think the field no. (02) ChargedNumber will contain the external number (if transmitted by caller) when then setting in trunkgroup for "charge calling and adn creation" is "true".

regards...
--- back to basics... focus your eyes to the essential things... ---
onetwo
Member
Posts: 17
Joined: 24 Apr 2013 02:36

Re: Transit calls calling number display in Omnivista.

Post by onetwo »

Hi everybody,
My customer have too many unknow external calls . They have asked us to find relevant number (to charge). No DISA license on this system. Transit calls with transfer, forward, conference i can see calling number field. Hope to help.

(00) TicketVersion = ED5.2 (01) CalledNumber = 0021872342362
(02) ChargedNumber = FS028 (03) ChargedUserName =
(04) ChargedCostCenter = (05) ChargedCompany =
(06) ChargedPartyNode = 1 (07) Subaddress =
(08) CallingNumber = (09) CallType = Unspecified
(10) CostType = ISDNCircuitSwitchedCall (11) EndDateTime = 20140106 09:43:00
(12) ChargeUnits = 0 (13) CostInfo = 0
(14) Duration = 25 (15) TrunkIdentity = 26
(16) TrunkGroupIdentity = 1 (17) TrunkNode = 1
(18) PersonalOrBusiness = Normal (19) AccessCode =
(20) SpecificChargeInfo = (21) BearerCapability = Speech
(22) HighLevelComp = Telephony (23) DataVolume = 0
(24) UserToUserVolume = 0
(25) ExternFacilities = CallingLineIdentificationPresentation
(26) InternFacilities = Transit (27) CallReference = 243
(28) SegmentsRate1 = 0 (29) SegmentsRate2 = 0
(30) SegmentsRate3 = 0 (31) ComType = Voice
(32) X25IncomingFlowRate = Unspecified (33) X25OutgoingFlowRate = Unspecified
(34) Carrier = 0 (35) InitialDialledNumber =
(36) WaitingDuration = 0 (37) EffectiveCallDuration = 0
(38) RedirectedCallIndicator = 0 (39) StartDateTime = 20140106 09:42:35
(40) ActingExtensionNumber = (41) CalledNumberNode = 9999
User avatar
joao.carlos
Member
Posts: 213
Joined: 11 Feb 2010 12:05
Location: Brasil

Re: Transit calls calling number display in Omnivista.

Post by joao.carlos »

Do you have SIP trunk?

What is your TG 28?
---
joao.carlos
ACSE OXE R12 | ACSE OpenTouch R2 | ACSE OXO Connect R2 | ACSE OmniVista 8770 R3 | ACFE OmniSwitch R6/R7/R8 | ACSE OTCS R8.2
ACPS IP Telephony R12 | ACPS OpenTouch R2 | ACPS Data Networks R6/R7 | ACPS OTCS R8.2
haroun
Senior Member
Posts: 1355
Joined: 29 Mar 2010 11:09

Re: Transit calls calling number display in Omnivista.

Post by haroun »

@tgn i validate this parameter in trunkgroup but oxe doesn't accept it specially for T2 trunkgroup ? how did you do it? :lol:
haroun
Senior Member
Posts: 1355
Joined: 29 Mar 2010 11:09

Re: Transit calls calling number display in Omnivista.

Post by haroun »

haroun wrote:@tgn i validate this parameter in trunkgroup but oxe doesn't accept it specially for T2 trunkgroup ? how did you do it? :lol:
i see where is my mistake , from doc the T2 trunkgroup should be QSIG
onetwo
Member
Posts: 17
Joined: 24 Apr 2013 02:36

Re: Transit calls calling number display in Omnivista.

Post by onetwo »

Many thanks to everybody!
Mr Jao Carlos, Yes, My system has 2xT2 (TG 1), 60 analog line (TG 2) and local SIP trunk (TG 28) for SIP extension (Audio Code MP11x, with 200 SIP extension licences).
More help to me!
User avatar
joao.carlos
Member
Posts: 213
Joined: 11 Feb 2010 12:05
Location: Brasil

Re: Transit calls calling number display in Omnivista.

Post by joao.carlos »

Well when CChargedNUmbernis the tg number (FS28), it generally means anonymous calls.

Go to SIP>>Sip Proxy and put Minimal Authentication Method to Digest since it's probablybset to None and someone could be hacking at your system.
---
joao.carlos
ACSE OXE R12 | ACSE OpenTouch R2 | ACSE OXO Connect R2 | ACSE OmniVista 8770 R3 | ACFE OmniSwitch R6/R7/R8 | ACSE OTCS R8.2
ACPS IP Telephony R12 | ACPS OpenTouch R2 | ACPS Data Networks R6/R7 | ACPS OTCS R8.2
onetwo
Member
Posts: 17
Joined: 24 Apr 2013 02:36

Re: Transit calls calling number display in Omnivista.

Post by onetwo »

Yes, i changed these parameter in sip proxy 10 days ago and is monitoring them. So we can not find calling number field in this case. It's difficult to explain to client. One more thanks to Mr Jaoo and everyboy!
Post Reply

Return to “OmniVista 4760”