[cisco-voip] No inbound call signaling

norm.nicholson at kitchener.ca norm.nicholson at kitchener.ca
Mon Mar 14 14:54:59 EDT 2016


Here are some things to check…



1)      Put a volt meter across tip and ring to measure the ringing voltage ( AC ) . Should be above 75 volts AC

2)      If it is old rural copper and a long distance from the CO there may be load coils on the pair. The Telco can confirm this and may need to be replaced.

3)      Check for ground hums or an imbalance hum on the line.



Thanks



From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Horton, Jamin
Sent: Monday, March 14, 2016 2:35 PM
To: Norton, Mike
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] No inbound call signaling

Mike,

You’re right I should consider every piece along the path. I’ll change it out and let you know. Appreciate your feedback.

Jamin Horton – Collaboration Practice Manager
CCIE Collaboration #39988
Direct:  303-734-4048
Cell:  720-401-8340
Email:  Jamin.Horton at OneNeck.com<mailto:Jamin.Horton at OneNeck.com>

[cid:image001.png at 01D02C2C.D0AFA6E0]   [cid:image002.jpg at 01D17E01.50746F10]
[cid:image004.png at 01D17E01.50746F10]<xmpp:jamin.horton at uc.oneneck.com>[cid:image006.png at 01D17E01.50746F10]<tel:3037344048>[cid:image014.png at 01D17E01.50746F10]<tel:jamin.horton at uc.oneneck.com>[cid:image024.png at 01D17E01.50746F10]<https://jabber-guest.uc.oneneck.com/call/jamin.horton@uc.oneneck.com>[cid:image039.png at 01D17E01.50746F10]<https://oneneck.webex.com/join/jamin.horton>[cid:image041.png at 01D17E01.50746F10]<tel:3033873980>

[Description: Description: unknown.png] - This email may contain confidential and privileged material for the sole use of the intended recipient. Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

From: Norton, Mike [mailto:mikenorton at pwsd76.ab.ca]
Sent: Monday, March 14, 2016 11:56 AM
To: Horton, Jamin
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: RE: [cisco-voip] No inbound call signaling

I wouldn’t be so quick to rule out cabling.

Ring voltage is WAY higher than anything else that goes through that cable, so ringing can often highlight cabling problems that other signals appear to be fine with. It is common to have a “partial” short (e.g. nicked wire insulation, or moisture) that does not conduct noticeably at low voltages, but the high voltage ringing will break through and make the problem apparent.

A butt set would probably still “hear” the ringing even if most of the ring current is sucked up by a partial short in the cabling. A better test would be an old-style telephone set with a mechanical bell ringer.

Unless the line can ring a mechanical bell ringer, IMO you cannot confidently proclaim that the cabling is fine.

-mn

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Horton, Jamin
Sent: March-14-16 11:23 AM
To: Anthony Holloway <avholloway+cisco-voip at gmail.com<mailto:avholloway+cisco-voip at gmail.com>>
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] No inbound call signaling

Anthony / Ryan,

Appreciate the feedback. Comments below.

1. Did you plug in an analog phone to the analog line (aka 1FB, aka POTS) and confirm inbound and outbound dialing?  I couldn't tell from your wording, if you plugged the phone into the router or the trunk line. Yes, I used a butt set and was able to confirm inbound dialing. I also configured a route pattern that used the FXO outbound and can see it make the port active and it rings my cell just fine.

2. What debugs are you using, and are you trying to debug to the terminal session or to the buffer?  What does your debug config look like? Debug vpm signal, debug mgcp all, debug voice ccapi inout.

3. What type of analog trunk signaling is it?  Loop start?  Ground start?  E&M? Loop start. I tried configuring Ground Start as well but no dice.


Is there a plar on the voice port going somewhere you are not expecting maybe? No, I have it set to ring where I want but never see anything inbound

Have you tried a new cable from the demarcation to the router? No, cable does not appear to be the issue as I can dial outbound fine via the router and inbound/outbound using a butt set.

If the telco is using anti-tinkle circuits, you may need to play around with the ring in frequency. I’m going to open a case with them, I’ll definitely ask about this. Thanks!

You may also need to adjust the dc-offset voltage. I’m going to open a case with them, I’ll definitely ask about this. Thanks!


I’m going to open a case with Telco to verify that my ringing current is sufficient.


Jamin Horton – Collaboration Practice Manager
CCIE Collaboration #39988
Direct:  303-734-4048
Cell:  720-401-8340
Email:  Jamin.Horton at OneNeck.com<mailto:Jamin.Horton at OneNeck.com>

[cid:image001.png at 01D02C2C.D0AFA6E0]   [cid:image044.jpg at 01D17E01.50746F10]
[cid:image045.png at 01D17E01.50746F10]<xmpp:jamin.horton at uc.oneneck.com>[cid:image046.png at 01D17E01.50746F10]<tel:3037344048>[cid:image047.png at 01D17E01.50746F10]<tel:jamin.horton at uc.oneneck.com>[cid:image048.png at 01D17E01.50746F10]<https://jabber-guest.uc.oneneck.com/call/jamin.horton@uc.oneneck.com>[cid:image049.png at 01D17E01.50746F10]<https://oneneck.webex.com/join/jamin.horton>[cid:image050.png at 01D17E01.50746F10]<tel:3033873980>

[Description: Description: unknown.png] - This email may contain confidential and privileged material for the sole use of the intended recipient. Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

From: avholloway at gmail.com<mailto:avholloway at gmail.com> [mailto:avholloway at gmail.com] On Behalf Of Anthony Holloway
Sent: Monday, March 14, 2016 10:26 AM
To: Horton, Jamin
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] No inbound call signaling

Sounds like you know what your doing, but I'll just ask and confirm three things:

1. Did you plug in an analog phone to the analog line (aka 1FB, aka POTS) and confirm inbound and outbound dialing?  I couldn't tell from your wording, if you plugged the phone into the router or the trunk line.

2. What debugs are you using, and are you trying to debug to the terminal session or to the buffer?  What does your debug config look like?

3. What type of analog trunk signaling is it?  Loop start?  Ground start?  E&M?

On Mon, Mar 14, 2016 at 11:08 AM, Horton, Jamin <jamin.horton at oneneck.com<mailto:jamin.horton at oneneck.com>> wrote:
Hello all,

I have a weird one. I’m in a rural area for a customer and I can’t get inbound calls on the FXO port to generate any debugs of any kind. I can call outbound all day and see debugs when doing so. I’ve put a phone on the end of the cable going into the router and verified inbound calls ring in from the PSTN. However the second it’s connected to the FXO port I get nothing on the CLI. We’ve replaced PVDM and FXO card, even tried a different router. I’m thinking it may be possibly be an inbound ringing current issue. Thoughts anyone?

Jamin Horton – Collaboration Practice Manager
CCIE Collaboration #39988
Direct:  303-734-4048<tel:303-734-4048>
Cell:  720-401-8340<tel:720-401-8340>
Email:  Jamin.Horton at OneNeck.com<mailto:Jamin.Horton at OneNeck.com>

[cid:image001.png at 01D02C2C.D0AFA6E0]   [cid:image002.jpg at 01D17E01.50746F10]
[cid:image051.png at 01D17E01.50746F10][cid:image052.png at 01D17E01.50746F10]<tel:3037344048>[cid:image053.png at 01D17E01.50746F10]<tel:jamin.horton at uc.oneneck.com>[cid:image054.png at 01D17E01.50746F10]<https://jabber-guest.uc.oneneck.com/call/jamin.horton@uc.oneneck.com>[cid:image055.png at 01D17E01.50746F10]<https://oneneck.webex.com/join/jamin.horton>[cid:image056.png at 01D17E01.50746F10]<tel:3033873980>

[Description: Description: unknown.png] - This email may contain confidential and privileged material for the sole use of the intended recipient. Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.


_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160314/82f0669b/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 2092 bytes
Desc: image001.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160314/82f0669b/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 894 bytes
Desc: image002.jpg
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160314/82f0669b/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 1973 bytes
Desc: image004.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160314/82f0669b/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 2309 bytes
Desc: image006.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160314/82f0669b/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image014.png
Type: image/png
Size: 2191 bytes
Desc: image014.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160314/82f0669b/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image024.png
Type: image/png
Size: 1678 bytes
Desc: image024.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160314/82f0669b/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image039.png
Type: image/png
Size: 1836 bytes
Desc: image039.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160314/82f0669b/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image041.png
Type: image/png
Size: 1498 bytes
Desc: image041.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160314/82f0669b/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image042.png
Type: image/png
Size: 1636 bytes
Desc: image042.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160314/82f0669b/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image043.png
Type: image/png
Size: 2090 bytes
Desc: image043.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160314/82f0669b/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image044.jpg
Type: image/jpeg
Size: 894 bytes
Desc: image044.jpg
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160314/82f0669b/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image045.png
Type: image/png
Size: 2025 bytes
Desc: image045.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160314/82f0669b/attachment-0009.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image046.png
Type: image/png
Size: 2345 bytes
Desc: image046.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160314/82f0669b/attachment-0010.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image047.png
Type: image/png
Size: 2234 bytes
Desc: image047.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160314/82f0669b/attachment-0011.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image048.png
Type: image/png
Size: 1715 bytes
Desc: image048.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160314/82f0669b/attachment-0012.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image049.png
Type: image/png
Size: 1880 bytes
Desc: image049.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160314/82f0669b/attachment-0013.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image050.png
Type: image/png
Size: 1541 bytes
Desc: image050.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160314/82f0669b/attachment-0014.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image051.png
Type: image/png
Size: 1973 bytes
Desc: image051.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160314/82f0669b/attachment-0015.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image052.png
Type: image/png
Size: 2309 bytes
Desc: image052.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160314/82f0669b/attachment-0016.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image053.png
Type: image/png
Size: 2191 bytes
Desc: image053.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160314/82f0669b/attachment-0017.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image054.png
Type: image/png
Size: 1678 bytes
Desc: image054.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160314/82f0669b/attachment-0018.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image055.png
Type: image/png
Size: 1836 bytes
Desc: image055.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160314/82f0669b/attachment-0019.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image056.png
Type: image/png
Size: 1498 bytes
Desc: image056.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160314/82f0669b/attachment-0020.png>


More information about the cisco-voip mailing list