07-01-2007 08:18 AM
Can someone tell me what is the purpose of Peer Address field on show call history voice last 1. Or any link that explains this. My problem is that i created a 2 scenarios, 1. terminating on e1 or t1 trunk and 2. fxo trunk. I am using a Call Center Application. My topology is CCA -> VM -> Cisco Gateways. On the first scenario, Terminating on t1 trunk the peer address field indicates the called number while on e1 and fxo indicatees calling number. And it turned out when terminating to t1 trunks the call is working fine. but on e1 and fxo were not, so i am confused on comparing and isolating those scenarios.
07-01-2007 11:41 AM
Hello,
as I told you previously, for each call two entries are generated. You need to look at both of them and the parameter calltype to understand what is calling and what is called.
07-02-2007 11:06 AM
I use the debug cch323 on my cisco 3660 (with FXO Port), from CCA i called 6314224 routed into VM for billing then to the cisco 3660's FXO port going to PSTN line.
MNLA-C3660-2503-250.49#
Jul 2 18:35:31.606: cch323_ct_main: SOCK 0 Event 0x1
Jul 2 18:35:31.606: cch323_get_new_ccb: ccb (0x64DE3F78) is in use
Jul 2 18:35:31.606: cch323_ct_main: SOCK 2 Event 0x1
Jul 2 18:35:31.606: [1]towner_data=0x6460A230, len=261, msgPtr=0x644EF558
cch323_gw_process_read_socket: received msg for H.225
Jul 2 18:35:31.606: cch323_h225_receiver: received msg of type SETUPIND_CHOSEN
Jul 2 18:35:31.606: cch323_h225_receiver CCB existing from TCP accepted
Jul 2 18:35:31.606: cch323_h225_receiver Got a new CCB for crv 57774
Jul 2 18:35:31.610: setup_ind
Jul 2 18:35:31.610: setup_ind: callingNumber[12345] calledNumber[25036326314224]
Jul 2 18:35:31.610: setup_ind---- calling IE present
Jul 2 18:35:31.610: ======= PI in setup_ind = 0
Jul 2 18:35:31.610: Receive: infoXCap 0
Jul 2 18:35:31.610: Receive infoXCap ccb 0
Jul 2 18:35:31.610: cch323_extract_signaled_carriers
Jul 2 18:35:31.610: No Source IP group match with Src CarrierId/Zone ID
Jul 2 18:35:31.610: No Source IP group matched with rte id/zone_id/acl.
Jul 2 18:35:31.610: cch323_determine_source_group
Jul 2 18:35:31.610: No Source IP group match with Incoming Called Number.
Jul 2 18:35:31.610: cch323_determine_source_group
Jul 2 18:35:31.610: No Source IP group match with Destination pattern.
Jul 2 18:35:31.610: setup_ind: is_overlap = 1, info_complete = 0
cch323_is_preauth_reqd is FALSE
Jul 2 18:35:31.610: src address = 64.192.248.6 of SETUPIND_CHOSEN
Jul 2 18:35:31.610: dest address = 64.192.251.11 of SETUPIND_CHOSEN
Also can you help me, the call already reached the cisco and it supposed to go to the pstn and match the pots dial peer, since the FXO is connected to PSTN Line. but i found out that the call was again trying to route going back to my VM.
GENERIC:
SetupTime=931047814 ms
Index=10134
PeerAddress=12345
PeerSubAddress=
PeerId=0
PeerIfIndex=0
LogicalIfIndex=0
DisconnectCause=10
DisconnectText=normal call clearing (16)
ConnectTime=0 ms
DisconnectTime=931063394 ms
CallDuration=00:00:00 sec
CallOrigin=2
ReleaseSource=2
ChargedUnits=0
InfoType=speech
TransmitPackets=0
TransmitBytes=0
ReceivePackets=0
ReceiveBytes=0
VOIP:
ConnectionId[0x65B70891 0x37C0051F 0x3E8D4253 0x90898EAF]
IncomingConnectionId[0x65B70891 0x37C0051F 0x3E8D4253 0x90898EAF]
RemoteIPAddress=64.192.251.11 => VM's IP
RemoteUDPPort=50022
RemoteSignallingIPAddress=64.192.251.11
RemoteSignallingPort=38566
RemoteMediaIPAddress=64.192.251.11
RemoteMediaPort=50022
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=25036329314224
OriginalCalledOctet=0xA1
OriginalRedirectCalledNumber=
OriginalRedirectCalledOctet=0xFF
TranslatedCallingNumber=12345
TranslatedCallingOctet=0x21
TranslatedCalledNumber=25036329314224
TranslatedCalledOctet=0xA1
TranslatedRedirectCalledNumber=
TranslatedRedirectCalledOctet=0xFF
GwReceivedCalledNumber=25036329314224
GwReceivedCalledOctet3=0xA1
GwReceivedCallingNumber=12345
GwReceivedCallingOctet3=0xA1
GwReceivedCallingOctet3a=0x0
Username=
07-02-2007 02:03 PM
Ok, so the call gets to router from voip/h323 and is supposed to go out via FXO.
Can I see the dial-peer again, and show voice port ? Is the called number fixed lenght, or variable ? Do you want to send out such a long number to telco, or just a part of it ?
If the DP insists in not matching, what would be useful to see is "debug voip dialpeer".
07-03-2007 12:57 PM
Yes, it should send out long number because the 026314224 (called number) it must route to our PBX.
Here is my config.
On FXO:
voice-port 2/0/0
no battery-reversal
echo-cancel coverage 32
cptone PH
connection plar 026345991
description GTCTI
!
voice-port 2/0/1
no battery-reversal
echo-cancel coverage 32
cptone PH
connection plar 026386223
description GTCTI
!
voice-port 2/1/0
no battery-reversal
echo-cancel coverage 32
cptone PH
connection plar 026386210
description Zhapa
!
voice-port 2/1/1
no battery-reversal
echo-cancel coverage 32
cptone PH
connection plar 026386220
description Zhapa
!
voice-port 3/0/0
no battery-reversal
echo-cancel coverage 32
cptone PH
connection plar 5000
description Velotech
!
voice-port 3/0/1
no battery-reversal
echo-cancel coverage 32
cptone PH
connection plar 026314224
description GACI
!
voice-port 3/1/0
no battery-reversal
echo-cancel coverage 32
cptone PH
connection plar 026347120
description ThinkVoIP
!
voice-port 3/1/1
no battery-reversal
echo-cancel coverage 32
cptone PH
connection plar 026347120
description ThinkVoIP
!
voice-port 5/0/0
!
voice-port 5/0/1
no battery-reversal
echo-cancel coverage 32
cptone PH
connection plar 029143921
description TO CCA-TLPHNY
On Dial Peer:
dial-peer voice 300 pots
description Office_Outbound
destination-pattern 2503632T
port 2/0/1
!
dial-peer voice 301 pots
description Office_Outbound
destination-pattern 2503632T
port 2/1/1
!
dial-peer voice 302 pots
description Office_Outbound
destination-pattern 2503632T
port 2/1/0
!
dial-peer voice 303 pots
description Office_Outbound
destination-pattern 5000632T
port 2/0/1
!
dial-peer voice 304 pots
description Velotech
destination-pattern 2503632T
port 3/0/0
!
dial-peer voice 305 pots
description GACI
preference 10
destination-pattern 2503632T
port 3/0/1
!
dial-peer voice 306 pots
description ThinkVoIP
destination-pattern 2503632T
port 3/1/0
!
dial-peer voice 307 pots
description TO CCA-TLPHNY
destination-pattern 2503632T
port 5/0/1
!
dial-peer voice 206 voip
description GACI
huntstop
destination-pattern 026314224
progress_ind setup enable 3
voice-class codec 1
session protocol sipv2
session target ipv4:64.192.254.57
dtmf-relay rtp-nte h245-signal h245-alphanumeric
no vad
On debug dialpeer:
MNLA-C3660-2503-250.49#debug dialpeer
dialpeer detailed info debugging is on
MNLA-C3660-2503-250.49#term mon
MNLA-C3660-2503-250.49#
Jul 3 20:55:30.031: Inside dpMatchCore:
Jul 3 20:55:30.031: destination pattn: 25036326314224 expanded string: 25036326314224
Jul 3 20:55:30.031: Inside dpMatchCore:
Jul 3 20:55:30.031: destination pattn: 12345 expanded string: 12345
Jul 3 20:55:30.031: Inside dpMatchCore:
Jul 3 20:55:30.031: destination pattn: 12345 expanded string: 12345
Jul 3 20:55:30.031: dpAssociateIncomingPeer_T null source route label
07-03-2007 01:21 PM
Hello,
you have no DP pots with a destination-pattern of 026314224, hence the call will never go out via an FXO port.
Hope this helps, please rate post if it does!
07-03-2007 01:37 PM
One the Voice Master, I have a prefix of 2503632 before routing it to cisco.
07-03-2007 02:26 PM
Hi,
I don't know what a voice master is and how it fits on you scenario and what prefix are you talking about.
What I can tell you for sure, is that in the router that you sent the configuration, when a call comes in with called number 026314224, it will go nowhere because there is no matching dial-peer. Just as the debug before was demonstrating.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: