[cisco-voip] problem forwarding calls

[VoIP Guy]

A couple of years ago we came across the same thing and it was because the
router was making 2 calls to the same cell phone, tieing up the line for a
very short duration (in the magnitude of milliseconds) causing the cell
phone network to present voicemail to the second call which is the real
call. The details of that issue escape me now unfortunately as regards
whether the cell phone actually rang at all but as Jim stated, a debug isdn
q931 should actually show what is happening.

Let us know the results of your debugs and outputs.

On Thu, Nov 11, 2010 at 6:21 PM, Jim Reed <jreed at swiftnews.com> wrote:

>  *Andy,
> What is the dial string you’re putting in the DN setup to forward to the
> external device?  That will give some indication of what dial peer it will
> attempt to use on the router.  Also, you might try logging into the router,
> doing a “debug isdn q931” and “term mon”.  Then place a call to that
> extension and let it complete the process of forwarding to the cell phone.
>  You should see a bunch of stuff run across the screen.  Once the call is
> complete, hang up and do a “term no mon” and “undebug all”.  If you want,
> copy the data from the screen and send it to me so I can look at it.  Also,
> if you have the proper configuration in your router, you should be able to
> do a “show call history voice” and run all of that out as well.  That will
> give a complete history of what went on on the gateway during all of your
> calls for the last several hours.  Somewhere in there you’ll be able to see
> exactly what the gateway sent to the telco during that particular forward.
> **
> --
> Jim Reed
> Manager of Technical Services
> and “de facto Sprint employee”
> Swift Communications, Inc.
> 970-384-9141 (Direct)
> 775-772-7666 (Cell)
>
> Today’s Paraprosdokian:
> I know the voices
> in my head aren’t real.
> But they do have some
> really good ideas.
> *
>
>
> On 11/11/10 7:48 AM, "Andy Infante" <AInfante at APRecovery.Com> wrote:
>
> It’s going to the cell phone voicemail, not internal voicemail.  Attached
> is our router config.  This was created before I became admin here, and I’m
> not that familiar with the voice routing…so I don’t know exactly what to
> change.
>
> Andy
>
>
>
>
>
>
> *From:* Jim Reed [*mailto:jreed at swiftnews.com <jreed at swiftnews.com>*]
> *Sent:* Wednesday, November 10, 2010 6:11 PM
> *To:* Andy Infante; *cisco-voip at puck.nether.net
> **Subject:* Re: [cisco-voip] problem forwarding calls
>
> *Andy,
> When you say it goes to voicemail, is it going to the external device
> voicemail or your internal voicemail.  One mistake that some of my fellow IT
> guys make when configuring a DN to forward externally is checking the box to
> the right of Forward All and then putting a number in the
> Coverage/Destination field.  Those are two separate entities and once you
> put a check in the box to the right of Forward All, all calls are forwarded
> to internal voicemail.  That probably isn’t what’s happening but I am trying
> to figure out what kind of dial sequence would be going out that would cause
> the call to go directly to the external devices voicemail instead of ringing
> that device.
> **--
> Jim Reed
> Manager of Technical Services
> and “de facto Sprint employee”
> Swift Communications, Inc.
> 970-384-9141 (Direct)
> 775-772-7666 (Cell)
>
> Today’s Paraprosdokian:
> I want to die peacefully in my sleep,
> like my grandfather.
> Not screaming and yelling
> like the passengers in his car.
> *
>
> On 11/10/10 2:50 PM, "Andy Infante" <*AInfante at APRecovery.Com*> wrote:
> If we have a line forwarded to an external number outside of the
> organization, when an internal caller dials the 4 digit extension, they are
> forwarded to the external number’s voicemail instead of directly to the
> device (like a cell phone for example).  Additionally, if the external
> number is an AT&T line, AT&T doesn’t even recognize the called id, and says
> it can’t even find the voicemail mailbox.  Verizon gets the called number id
> can correctly goes to the right mailbox, but the cell phone never even
> rings.
>
> Is there a configuration on call manager (we are using 4.2 (3)) or the
> router that needs to be done for this to work properly?
>
> Thanks,
>
> Andy Infante
>
>
> IMPORTANT: This e-mail and any attachments may contain confidential,
> proprietary, and/or privileged information.
> If you are not the intended recipient, please notify the sender immediately
> by return e-mail, delete this e-mail, and destroy any copies. Any
> dissemination, copying, retention, printing, or use of this information by a
> person other than the intended recipient is unauthorized and may be illegal.
> Any opinions expressed in this e-mail are those of the author and may not
> reflect the views of the company. The sender believes that this E-mail and
> any attachments were free of any virus, worm, Trojan horse, and/or malicious
> code when sent. This message and its attachments could have been infected
> during transmission. By reading the message and opening any attachments, the
> recipient accepts full responsibility for taking protective and remedial
> action about viruses and other defects. The sender's employer is not liable
> for any loss or damage arising in any way from this message or its
> attachments.
>
>
>
> IMPORTANT: This e-mail and any attachments may contain confidential,
> proprietary, and/or privileged information.
> If you are not the intended recipient, please notify the sender immediately
> by return e-mail, delete this e-mail, and destroy any copies. Any
> dissemination, copying, retention, printing, or use of this information by a
> person other than the intended recipient is unauthorized and may be illegal.
> Any opinions expressed in this e-mail are those of the author and may not
> reflect the views of the company. The sender believes that this E-mail and
> any attachments were free of any virus, worm, Trojan horse, and/or malicious
> code when sent. This message and its attachments could have been infected
> during transmission. By reading the message and opening any attachments, the
> recipient accepts full responsibility for taking protective and remedial
> action about viruses and other defects. The sender's employer is not liable
> for any loss or damage arising in any way from this message or its
> attachments.
>
>
>
>
> _______________________________________________
> cisco-voip mailing list
> 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/20101111/47e16da3/attachment.html>