cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
556
Views
0
Helpful
4
Replies

FXO Port (Long Distance Issues)

Jason Amick
Level 1
Level 1

I am having issues with one of our sites that is setup with a cisco 2921 that has 4 POTS lines in a hunt connected to FXO ports on the gateway.  Local calls complete fine but when dialing long distance I get the message "we're sorry your call cannot be completed as dialed".  I have looked and am matching the correct incoming and outgoing dial peers.  I have several other sites setup in the same fashion without any LD issues.  I would normally think this issue would be with the carrier but I can successfully complete a long distance call directly from the gateway via the CSIM start command.  An example of the outgoing dial peer is below.  I have tested with both the forward-digits 11 and no digit strip command and LD is still unsuccessful.  I have also attached a call log with several debugs enabled.  Any suggestions??

 

dial-peer voice 93 pots
 description Local Outbound Dialing
 preference 7
 destination-pattern 9.T
 progress_ind progress enable 8
 progress_ind connect enable 8
 port 1/0/11

 

rtr-haw-231#show dial-peer voice 93
VoiceEncapPeer93
        peer type = voice, system default peer = FALSE, information type = voice,
        description = `Local Outbound Dialing',
        tag = 93, destination-pattern = `9.T',
        voice reg type = 0, corresponding tag = 0,
        allow watch = FALSE
        answer-address = `', preference=7,
        CLID Restriction = None
        CLID Network Number = `'
        CLID Second Number sent
        CLID Override RDNIS = disabled,
        rtp-ssrc mux = system
        source carrier-id = `', target carrier-id = `',
        source trunk-group-label = `',  target trunk-group-label = `',
        numbering Type = `unknown'
        group = 93, Admin state is up, Operation state is up,
        Outbound state is up,
        incoming called-number = `',
connections/maximum = 0/unlimited,
        DTMF Relay = disabled,
        URI classes:
            Destination =
        Destination route-string = None
        huntstop = disabled,
        in bound application associated: 'DEFAULT'
        out bound application associated: ''
        dnis-map =
        permission :both
        incoming COR list:maximum capability
        outgoing COR list:minimum requirement
        Translation profile (Incoming):
        Translation profile (Outgoing):
        incoming call blocking:
        translation-profile = `'
        disconnect-cause = `no-service'
        advertise 0x40 capacity_update_timer 25 addrFamily 4 oldAddrFamily 4
        mailbox selection policy: none
        type = pots, prefix = `',
        forward-digits default
        session-target = `', voice-port = `1/0/11',
        direct-inward-dial = disabled,
        digit_strip = enabled,
        register E.164 number with H323 GK and/or SIP Registrar = TRUE
        fax rate = system,   payload size =  20 bytes
        supported-language = ''
        preemption level = `routine'
        bandwidth:
            maximum = 64 KBits/sec, minimum = 64 KBits/sec
        voice class called-number:
            inbound = `', outbound = `'
        dial tone generation after remote onhook = enabled
        mobility=0, snr=, snr_noan=, snr_delay=0, snr_timeout=0
        snr calling-number local=disabled, snr ring-stop=disabled, snr answer-too-soon timer=0
        Time elapsed since last clearing of voice call statistics never
        Connect Time = 102355, Charged Units = 0,
        Successful Calls = 58, Failed Calls = 0, Incomplete Calls = 0
        Accepted Calls = 0, Refused Calls = 0,
        Last Disconnect Cause is "10  ",
        Last Disconnect Text is "normal call clearing (16)",
        Last Setup Time = 47290722.
        Last Disconnect Time = 47292069.

4 Replies 4

Jason Amick
Level 1
Level 1

Call Logs

Nothing relevant really in those logs. I do see a cut through which is for the announcement that you hear -
Apr 11 19:14:21: htsp_process_event: [1/0/11, FXOLS_OFFHOOK, E_HTSP_VOICE_CUT_THROUGH]fxols_proc_voice

Post which the IP Phone drops the calls and call is terminated.

Take the following for a test call please -

debug voip vtsp all
debug vpm signal
debug voice ccapi inout

Are you sure your Telco is not expecting a 9 as well with LD calls ?

Nipun:

 

Thanks for the response, I have completed a test call to recreate the message.  Attached is the debugs you requested.  I have am not sure if the carrier is expecting the 9 but I will find out.  We have several sites setup the same way with us stripping the 9 before sending the call and it works fine and with different carriers.  Please let me know if you see anything in the logs.  Thanks!!

I don't see the IOS sending a 1 which is strange. The call is being made as a local call rather than LD -

Apr 12 11:34:37: //172/xxxxxxxxxxxx/VTSP:(1/0/11):-1:1:1/ds_do_dial:
Digits To Dial=15408941690
Apr 12 11:34:38: //172/xxxxxxxxxxxx/VTSP:(1/0/11):-1:1:1/vtsp_dsm_digit_begin_cb:
Apr 12 11:34:38: //172/xxxxxxxxxxxx/VTSP:(1/0/11):-1:1:1/vtsp_dsm_digit_begin_cb:
Begin Digit=5

It might be a message drop but it would be very strange for the IOS to do this for one specific line in the logs.

Can you create another dial-peer with the destination-pattern of "91[2-9]..[2-9]......" and see if it helps ?