[cisco-voip] alarm panel issues and VG224 w/ SCCP

Fuermann, Jason jason.f at shsu.edu
Wed Mar 30 10:48:21 EDT 2011


Did you ever get this figured out?

From: Lelio Fulgenzi [mailto:lelio at uoguelph.ca]
Sent: Thursday, March 24, 2011 5:48 PM
To: Nick Matthews
Cc: Fuermann, Jason; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] alarm panel issues and VG224 w/ SCCP

Thanks Nick. After talking with the client, it seems it's only one of a number of alarm panels that is causing the problem. So I'm not sure what the difference is between this unit and others. I'm hoping the client can set up a meeting with the vendor as soon as possible.

Reading one of the threads, it talks about 4+2 or 4x2 as using touch tones and the contact ID using hook flashes. I wonder if switching modes will help.





---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it.
                              - LFJ (with apologies to Mr. Popeil)

________________________________
From: "Nick Matthews" <matthnick at gmail.com>
To: "Lelio Fulgenzi" <lelio at uoguelph.ca>
Cc: "Jason Fuermann" <jason.f at shsu.edu>, cisco-voip at puck.nether.net
Sent: Thursday, March 24, 2011 6:08:41 PM
Subject: Re: [cisco-voip] alarm panel issues and VG224 w/ SCCP

Can almost tell you the problem from the title of the email:

The problem with using MGCP/SCCP on these ports is that they are going to do DTMF relay.  They will take the TDM tone, convert it to sccp, and replay it on the other side.  This doesn't jive with alarm panels because their timing is very specific.  They basically use DTMF tones like modem tones and send information back and forth via DTMF. Because SCCP DTMF messages have a fixed duration when they are replayed, this interferes with the timing between digits and the actual digits themselves.

The solution is to switch this to H323 (or SIP) and on your outbound dial peer omit any type of dtmf-relay.  This allows the g711 stream to carry the dtmf natively to the headend.

-nick
On Thu, Mar 24, 2011 at 2:40 PM, Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>> wrote:
That was my suspicion. Just wondering if those who went from SCCP to MGCP/H323 were encountering the same thing.

We'll have to see what the alarm vendor says.

I'm hoping someone on the list who has sccp/h323 configured ports on a vg224 can help with my other questions.


---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120<tel:%28519%29%20824-4120> x56354 (519) 767-1060<tel:%28519%29%20767-1060> FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it.
                              - LFJ (with apologies to Mr. Popeil)

________________________________
From: "Jason Fuermann" <jason.f at shsu.edu<mailto:jason.f at shsu.edu>>
To: "Lelio Fulgenzi" <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>, cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Sent: Thursday, March 24, 2011 12:46:34 PM
Subject: RE: [cisco-voip] alarm panel issues and VG224 w/ SCCP

The head end is probably hanging up while the dialer is still spitting out codes, and the gw thinks it’s trying to dial an extension. Just a guess.
http://markmail.org/message/kwzlalbdo2asbxqo


From: cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net> [mailto:cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>] On Behalf Of Lelio Fulgenzi
Sent: Thursday, March 24, 2011 10:55 AM
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: [cisco-voip] alarm panel issues and VG224 w/ SCCP

We have a remote site which uses alarms on their VG224. It seems they're not working properly. I've got a call back into the client to arrange a conference call with their alarm provider so I have access to technical details I can share.

When I look at the CDRs, I see some strange entries. Basically a call to a toll free number, followed by short calls of 1 second with invalid DNs. (see below)

I recall some talk about alarms and SCCP and it's better with MGCP. Can anyone who had this problem confirm if this was the same issue?

I have no problem setting up a few ports for MGCP but I have some concerns:

 *   can I have a VG224 with some ports as SCCP and some as MGCP?
 *   how can I ensure that my MGCP ports work during failover, i.e. SRST?

    *   I don't want to have to redo all my dial-peers. I don't mind putting in one dial that sends all calls from the VG224 to the SRST router, but I'd like an inbound dialpeer from the VG224 that assigns the same class of service for all inbound calls from that vg224.
    *   Is this doable?

________________________________
call 1

call 2

DateTimeOrigination

DateTimeOrigination

  Mar 8, 2011 10:02:10 AM

  Mar 8, 2011 10:02:34 AM

OriginalCalledPartyNumber

OriginalCalledPartyNumber

  1866------- <snip>

  7000C

FinalCalledPartyNumber

FinalCalledPartyNumber

  1866------- <snip>

  7000C

DateTimeConnect

DateTimeConnect

  Mar 8, 2011 10:02:22 AM

  N/A

DateTimeDisconnect

DateTimeDisconnect

  Mar 8, 2011 10:02:34 AM

  Mar 8, 2011 10:02:36 AM

Duration

Duration

  12

  0

________________________________

---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120<tel:%28519%29%20824-4120> x56354 (519) 767-1060<tel:%28519%29%20767-1060> FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it.
                              - LFJ (with apologies to Mr. Popeil)

_______________________________________________
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/20110330/4ec29330/attachment.html>


More information about the cisco-voip mailing list