Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

T1 e&m - 2 way problems. Post in wrong forum Sorry

Hi

I am having problems with a T1 circuit (ESF, B8ZS and E&M Winkstart) and CallManager 4.2.

controller T1 1/0

framing esf

linecode b8zs

ds0-group 0 timeslots 1-24 type e&m-wink-start

!

This is terminating on a 2621XM with a NM-HDV.

I can successfully make inbound and outbound calls depending on having the port line in on the pots dial-peer.

If I have the port line in on the pots dial-peer, I can make outbound calls but inbound calls fail. On debug of voice vtdp inout I see there is no Called number. Debug attached.

voice-port 1/0:0

translate called 1

bearer-cap Speech

!

!

!

!

dial-peer voice 9 pots

tone ringback alert-no-PI

destination-pattern 9.T

progress_ind setup enable 3

progress_ind alert enable 8

progress_ind progress enable 8

progress_ind connect enable 8

progress_ind disconnect enable 8

fax rate disable

direct-inward-dial

forward-digits 11

port 1/0:0

If I take out the port line from the pots dial-peer inbound calls work and the deb shows the called number. But obviously the outbound doesn't work.

I dont know if the call is failing before it sends the DNIS or DNIS is the problem I dont know enough about e&m.

voice-port 1/0:0

translate called 1

bearer-cap Speech

!

!

!

!

dial-peer voice 9 pots

tone ringback alert-no-PI

destination-pattern 9.T

progress_ind setup enable 3

progress_ind alert enable 8

progress_ind progress enable 8

progress_ind connect enable 8

progress_ind disconnect enable 8

fax rate disable

direct-inward-dial

forward-digits 11

This is the voip dial-peer

dial-peer voice 101 voip

preference 1

destination-pattern 23T

progress_ind setup enable 3

modem passthrough nse codec g711ulaw

voice-class codec 1

session target ipv4:10.3.1.14

incoming called-number .

dtmf-relay h245-alphanumeric

fax rate disable

no vad

An ideas greatly appreciated.

deb vpm....

*Jun 11 09:45:14.498: htsp_dsp_message: SEND/RESP_SIG_STATUS: state=0xC timestam

p=23669 systime=13390097

*Jun 11 09:45:14.498: htsp_process_event: [1/0:0(1), EM_ONHOOK, E_DSP_SIG_1100]e

m_onhook_offhook htsp_setup_ind

*Jun 11 09:45:14.502: [1/0:0(1)] get_local_station_id calling num= calling name=

calling time=06/11 09:45 orig called=

*Jun 11 09:45:14.502: TGRM: reg_invoke_tgrm_accept_call(1, TGRM_CALL_VOICE, TGRM

_DIRECTION_IN, 1, 0, 0, 0)

*Jun 11 09:45:14.502: TGRM: Calling vtsp_tsp_call_setup_ind().

*Jun 11 09:45:14.502: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

Calling Number=, Called Number=, Voice-Interface=0x840BFDFC,

Timeout=TRUE, Peer Encap Type=ENCAP_VOICE, Peer Search Type=PEER_TYPE_VOICE,

Peer Info Type=DIALPEER_INFO_SPEECH

*Jun 11 09:45:14.502: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

Match Rule=DP_MATCH_PORT;

*Jun 11 09:45:14.502: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

Result=Success(0) after DP_MATCH_PORT; Incoming Dial-peer=9

*Jun 11 09:45:14.506: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerSPI:exit@5831

*Jun 11 09:45:14.506: TGRM: reg_invoke_tgrm_call_update(1, 0, 0, 0, 1, TGRM_CALL

_BUSY, TGRM_CALL_VOICE, TGRM_DIRECTION_IN)

*Jun 11 09:45:14.506: htsp_timer - 3000 msec

*Jun 11 09:45:14.506: //-1/xxxxxxxxxxxx/VTSP:(1/0:0):-1:-1:-1/vtsp_allocate_cdb:

CDB=0x843DBFA0

*Jun 11 09:45:14.506: //-1/xxxxxxxxxxxx/VTSP:(1/0:0):-1:-1:-1/vtsp_do_call_setup

_ind:

Event=E_TSP_SETUP_IND

Progress Indication=3, CarrierIDCode=, Info Trans Capability=128, Source Carr

ier ID=, tg_label_flag=0

*Jun 11 09:45:14.510: //-1/3C6720068410/VTSP:(1/0:0):-1:-1:-1/vtsp_timer:

Timer Start Time=13390098, Timer Value=180000(ms)

1 REPLY
Anonymous
N/A

Re: T1 e&m - 2 way problems. Post in wrong forum Sorry

gateway attempts to match the called number of the call setup request with the configured incoming called-number of each dial peer. Because call setups always include DNIS information, it is recommended to use the incoming called-number command for inbound dial peer matching

http://www.cisco.com/en/US/tech/tk652/tk90/technologies_tech_note09186a008010fed1.shtml

138
Views
0
Helpful
1
Replies
CreatePlease login to create content