VoipDetailsView shows some records where ToPhone and FromPhone values are the same. Lync 2013 Server

I'm seeing numerous records in  the LCSCDR  VoipDetailsView where the ToPhone and FromPhone values are the same. Can anyone explain why this would occur. The following is an example from that table. I've modified the values to ensure the privacy of the data.


SessionIdTime         : 9/10/2015 4:16:20 PM
SessionIdSeq          : 1
InviteTime            : 9/10/2015 4:16:20 PM
FromUri               : m.goff@somewhere.com
ToUri                 : 1630xxxxxxx;phone-context=defaultprofile@somewhere.com
FromUriType           : UserUri
ToUriType             : PhoneUri
FromTenant            : 00000000-0000-0000-0000-000000000000
ToTenant              : 00000000-0000-0000-0000-000000000000
FromEndpointId        : 7a317144-cb38-52fc-b207-c1386a36f84e
ToEndpointId          : fb2434da-564e-56b6-bed0-6e3ce531621a
EndTime               : 9/10/2015 4:16:36 PM
FromMessageCount      : 0
ToMessageCount        : 0
FromClientVersion     : UCCAPI/15.0.4745.1000 OC/15.0.4745.1000 (Microsoft Lync)
FromClientType        : 4
FromClientCategory    : OC
ToClientVersion       : RTCC/5.0.0.0 MediationServer
ToClientType          : 1
ToClientCategory      : MediationServer
TargetUri             : +1415xxxxxxx@somewhere.com
TargetUriType         : PhoneUri
TargetTenant          : 00000000-0000-0000-0000-000000000000
OnBehalfOfUri         : 
OnBehalfOfUriType     : 
OnBehalfOfTenant      : 
ReferredByUri         : 
ReferredByUriType     : 
ReferredByTenant      : 
DialogId              : 7597398c-4115-4bde-8c0f-01004de185ed;c45eba4c35;b226213573
CorrelationId         : 
ReplacesDialogIdTime  : 
ReplacesDialogIdSeq   : 
ReplacesDialogId      : 
ResponseTime          : 9/10/2015 4:16:30 PM
ResponseCode          : 200
DiagnosticId          : 51004
ContentType           : application/sdp
FrontEnd              : fe01.somewhere.local
Pool                  : FEPOOL01.somewhere.local
FromEdgeServer        : usatlarklyedpool01.somewhere.local
ToEdgeServer          : lyedpool01.somewhere.local
IsFromInternal        : False
IsToInternal          : True
CallPriority          : Normal
MediaTypes            : 16
FromUserFlag          : 0
ToUserFlag            : 0
CallFlag              : 0
Location              : 
FromPhone             : 1630xxxxxxx
ToPhone               : 1630xxxxxxx
DisconnectedByUri     : m.goff@somewhere.com
DisconnectedByUriType : UserUri
DisconnectedByTenant  : 00000000-0000-0000-0000-000000000000
DisconnectedByPhone   : 
FromMediationServer   : MED02.somewhere.local
ToMediationServer     : 
FromGateway           : xxx.xx.xx.xxx
ToGateway             : 

In this case the TargetUri is the DID phone number assigned to  the Lync User in the FromUri field. As first glance this appears to be an outbound PSTN call, but there is no value in ToGateway and FromGateway has a value. This typically indicates an inbound call. I don't understand why the ToPhone and FromPhone values would be the same in this case.

Any advice is appreciated.

September 10th, 2015 2:47pm

Hi,

Did the issue happen for all calls or just for several calls?

When a Lync user call a number, Lync Server will check if the number match E.164 format, if yes, then Lync will perform a Reverse Number lookup. If not, Lync will normalize it to E.164 format and then perform a Reverse Number Lookup.

So please check if the normalization rule set correctly on Lync Server Control Panel--Voice Route--Dial Plan.

Best Regards

Free Windows Admin Tool Kit Click here and download it now
September 10th, 2015 10:17pm

The issues appears on several calls, not all calls. I'm not sure I understand how the normalization rules would cause the FromPhone and the ToPhone values to be the same  in the VoipDetailsView?

The normalization rules for this user's dial plan are:

Description         :
Pattern             : ^(911)$
Translation         : $1
Name                : Colombia-Emergency
IsInternalExtension : False

Description         :
Pattern             : ^(1\d{2})$
Translation         : $1
Name                : Colombia-Services
IsInternalExtension : False

Description         :
Pattern             : ^([2-8]\d{6})$
Translation         : +571$1
Name                : Colombia-Bogota-local
IsInternalExtension : False

Description         :
Pattern             : ^(033\d{9})$
Translation         : +57$1
Name                : Colombia-Mobile
IsInternalExtension : False

Description         :
Pattern             : ^0(1800\d{7})$
Translation         : +57$1
Name                : Colombia-Toll Free
IsInternalExtension : False

Description         :
Pattern             : ^0([124-8][2-8]\d{6})\d*(\D+\d+)?$
Translation         : +57$1
Name                : Colombia-National
IsInternalExtension : False

Description         :
Pattern             : ^(?:00)((1[2-9]\d\d[2-9]\d{6})|([2-9]\d{6,14}))(\D+\d+)?$
Translation         : +$1
Name                : Colombia-International
IsInternalExtension : False

September 11th, 2015 12:27pm