David,
After double checking, I do seem to be getting E.164 formatted numbers coming from the Cisco datasource, at least for the numbers we care about. Following is an example, you can see that I am able to successfully match a 1800 # as 1800, test (I just can't rate a price to it).
id,StartTime,Username,CallerParty,Destination,DestinationId,DestinationName,Duration,Price,Gateway,KBIn,KBOut,Disconnect,Channel,Direction,CallType
1,2008-08-05 08:55:28,,5635833713,2415453,,,0,,208.66.128.72-ISDN-7,0,0,0,Normal release,ISDN 7/2:D:2,outgoing,Telephony
2,2008-08-05 08:55:28,,5635833713,2415453,,,0,,208.66.128.72-ISDN-7,0,0,0,Normal release,ISDN 7/0:D:1,incoming,Telephony
3,2008-08-05 08:55:11,,6082516000,19206750230,,,0,,208.66.128.72-ISDN-7,0,0,0,Normal release,ISDN 7/1:D:22,outgoing,Telephony
4,2008-08-05 08:55:11,,6082516000,19206750230,,,0,,,0,0,0,Normal release,,incoming,VoIP
5,2008-08-05 08:54:37,,6082888583,18004266918,1800,test,0,,208.66.128.72-ISDN-7,0,0,0,Normal release,ISDN 7/1:D:18,outgoing,Telephony
On Fri, Aug 1, 2008 at 8:23 PM, David Villasmil
<david.villasmil.work@gmail.com> wrote:
correct
Okay, I'm using a Cisco datasource, so I'm assuming that would replace OpenSER in the general schema, correct?