[cisco-voip] missing trace information in trace files

[Ryan Ratliff]

It shows up on the node that process DA for the call.  If it's an  
inbound MGCP call then DA is processed on the node where the endpoint  
is registered.  If it's from a phone it gets processed on the node  
where the phone is registered.   You can have some funkiness with CTI  
devices where your CTI provider isn't the primary in the CTI device's  
CM group, but otherwise it's pretty straight forward.  I don't think  
it gets funky even with shared lines across nodes.

-Ryan

On Jun 13, 2007, at 5:11 PM, Lelio Fulgenzi wrote:

wow....why is it on the server the MGCP is registered to? I would  
have though it would have been on the one my phone is registered too.

------------------------------------------------------------------------ 
--------
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"Buffalo buffalo Buffalo buffalo buffalo buffalo Buffalo  
buffalo."      WJR
----- Original Message -----
From: Lelio Fulgenzi
To: Ryan Ratliff
Cc: cisco-voip at puck.nether.net
Sent: Wednesday, June 13, 2007 5:07 PM
Subject: Re: [cisco-voip] missing trace information in trace files

Yup - I'm looking on the server where my phone is registered for  
sure. Checked it again. And again during this message. ;)

Do you think that summary will appear on the subscriber on which the  
MGCP gateways are registered? I'll check there.....

------------------------------------------------------------------------ 
--------
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"Buffalo buffalo Buffalo buffalo buffalo buffalo Buffalo  
buffalo."      WJR
----- Original Message -----
From: Ryan Ratliff
To: Lelio Fulgenzi
Cc: cisco-voip at puck.nether.net
Sent: Wednesday, June 13, 2007 5:04 PM
Subject: Re: [cisco-voip] missing trace information in trace files

Are you sure you're looking at the server where the phones are
registered?   That tracing comes from DA (digit analysis) and that
will only occur where the device is registered.   If you only see it
for incoming calls it sounds like your MGCP gateway(s) are not
registered to the same server your phones are.

-Ryan

On Jun 13, 2007, at 4:57 PM, Lelio Fulgenzi wrote:

This is really wierd since I don't even see the PSS in some calls any
more.


------------------------------------------------------------------------
--------
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"Buffalo buffalo Buffalo buffalo buffalo buffalo Buffalo
buffalo."      WJR
----- Original Message -----
From: Lelio Fulgenzi
To: cisco-voip at puck.nether.net
Sent: Wednesday, June 13, 2007 4:36 PM
Subject: [cisco-voip] missing trace information in trace files

I used to be able to see a nice summary in the trace files which
showed which route pattern a call hit. I don't seem to be getting
that information anymore. Something like this. But now it's only for
incoming calls.
|CallingPartyNumber=38003
|DialingPartition=UoGSysDN_G31_PT
|DialingPattern=37023
|FullyQualifiedCalledPartyNumber=37023
|DialingRoutePatternRegularExpression=(37023)
|DialingWhere=
|PatternType=Enterprise
|PotentialMatches=NoPotentialMatchesExist
|DialingSdlProcessId=(0,0,0)
|PretransformDigitString=37023
|PretransformTagsList=SUBSCRIBER
|PretransformPositionalMatchList=37023
|CollectedDigits=37023
|UnconsumedDigits=
|TagsList=SUBSCRIBER
|PositionalMatchList=37023
|VoiceMailbox=
|VoiceMailCallingSearchSpace=
|VoiceMailCallingSearchSpace=
|VoiceMailPilotNumber=
|AlertingName=
|RouteBlockFlag=RouteThisPattern
|RouteBlockCause=0
|InterceptPartition=UoGSysDN_G31_PT
|InterceptPattern=37023
|InterceptWhere=
|InterceptSdlProcessId=(9,35,1)
|InterceptSsType=150994948
|InterceptSsKey=565
|OverlapSendingFlagEnabled=0
|WithTags=

Anyone have any ideas? Did a recent upgrade change this? Grrrr.

I have detailed traces set on the active subscriber of my phone. I
have all settings checked except:
Enable H245 Message Trace
Enable All GateWay Trace
Enable SIP Stack Trace
Enable SIP Call Processing Trace
Enable Keep Alive Trace
Device Name Based Trace Monitoring
------------------------------------------------------------------------
--------
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"Buffalo buffalo Buffalo buffalo buffalo buffalo Buffalo
buffalo."      WJR


_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip