Yes, thats why..thanks for your help

Another question. On show call history voice last, on the peer address field, is it always the dialed digits or it could be the ANI? based on my experience its always the called number, but somehow using an call center application the number that appears on peer address is the ANI so did not match in my pots dial-peer.

show call history voice last

MNLA-C3660-2503-250.49#lastcall

GENERIC:

SetupTime=61555814 ms

Index=7874

PeerAddress=12345

PeerSubAddress=

PeerId=0

PeerIfIndex=0

LogicalIfIndex=0

DisconnectCause=10

DisconnectText=normal call clearing (16)

ConnectTime=0 ms

DisconnectTime=61571404 ms

CallDuration=00:00:00 sec

CallOrigin=2

ReleaseSource=2

ChargedUnits=0

InfoType=speech

TransmitPackets=0

TransmitBytes=0

ReceivePackets=0

ReceiveBytes=0

VOIP:

ConnectionId[0xC824E56B 0x2AA9021F 0x2DFC85DA 0xBE801A7]

IncomingConnectionId[0xC824E56B 0x2AA9021F 0x2DFC85DA 0xBE801A7]

RemoteIPAddress=64.192.251.11

RemoteUDPPort=55706

RemoteSignallingIPAddress=64.192.251.11

RemoteSignallingPort=58714

RemoteMediaIPAddress=64.192.251.11

RemoteMediaPort=55706

RoundTripDelay=0 ms

SelectedQoS=best-effort

tx_DtmfRelay=inband-voice

FastConnect=FALSE

AnnexE=FALSE

Separate H245 Connection=FALSE

H245 Tunneling=FALSE

SessionProtocol=cisco

ProtocolCallId=

SessionTarget=

OnTimeRvPlayout=0

GapFillWithSilence=0 ms

GapFillWithPrediction=0 ms

GapFillWithInterpolation=0 ms

GapFillWithRedundancy=0 ms

HiWaterPlayoutDelay=0 ms

LoWaterPlayoutDelay=0 ms

PlayoutMode = undefined

PlayoutInitialDelay=0 ms

ReceiveDelay=0 ms

LostPackets=0

EarlyPackets=0

LatePackets=0

VAD = enabled

CoderTypeRate=g729r8 pre-ietf

CodecBytes=0

cvVoIPCallHistoryIcpif=-1

MediaSetting=flow-around

CallerName=telwise

CallerIDBlocked=False

OriginalCallingNumber=12345

OriginalCallingOctet=0x21

OriginalCalledNumber=25036326314224

OriginalCalledOctet=0xA1

OriginalRedirectCalledNumber=

OriginalRedirectCalledOctet=0xFF

TranslatedCallingNumber=12345

TranslatedCallingOctet=0x21

TranslatedCalledNumber=25036326314224

TranslatedCalledOctet=0xA1

TranslatedRedirectCalledNumber=

TranslatedRedirectCalledOctet=0xFF

GwReceivedCalledNumber=25036326314224

GwReceivedCalledOctet3=0xA1

GwReceivedCallingNumber=12345

GwReceivedCallingOctet3=0xA1

GwReceivedCallingOctet3a=0x0

Username=

Dial-Peer:

dial-peer voice 300 pots

description CCA

destination-pattern 2503632T

port 2/0/1

I'm getting confused here i have not experience this before. I hope you could help me with these also. Thanks.

Hello,

In show call history voice last, you have too look at CallOrigin, 1=answer, 2= originate.

For answer, will be called number, for originate will be calling.

Note that one call normally generates two entries!

Now, with DP 300 should work as long the called number begins with 2503632, on what conditions do you find that does not match ?

Apparently, the Peer ID field is set to 0 instead of the dial peer ID of 300. I assume that the call did not match on dial peer 300. All my dial peer is 100% working on my other VoIP Application. Im having a difficult time troubleshooting with Call Center Anywhere. May be you have an idea about CCA in regards to cisco gateways

Hello,

I generally do not care about "peer id". What you want to do, is "debug voice dialpeer" to see what is matching. What is your architecture? From where the call is coming in, and to where is supposed to go out?

Here is the screen shot from debug dialpeer

Inside dpMatchCore:

Jun 23 18:34:03.184: destination pattn: 25036326314224 expanded string: 25036326314224

Jun 23 18:34:03.184: Inside dpMatchCore:

Jun 23 18:34:03.184: destination pattn: 12345 expanded string: 12345

Jun 23 18:34:03.184: Inside dpMatchCore:

Jun 23 18:34:03.184: destination pattn: 12345 expanded string: 12345

Jun 23 18:34:03.184: dpAssociateIncomingPeer_T null source route label

Jun 23 18:34:03.188: Inside dpMatchCore:

Jun 23 18:34:03.188: destination pattn: 25036326314224 expanded string: 25036326314224

Jun 23 18:34:03.188: Inside dpMatchCore:

Jun 23 18:34:03.188: destination pattn: 12345 expanded string: 12345

Jun 23 18:34:03.188: Inside dpMatchCore:

Jun 23 18:34:03.188: destination pattn: 12345 expanded string: 12345

Jun 23 18:34:03.188: dpAssociateIncomingPeer_T null source route label

Jun 23 18:34:03.188: Inside dpMatchCore:

Jun 23 18:34:03.188: destination pattn: 25036326314224 expanded string: 25036326314224

Jun 23 18:34:03.188: Inside dpMatchCore:

Jun 23 18:34:03.188: destination pattn: 12345 expanded string: 12345

Jun 23 18:34:03.188: Inside dpMatchCore:

Jun 23 18:34:03.188: destination pattn: 12345 expanded string: 12345

Jun 23 18:34:03.188: dpAssociateIncomingPeer_T null source route label

Jun 23 18:34:03.188: Inside dpMatchPeersMoreArg

Jun 23 18:34:03.188: dpMatchPeersMoreArg: Match Dest. pattern; called (25036326314224)

Jun 23 18:34:03.188: Inside dpMatchCore:

Jun 23 18:34:03.188: destination pattn: 25036326314224 expanded string: 25036326314224

Jun 23 18:34:03.188: MatchNextPeer: Peer 300 matched partially

Jun 23 18:34:03.188: dpMatchPeersMoreArg: Result=1 after MATCH_ORIGINATE

Jun 23 18:34:36.577: Inside dpMatchCore:

Jun 23 18:34:36.577: destination pattn: expanded string:

Jun 23 18:34:36.577: Inside dpMatchCore:

Jun 23 18:34:36.577: destination pattn: Unknown expanded string: Unknown

Jun 23 18:34:36.577: Inside dpMatchCore:

Jun 23 18:34:36.577: destination pattn: Unknown expanded string: Unknown

Jun 23 18:34:36.577: dpAssociateIncomingPeer_T null source route label

Basically, the call flow would be CCA Telephony Server -> Voice Master -> Cisco Gateway.

Hello,

What matters to the GW are just the numbers. I assume the call comes in via VOIP and should go out via PRI. Now, if the called number has constant lenght, you would have a better match under DP 300 with:

destination-pattern 2503632........ <-- matches this prefix followed by 7 digits

and will dial the 7 digits via PRI. Is that ok ?