<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <title>SIP Trunk configured for DNS SRV not getting INVITES</title>
  <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_category?p_l_id=386195&amp;mbCategoryId=0" />
  <subtitle>SIP Trunk configured for DNS SRV not getting INVITES</subtitle>
  <id>http://developer.cisco.com/c/message_boards/find_category?p_l_id=386195&amp;mbCategoryId=0</id>
  <updated>2013-05-22T13:02:35Z</updated>
  <dc:date>2013-05-22T13:02:35Z</dc:date>
  <entry>
    <title>SIP trunk failover</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=386195&amp;messageId=2109182" />
    <author>
      <name>Ashraf Khandwalla</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=386195&amp;messageId=2109182</id>
    <updated>2010-04-13T22:42:49Z</updated>
    <published>2010-04-13T22:42:49Z</published>
    <summary type="html">hi,

We have a Top-Down based Route Group configured with two SIP trunks for Recording Servers. It takes approx 5 seconds for the second Recording Server to get a SIP INVITE if the first computer in the Route Group is powered off. This happens for all calls while the first computer is down and results in the first 5 seconds of every call not being recorded. We are able to adjust the duration by modifying the SIP TCP Timer in the Service Parameters. We are not sure if adjusting this timer is a good idea, considering that it is a system wide configuration and affects all trunks.
 
It looks like the Call Manager always tries the first trunk first regardless of whether the first trunk is up or not. Desired behavior would be that the Call Manager detects the failure on the first call; and send subsequent INVITEs to the second server until the first server was back up and running. 
 
Is this behavior configurable or is there a recommended approach to handling this scenario so that we don¿t lose recording the first few seconds of a call? 

Thanks.</summary>
    <dc:creator>Ashraf Khandwalla</dc:creator>
    <dc:date>2010-04-13T22:42:49Z</dc:date>
  </entry>
  <entry>
    <title>SIP Trunk configured for DNS SRV not getting INVITES</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=386195&amp;messageId=2072309" />
    <author>
      <name>Ashraf Khandwalla</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=386195&amp;messageId=2072309</id>
    <updated>2010-03-26T19:52:42Z</updated>
    <published>2010-03-26T19:52:42Z</published>
    <summary type="html">hi,
 
I have a SIP Trunk configured with a DNS SRV destination address; a device configured for automatic recording; a recording profile, etc configured to associate the trunk to the device. 
 
None of my servers in the DNS SRV record get a SIP INVITE when the device answers the call.
 
A quick look at the Call Manager sdi logs seem to indicate a DNS query failure.
 
[color=#0000ff][i]03/25/2010 16:53:20.660 CCM|//SIP/SIPDns(1,53,1)/wait_SdlDnsSrvRecordRsp: (DNS A or AAAA query called as SRV query Fail):hostname=_myserver_sip._tcp.mydomain.com, ReqType=1,serversused=0
|&lt;CLID::StandAloneCluster&gt;&lt;NID::10.10.10.151&gt;&lt;CT::0,0,0,0.0&gt;&lt;IP::&gt;&lt;DEV::&gt;&lt;LVL::Detailed&gt;&lt;MASK::20000&gt;[/i][/color]
 
The query is successful when I run it in the Call Manager CLI:
 
[color=#0000ff][i]utils network host _myserver_sip._tcp.mydomain.com srv[/color][/i]
[color=#0000ff][i][/i][/color]
[color=#0000ff][i]Local Resolution:[/i][/color]
[color=#0000ff][i]Nothing found[/i][/color]
[color=#0000ff][i][/i][/color]
[color=#0000ff][i]External Resolution:[/i][/color]
[color=#0000ff][i]_myserver_sip._tcp.mydomain.com SRV 0 0 5060 host1.mydomain.com[/i][/color]
[i]
[color=#0000ff][i]_myserver_sip._tcp.mydomain.com SRV 0 0 5060 host2.mydomain.com[/i][/color]
[/i]
[i]
[color=#0000ff][i]_myserver_sip._tcp.mydomain.com SRV 0 0 5060 host3.mydomain.com[/i][/color]
[/i]
 
The query is also successful when I run it using nslookup.
 
I am not sure why the CLI would be able to run the query but the CCM service would not.
 
Appreciate any ideas anyone might have. Thanks.
 
CCM version 7.1.3
 
Ashraf
 </summary>
    <dc:creator>Ashraf Khandwalla</dc:creator>
    <dc:date>2010-03-26T19:52:42Z</dc:date>
  </entry>
</feed>

