Found a solution.
I called Viking support. Unfortunately they do not have a solutions database
but the technical support person suggested I change the gate open code to 99.
He said that the digits * and 9 are generally more tolerated by the Viking
devices. So after changing the code to 99, it
It actually may depend on what type of IP endpoint is calling the gateway.
With the gateway in MGCP mode, I have had the best overall compatibility
results when I configured the gateway to support RFC2833 and allow CUCM to
negotiate that. I usually keep the Type of DTMF Relay in CUCM to its
Yes, we press 6 or 8 to open the gate.
I have did not have mgcp dtmf-relay voip codec all mode nse set. In CUCM under
the gateway settings, I changed "Type Of DTMF Relay" to NSE. Saved, applied
config and then did a no mgcp and then mgcp on the router and tested. Still
cannot open the gate.
Any
I take it you press 6 or something to allow the gate to open? can you send a
copy of the MGCP statements on the gateway?
looking to see what the dtmf-relay is set to.
mgcp dtmf-relay voip codec all mode nse
On Tuesday, March 28, 2017 6:46 AM, Brian Meade wrote:
We'd
We'd need some debugs to see what is happening like "debug vpm signal" to
see what tones are sent on the line.
On Tue, Mar 28, 2017 at 9:35 AM, Kevin via cisco-voip <
cisco-voip@puck.nether.net> wrote:
>
> Hi,
>
> I was wondering if a solution was found.
>
> I have a similar issue. We have a
t: July-11-16 1:27 PM
To: Damisch, Kevin <kevin.dami...@oneneck.com>; Ryan Huff
<ryanh...@outlook.com>; Norton, Mike <mikenor...@pwsd76.ab.ca>
Cc: cisco-voip@puck.nether.net
Subject: RE: [cisco-voip] FXO port to Viking C-1000B door entry controller
Another update
I went thr
@outlook.com>>; Norton, Mike
<mikenor...@pwsd76.ab.ca<mailto:mikenor...@pwsd76.ab.ca>>
Cc: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Subject: Re: [cisco-voip] FXO port to Viking C-1000B door entry controller
Just giving an update on this one….
Adding “
t;mikenor...@pwsd76.ab.ca>
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] FXO port to Viking C-1000B door entry controller
Just giving an update on this one
Adding "no battery-reversal" did keep the call connected. I was able to press
** and heard the 2-tone confir
-16 3:41 PM
To: Damisch, Kevin
<kevin.dami...@oneneck.com<mailto:kevin.dami...@oneneck.com>>; Ryan Huff
<ryanh...@outlook.com<mailto:ryanh...@outlook.com>>; Wes Sisk (wsisk)
<ws...@cisco.com<mailto:ws...@cisco.com>>
Cc: cisco-voip@puck.nether.net<mailto:cisco-voip@pu
on, Mike
Sent: July-04-16 3:41 PM
To: Damisch, Kevin <kevin.dami...@oneneck.com>; Ryan Huff
<ryanh...@outlook.com>; Wes Sisk (wsisk) <ws...@cisco.com>
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] FXO port to Viking C-1000B door entry controller
Re-reading the thread, I
o-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of
Damisch, Kevin
Sent: June-30-16 12:06 AM
To: Ryan Huff <ryanh...@outlook.com>; Wes Sisk (wsisk) <ws...@cisco.com>
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] FXO port to Viking C-1000B door entry controller
Ryan - the voice p
Hi Ryan,
I'm happy to continue discussing this topic but it might be a bit generous to
call me a "master" at it. I welcome corrections from anyone if I say something
incorrect. :-)
> As I understand supervisory disconnect (as it applies to this context), for
> the local-end to be hanging up,
IMHO this is where it gets interesting. We have to leave the ‘digital’ world
and enter the ‘analog’ world. The “FXO” emits a signal, it travels across the
wire, and might possibly be echoed back at the electrical level. Get the
o-scopes ladies and gents. When the firmware of the FXO card
.com]
Sent: June-30-16 4:10 PM
To: Norton, Mike <mikenor...@pwsd76.ab.ca><mailto:mikenor...@pwsd76.ab.ca>
Cc: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>; Damisch,
Kevin <kevin.dami...@oneneck.com><mailto:kevin.dami...@oneneck.com>
Subject: Re: [
-30-16 4:10 PM
To: Norton, Mike <mikenor...@pwsd76.ab.ca>
Cc: cisco-voip@puck.nether.net; Damisch, Kevin <kevin.dami...@oneneck.com>
Subject: Re: [cisco-voip] FXO port to Viking C-1000B door entry controller
In this scenario Mike, do you think adjusting the impedance would be a benefi
spot on. right up until they invented analog answering machines… then we *HAD*
to have analog disconnect supervision.
-w
On Jun 30, 2016, at 4:25 PM, Norton, Mike
> wrote:
A phone company cannot magically reach into your house and put
0-16 2:26 PM
To: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>; Ryan Huff
<ryanh...@outlook.com<mailto:ryanh...@outlook.com>>
Subject: Re: [cisco-voip] FXO port to Viking C-1000B door entry controller
I’m not Wes but I’ll take a go at it...
An FXO port is the essential
her.net] On Behalf Of
Norton, Mike
Sent: June-30-16 2:26 PM
To: cisco-voip@puck.nether.net; Ryan Huff <ryanh...@outlook.com>
Subject: Re: [cisco-voip] FXO port to Viking C-1000B door entry controller
I'm not Wes but I'll take a go at it...
An FXO port is the essentially the same thing
(wsisk) <ws...@cisco.com<mailto:ws...@cisco.com>>
Cc: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Subject: Re: [cisco-voip] FXO port to Viking C-1000B door entry controller
Wes,
With the utmost respect to you, I just want to take a moment to understand
someth
and thus
sucks.
-mn
From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Ryan
Huff
Sent: June-29-16 5:32 PM
To: Wes Sisk (wsisk) <ws...@cisco.com>
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] FXO port to Viking C-1000B door entry controller
: Damisch, Kevin <kevin.dami...@oneneck.com>; cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] FXO port to Viking C-1000B door entry controller
Wes,
With the utmost respect to you, I just want to take a moment to understand
something, in hopes that I may learn something from you (if yo
From: Wes Sisk (wsisk) <ws...@cisco.com>
Sent: Wednesday, June 29, 2016 6:56 PM
To: Ryan Huff
Cc: Damisch, Kevin; cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] FXO port to Viking C-1000B door entry controller
alternatively looks like the FXO port might be configured to to tone disc
alternatively looks like the FXO port might be configured to to tone disconnect
supervision. try disabling that all together and work forward from there. IIRC
(dis)connect supervision is implemented in firmware on the card and is only
sent back to IOS as an asserted event. Alternatively stated:
On the Cisco FXO port side, try "impedance 600r" under the voice port config.
Essentially, what I believe you are up against, is a sine oscillation
disagreement between the FXO port and the Viking.
Thanks,
Ryan
On Jun 29, 2016, at 5:55 PM, Damisch, Kevin
24 matches
Mail list logo