Yea, you’re right. I also looked at other gateway reports (CDR>Gateway) and selected type incoming only, and was able to see the originally dialed number.
However, it still lists just the DN. I guess the workaround would be to look at the calling party field, if you happen to know the telemarketer’s CLID, and find the call that way.
Not sure why CDR doesn’t show the originally called party pre-translation. But it’s too bad.
Sorry I didn’t have better results. Good luck!
- J
From: Lelio Fulgenzi [mailto:lelio at uoguelph.ca]
Sent: Wednesday, November 21, 2012 9:54 AM
To: James Avalos
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] tracing translations easily
detailed gateway report does not show originally dialled number. :(
---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it.
- LFJ (with apologies to Mr. Popeil)
________________________________
From: "Lelio Fulgenzi" <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>
To: "James Avalos" <javalos at adobe.com<mailto:javalos at adobe.com>>
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Sent: Wednesday, November 21, 2012 12:48:56 PM
Subject: Re: [cisco-voip] tracing translations easily
the biggest thing is trying to figure out which DID a telemarketer called.
i'll try a detailed gateway report....
---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it.
- LFJ (with apologies to Mr. Popeil)
________________________________
From: "James Avalos" <javalos at adobe.com<mailto:javalos at adobe.com>>
To: "Lelio Fulgenzi" <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Sent: Wednesday, November 21, 2012 12:45:45 PM
Subject: RE: [cisco-voip] tracing translations easily
If you do a detailed gateway report in CDR, your DID’s should show up as the original called party. Then somewhere along the report, you’ll see the DN is the final called party. Not sure if I have the working correct, but I think it should break this down for you in a detailed gateway report.
What is the application? Are you trying to figure out the most dialed DID’s at a particular site? If so, this is where I would start.
Hope this helps…
- J
From: Lelio Fulgenzi [mailto:lelio at uoguelph.ca]
Sent: Wednesday, November 21, 2012 9:22 AM
To: James Avalos
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] tracing translations easily
Thanks James.
We are using MGCP with CallManager v7.
We take in all 10 digits from the carrier and use translations to send that to a DN. For example, 519-555-1234 to 56354. Everything works, it's just that there's no clear way to map a call record in CDR to a particular DID. There's a many to one relationship in some cases, especially with wild cards.
I'd rather not go into traces. Even then, I think I have to enable a parameter for 'complex' diagnostics so each translation is recorded as well.
---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it.
- LFJ (with apologies to Mr. Popeil)
________________________________
From: "James Avalos" <javalos at adobe.com<mailto:javalos at adobe.com>>
To: "Lelio Fulgenzi" <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>, cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Sent: Wednesday, November 21, 2012 12:02:27 PM
Subject: RE: [cisco-voip] tracing translations easily
If you’re using H323 as your gateway type, the DID is most likely translated to your DN before it hits call manager, not allowing you to see the dialed digit in CM traces or CDR.
If you’re using MGCP, you most likely have a translation pattern that will take the digits sent by the carrier and mask them into your DN range.
Or, your carrier may simply not be sending all 10 digits of your DID. If this is the case, I don’t think you can see the full incoming dialed DID. Some of our offices are configured to just have the last 4 or 5 digits of the DID sent in on the circuit.
Not sure if this is what you were looking for. I may have completely misunderstood the question… ☺
-J
From: cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Lelio Fulgenzi
Sent: Wednesday, November 21, 2012 6:54 AM
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: [cisco-voip] tracing translations easily
anyone come up with an easy way to trace translations? we get calls to extensions through DIDs, but I only see the extension in the CDR, not the DID. I'd like to know what DID was called (if any).
lelio
---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it.
- LFJ (with apologies to Mr. Popeil)
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20121121/237755da/attachment.html>