[cisco-voip] SIP trunk status

Aman Chugh aman.chugh at gmail.com
Fri Jun 7 12:07:32 EDT 2013


Hi,

I think it is do able , I have not tried it in my lab yet. Syslogs in CUCM
do log a Sip trunk (Out of service) message and that can be sent as a
custom alert using RTMT syslog string match found alarm.


Aman

On Fri, Jun 7, 2013 at 10:42 AM, Matthew Loraditch <
MLoraditch at heliontechnologies.com> wrote:

>  Can that report via SNMP or some sort of IP SLA?****
>
> I’ve been trying to find a way to monitor my carrier connections and
> haven’t come up with anything that works.****
>
> The SBC’s they have don’t respond to regular ping and only allow
> connections from my sip source interface on my CUBE routers.****
>
> ** **
>
> ** **
>
> Matthew G. Loraditch – CCNP-Voice, CCNA, CCDA
>
> 1965 Greenspring Drive
> Timonium, MD 21093
>
> voice. 410.252.8830
> fax.  410.252.9284
>
> Twitter <http://twitter.com/heliontech>  |  Facebook<http://www.facebook.com/#!/pages/Helion/252157915296>
> | Website <http://www.heliontechnologies.com/>  |  Email Support<support at heliontechnologies.com?subject=Technical%20Support%20Request>
> ****
>
> ** **
>
> ** **
>
> ** **
>
> *From:* cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] *On Behalf
> Of *Joel Perez
> *Sent:* Friday, June 07, 2013 10:14 AM
>
> *To:* Eric Pedersen
> *Cc:* cisco-voip
> *Subject:* Re: [cisco-voip] SIP trunk status****
>
> ** **
>
> Hi Eric,****
>
> ** **
>
> Depending on what version of IOS you are running you can also use the
> "Options-Ping" commands on the dial peers pointing to CM or your SIP
> provider.****
>
> ** **
>
> You use "voice-class sip options-keepalive " and manipulate the timers in
> that command. That should get you what you want if i understood your
> question correctly.****
>
> ** **
>
> Joel P****
>
> ** **
>
> ** **
>
> ** **
>
> On Thu, Jun 6, 2013 at 3:49 PM, Eric Pedersen <PedersenE at bennettjones.com>
> wrote:****
>
>  That's good to hear.****
>
>  ****
>
> I have a related question: we have our SIP trunks to IOS gateways
> configured with OPTIONS ping. If a WAN issue causes the first CM in the CM
> group to be unable to reach the gateway will all calls to that GW get
> routed by the second CM provided the gateway is reachable from that
> server?  ****
>
>  ****
>
> Thank you,****
>
> Eric****
>
>  ****
>
> *From:* Chris Ward (chrward) [mailto:chrward at cisco.com]
> *Sent:* 06 June 2013 1:43 PM
> *To:* Ryan Ratliff (rratliff); Eric Pedersen
> *Cc:* cisco-voip
> *Subject:* RE: [cisco-voip] SIP trunk status****
>
>  ****
>
> I believe that feature is en route for 10.0.****
>
>  ****
>
> +Chris****
>
> Unity Connection TME****
>
>  ****
>
> *From:* cisco-voip [mailto:cisco-voip-bounces at puck.nether.net<cisco-voip-bounces at puck.nether.net>]
> *On Behalf Of *Ryan Ratliff (rratliff)
> *Sent:* Thursday, June 06, 2013 3:37 PM
> *To:* Eric Pedersen
> *Cc:* cisco-voip
> *Subject:* Re: [cisco-voip] SIP trunk status****
>
>  ****
>
> RTMT doesn't *currently* provide the state of SIP trunks.****
>
>  ****
>
> -Ryan ****
>
>  ****
>
> On Jun 6, 2013, at 3:09 PM, Eric Pedersen <PedersenE at bennettjones.com>
> wrote:****
>
>  ****
>
> Is there a way to monitor the status of a SIP trunk from CUCM's
> perspective, i.e. in-service/out-of-service, either with RTMT or SNMP?
> There are syslog messages that are generated when a SIP trunk becomes
> unreachable by CUCM servers but I'd like to be able to poll for the status.
> ****
>
>  ****
>
> Thanks,****
>
> Eric****
>
> The contents of this message may contain confidential and/or privileged****
>
> subject matter. If this message has been received in error, please contact****
>
> the sender and delete all copies. Like other forms of communication,****
>
> e-mail communications may be vulnerable to interception by unauthorized****
>
> parties. If you do not wish us to communicate with you by e-mail, please****
>
> notify us at your earliest convenience. In the absence of such****
>
> notification, your consent is assumed. Should you choose to allow us to****
>
> communicate by e-mail, we will not take any additional security measures****
>
> (such as encryption) unless specifically requested.****
>
>  ****
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip****
>
>   ****
>
> The contents of this message may contain confidential and/or privileged****
>
> subject matter. If this message has been received in error, please contact****
>
> the sender and delete all copies. Like other forms of communication,****
>
> e-mail communications may be vulnerable to interception by unauthorized****
>
> parties. If you do not wish us to communicate with you by e-mail, please****
>
> notify us at your earliest convenience. In the absence of such****
>
> notification, your consent is assumed. Should you choose to allow us to****
>
> communicate by e-mail, we will not take any additional security measures****
>
> (such as encryption) unless specifically requested.****
>
> ** **
>
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20130607/e2113877/attachment.html>


More information about the cisco-voip mailing list