[cisco-voip] FXO Outbound Call Not Working

Mon Jun 14 14:05:55 EDT 2010

The next step would be like I said, try out each line disconnected from
router FXO port with a old POTS / princess phone and see if the phone lines
work, or use a Butt Sett on them like Dennis suggested.

The 0x00 is indication of router voice-port seeing no voltage on the line
plugged into that port (maybe there is nothing plugged into the port, or it
got disconnected somewhere upstream). This command however gives you more of
a warm fuzzy then anything. With analog lines, there is no real good way
from router command line to really tell what is going on with the actual
phone lines. The no circuit on the call history means the router attempted
to make a call but didn't detect a phone line / dial tone on that port to do
so.

But, most likely a telephone provider / phone line cabling issue since this
used to work fine with no changes on your gateway.

On Mon, Jun 14, 2010 at 10:07 AM, Kim, Hyoun S <Hyoun.Kim at chartercom.com>wrote:

>  I’m having a local IT guy from down there to try it.  I can’t because I’m
> over 300 miles away.
>
>
>
> In the event that phone calls cannot be made outbound, what needs to be
> done given the e-mail I wrote out below?
>
>
>
> *Hyoun Kim*
>
> Network Administrator
>
> Charter Media - East Division
>
> 640 Broadmor Blvd, Suite 80
>
> Murfreesboro, TN 37129
>
>
>
> Email: Hyoun.Kim at chartercom.com
>
> Office: 615.217.6245
>
> Fax: 615.217.6247
>
>
>
> *From:* Dennis Heim [mailto:Dennis.Heim at cdw.com]
> *Sent:* Monday, June 14, 2010 9:07 AM
> *To:* Kim, Hyoun S; Erick B.; ccieid1ot
>
> *Cc:* cisco-voip at puck.nether.net
> *Subject:* RE: [cisco-voip] FXO Outbound Call Not Working
>
>
>
> If you connect your butt-set to these lines do they work?
>
>
>
> Dennis Heim
> Network Voice Engineer
> CDW  Advanced Technology Services
> 11711 N. Meridian Street, Suite 225
> Carmel, IN  46032
>
> 317.569.4255 Office
> 317.569.4201 Fax
> 317.694.6070 Cell
>
> dennis.heim at cdw.com
> cdw.com/content/solutions/unified-communications/<http://www.cdw.com/content/solutions/unified-communications/>
>
>
>
>
>
> *From:* cisco-voip-bounces at puck.nether.net [mailto:
> cisco-voip-bounces at puck.nether.net] *On Behalf Of *Kim, Hyoun S
> *Sent:* Monday, June 14, 2010 9:53 AM
> *To:* Erick B.; ccieid1ot
> *Cc:* cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] FXO Outbound Call Not Working
>
>
>
> Oh sorry Erick.
>
>
>
> The hardware is a C2811 with 3 VIC2-4FXO cards utilizing 12 analog phone
> lines from the telco (AT&T).  I have 2 DSP modules (PVDM2-16 & 64) installed
> with a NM-CUE module installed as well.
>
>
>
> All of the lines exhibit the same problem where people can dial to the
> office and the phone rings.  But outbound calls by that office do not work
> and display that same error I showed in the first e-mail.  I attempted to
> use the groundstart command on my voice ports per CCIEID1OT’s
> recommendation, but that didn’t work either.
>
>
>
> Thanks for that call command.  Here is the output for outbound calls… I see
> the “no circuit 34” you mentioned!
>
> 15B7 : 347 246488340ms.346 +-1 +1260 pid:6 Originate 16152176245
>
>  dur 00:00:00 tx:0/0 rx:0/0 22  (no circuit (34))
>
>  Telephony 0/0/0 (347) [0/0/0] tx:0/0/0ms None noise:0dBm acom:0dBm
>
>   long duration call detected:n long dur callduration :n/a timestamp:n/a
>
>
>
> Also, here are the results from the test voice command you gave me:
>
> 005578: Jun 14 08:50:42.880 CDT:
>
> Values read from SiLabs Codec connected to DSP 0, channel 8:
>
> --------------------------------------------------------------
>
> Register 29 = 0xD5
>
>
>
> I noticed the Register 29 comes out with different values for different
> ports.  Such as 0x00, 0xD5 & 0xD4.
>
>
>
> What are your recommendations since I get the “no circuit 34”?  The only
> thread I saw in regards to my initial error on Cisco’s support forums is
> this: https://supportforums.cisco.com/message/3118805#3118805
>
>
>
> However, the user ended up saying that the Telco was at fault and that’s
> how he got it fixed.  I just wanted to make sure all my hardware was ok
> before tell AT&T because in the past, they always tell me to check my
> equipment first.
>
>
>
> Thanks so much.
>
>
>
> *Hyoun Kim*
>
> Network Administrator
>
> Charter Media - East Division
>
> 640 Broadmor Blvd, Suite 80
>
> Murfreesboro, TN 37129
>
>
>
> Email: Hyoun.Kim at chartercom.com
>
> Office: 615.217.6245
>
> Fax: 615.217.6247
>
>
>
> *From:* Erick B. [mailto:erickbee at gmail.com]
> *Sent:* Friday, June 11, 2010 11:51 PM
> *To:* ccieid1ot
> *Cc:* Kim, Hyoun S; cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] FXO Outbound Call Not Working
>
>
>
> I would start by making sure each of the analog lines worked fine, with a
> regular old princess phone, if possible. Since it was working fine, and
> config hasn't changed, it's likely an issue with the phone lines or cabling.
>
>
>
> You don't mention what type of hardware you have, but try reseating the
> cables, especially if you have a amphenol connector. Those tend to vibrate
> loose over time and cause problems like this, where calls fail but some work
> depending on what port is being used.
>
>
>
> Output from 'show call history voice brief' may be useful. If the
> cause/reason states no circuit 34 then the line may be a problem.
>
>
>
> If you have a ISR router, you can try this, but it varies with voice-card
> hardware, a 0x0 result indicates the router see's no voltage on whatever is
> attached to the voice-port.
>
>
>
> term mon
>
> test voice port x/y/z si-reg-read 29 1
>
>
>
> Where x/y/z is your voice-port #/#/#, you need term mon to see the output
> from the test command.
>
>
>
>
>
> On Fri, Jun 11, 2010 at 3:27 PM, ccieid1ot <ccieid1ot at gmail.com> wrote:
>
> Try changing to ground-start.
>
> On Fri, Jun 11, 2010 at 2:43 PM, Kim, Hyoun S <Hyoun.Kim at chartercom.com>
> wrote:
>
>   I have a router that I’ve utilizes FXO modules for making calls.  When I
> first set it up, everything worked fine.  A few months later, users started
> reporting to me an intermittent problem for outbound calls.  Sometimes they
> can make calls, but the majority of the time, they get a fast busy signal.
> I compared the current router’s configuration to when I originally saved the
> configuration from initial setup.  Nothing changed.  Out of perhaps 10 calls
> made, maybe 1 of them went through.
>
>
>
> The following is the config for a voice-port.  All the other ones have the
> same config.  2857 is the number to the Unity Express.
>
> voice-port 0/0/0
>
>  trunk-group POTS-FXO
>
>  connection plar opx 2857
>
> caller-id enable
>
>
>
> I did try “no supervisory disconnect signal” but that didn’t work either.
>
>
>
> I turned on debugging for “vpm signal” and made several calls to different
> phone numbers.  The following output is just an example of what the result
> is for all calls:
>
> 001401: Jun 11 14:36:33.104 CDT: htsp_digit_ready(50/0/10.1): digit = 1
>
> 001402: Jun 11 14:36:33.500 CDT: htsp_digit_ready(50/0/10.1): digit = 6
>
> 001403: Jun 11 14:36:33.832 CDT: htsp_digit_ready(50/0/10.1): digit = 1
>
> 001404: Jun 11 14:36:34.124 CDT: htsp_digit_ready(50/0/10.1): digit = 5
>
> 001405: Jun 11 14:36:34.548 CDT: htsp_digit_ready(50/0/10.1): digit = 2
>
> 001406: Jun 11 14:36:34.816 CDT: htsp_digit_ready(50/0/10.1): digit = 1
>
> 001407: Jun 11 14:36:35.204 CDT: htsp_digit_ready(50/0/10.1): digit = 7
>
> 001408: Jun 11 14:36:35.636 CDT: htsp_digit_ready(50/0/10.1): digit = 6
>
> 001409: Jun 11 14:36:35.904 CDT: htsp_digit_ready(50/0/10.1): digit = 3
>
> 001410: Jun 11 14:36:36.308 CDT: htsp_digit_ready(50/0/10.1): digit = 0
>
> 001411: Jun 11 14:36:36.576 CDT: htsp_digit_ready(50/0/10.1): digit = 0
>
> 001412: Jun 11 14:36:36.588 CDT: htsp_timer_stop3
>
> 001413: Jun 11 14:36:36.588 CDT: htsp_process_event: [50/0/10.1,
> EFXS_OFFHOOK, E_HTSP_PROCEEDING]efxs_offhook_proceeding
>
> 001414: Jun 11 14:36:36.588 CDT: [50/0/10.1] set signal state = 0x8
> timestamp = 0htsp_setup_req
>
> 001415: Jun 11 14:36:36.592 CDT: htsp_process_event: [0/0/0, FXOLS_ONHOOK,
> E_HTSP_SETUP_REQ]fxols_onhook_setup
>
> 001416: Jun 11 14:36:36.592 CDT: [0/0/0] set signal state = 0xC timestamp =
> 0
>
> 001417: Jun 11 14:36:36.592 CDT: htsp_timer - 1300 msec
>
> 001418: Jun 11 14:36:36.844 CDT: htsp_process_event: [0/0/0,
> FXOLS_WAIT_DIAL_TONE, E_DSP_SIG_1100]fxols_power_denial_detected
>
> 001419: Jun 11 14:36:36.844 CDT: htsp_timer2 - 1000 msec
>
> 001420: Jun 11 14:36:36.844 CDT: htsp_timer_stop
>
> 001421: Jun 11 14:36:37.844 CDT: htsp_process_event: [0/0/0,
> FXOLS_WAIT_DIAL_TONE, E_HTSP_EVENT_TIMER2]fxols_power_den_disc
>
> 001422: Jun 11 14:36:37.844 CDT: htsp_timer_stop
>
> 001423: Jun 11 14:36:37.844 CDT: htsp_timer_stop2
>
> 001424: Jun 11 14:36:37.844 CDT: [0/0/0] set signal state = 0x4 timestamp =
> 0
>
> 001425: Jun 11 14:36:37.848 CDT: htsp_process_event: [0/0/0, FXOLS_ONHOOK,
> E_HTSP_RELEASE_REQ]fxols_onhook_release
>
> 001426: Jun 11 14:36:54.497 CDT: htsp_process_event: [50/0/10.1,
> EFXS_OFFHOOK, E_DSP_SIG_0100]efxs_offhook_onhook
>
> 001427: Jun 11 14:36:54.497 CDT: htsp_timer - 10 msec
>
> 001428: Jun 11 14:36:54.509 CDT: htsp_process_event: [50/0/10.1,
> EFXS_OFFHOOK, E_HTSP_EVENT_TIMER]efxs_offhook_timer
>
> 001429: Jun 11 14:36:54.513 CDT: htsp_process_event: [50/0/10.1,
> EFXS_ONHOOK, E_HTSP_RELEASE_REQ]efxs_onhook_release
>
> 001430: Jun 11 14:36:54.513 CDT: htsp_timer_stop
>
> 001431: Jun 11 14:36:54.513 CDT: [50/0/10.1] set signal state = 0x4
> timestamp = 0
>
>
>
> Thanks for any help.
>
> [image: 2C_CharLogo_Tag_CMYK]
>  ------------------------------
>
> *Hyoun Kim** • *Network Administrator – East Division
>
> 640 Broadmor Blvd *• *Suite 80 *• *Murfreesboro, TN 37129
>
> ' 615.217.6245 *• *7 615.217.6247 *• ** Hyoun.Kim at chartercom.com
>
>
>
>
>
> E-MAIL CONFIDENTIALITY NOTICE:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> The contents of this e-mail message and
>
> any attachments are intended solely for the
>
> addressee(s) and may contain confidential
>
> and/or legally privileged information. If you
>
> are not the intended recipient of this message
>
> or if this message has been addressed to you
>
> in error, please immediately alert the sender
>
>  by reply e-mail and then delete this message
>
> and any attachments. If you are not the
>
> intended recipient, you are notified that
>
> any use, dissemination, distribution, copying,
>
> or storage of this message or any attachment
>
> is strictly prohibited.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
>
>
> E-MAIL CONFIDENTIALITY NOTICE:
>
>
>
>
>
>
>
>
>
>
>
> The contents of this e-mail message and
>
> any attachments are intended solely for the
>
> addressee(s) and may contain confidential
>
> and/or legally privileged information. If you
>
> are not the intended recipient of this message
>
> or if this message has been addressed to you
>
> in error, please immediately alert the sender
>
>  by reply e-mail and then delete this message
>
> and any attachments. If you are not the
>
> intended recipient, you are notified that
>
> any use, dissemination, distribution, copying,
>
> or storage of this message or any attachment
>
> is strictly prohibited.
>
>
>
>
>
>
> E-MAIL CONFIDENTIALITY NOTICE:
>
>
>
>
>
>
>
> The contents of this e-mail message and
> any attachments are intended solely for the
> addressee(s) and may contain confidential
> and/or legally privileged information. If you
> are not the intended recipient of this message
> or if this message has been addressed to you
> in error, please immediately alert the sender
>  by reply e-mail and then delete this message
> and any attachments. If you are not the
> intended recipient, you are notified that
> any use, dissemination, distribution, copying,
> or storage of this message or any attachment
> is strictly prohibited.
>
>
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100614/09c76d25/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 1990 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100614/09c76d25/attachment.jpe>