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

Gateway T1 Controller Configuration for fxs-loop-start

We have a customer who has 2 T1 that are being frought in via a T1 and state that once it's brought in they are setup for pots lines. We configured the T1 with many different type but cannot get a call in or out. Our dail-peer staements seem correct but I believe the issue is with the type setting on the Controller. Here's what we have setup with on the controller T1 card, what happens is when a call is placed it shows ringing when I do a show voice port summ but the other end never hears it ringing. I have never worked on a T1 that was setup this way. Here's the configuration we have for the gateway:

controller T1 0/0/1

framing sf

linecode ami

ds0-group 1 timeslots 1-24 type fxs-loop-start

!

interface Loopback0

ip address 172.16.xxx.x 255.255.255.255

h323-gateway voip interface

h323-gateway voip bind srcaddr 172.16.xxx.x

!

dial-peer voice 5 pots

destination-pattern 1[2-9]..[2-9]......

incoming called-number .

direct-inward-dial

port 0/0/1:1

forward-digits 11

!

3 REPLIES
New Member

Re: Gateway T1 Controller Configuration for fxs-loop-start

You might want to include your destination dial peer on the VOIP side. You will also want to troubleshoot with "debug voip/voice ccapi inout" / and "debug isdnq931" to verify call failure/delivery. You can also test calling out sourced from the router with " csim start"

New Member

Re: Gateway T1 Controller Configuration for fxs-loop-start

I'm sorry I didn't post the VOIP peer, but it's in there:

dial-peer voice 2004 voip

destination-pattern 1...

session target ipv4:172.16.83.21

incoming called-number .

dtmf-relay h245-alphanumeric

no vad

!

You say to do debug isdn q931, but it's not an isdn circuit so this will not work. I was wondering if anyone has ran into this type of circuit before.

New Member

Re: Gateway T1 Controller Configuration for fxs-loop-start

Sorry about that. This is a CAS T1 circuit and troubleshooting is more like analog FXS?FXO. I am listing a snip from a similar back 2 back link I have to a PBX. Rather than q931 you will want to "debug vpm signal" in conjuction with previously mentioned cmds. You will want to check the listed URL which I have found very useful. I would also verify obvious stuff like routing to the loopback interface that you are using as source.... Hope it helps. -Adam

http://cisco.com/en/US/customer/tech/tk652/tk653/technologies_troubleshooting_procedures09186a00801040bc.shtml

controller T1 1/0

framing esf

linecode b8zs

cablelength short 133

ds0-group 1 timeslots 1-6 type e&m-wink-start dtmf dnis

!

!

voice-port 1/0:1

!

dial-peer voice 991600 pots

destination-pattern 16..

progress_ind alert enable 8

incoming called-number .

no digit-strip

direct-inward-dial

port 1/0:1

!

dial-peer voice 995600 pots

destination-pattern 56..

progress_ind alert enable 8

incoming called-number .

no digit-strip

direct-inward-dial

port 1/0:1

!

dial-peer voice 1000 voip

destination-pattern ....

voice-class codec 10

session target ipv4:10.10.3.11

dtmf-relay h245-alphanumeric

!

PTA-1760# sh voice call summary

PORT CODEC VAD VTSP STATE VPM STATE

============== ======== === ==================== ======================

1/0:1.1 - - - EM_ONHOOK

1/0:1.2 - - - EM_ONHOOK

1/0:1.3 - - - EM_ONHOOK

1/0:1.4 - - - EM_ONHOOK

1/0:1.5 - - - EM_ONHOOK

1/0:1.6 - - - EM_ONHOOK

263
Views
0
Helpful
3
Replies
CreatePlease to create content