[VoiceOps] Acme Packet/Broadsoft/ENUM

[Mark R Lindsey]

Would sag-recursion obviate the need for the two session groups? 

It would allow the SD attempt more than one target within that SAG for the same SIP transaction. 

But I haven't tried it with enum. 

On Jan 5, 2012, at 18:03, Tim Thompson <timthompson at nicodem.us> wrote:

> Yessir:
> 
> session-group
>        group-name                     NetSrvr
>        description                    Broadsoft_NetGroup
>        state                          enabled
>        app-protocol                   SIP
>        strategy                       Hunt
>        dest
>                                       net1.bs.sip
>                                       net2.bs.sip
> 
> session-group
>        group-name                     NetSrvr2
>        description                    Broadsoft_NetGroup
>        state                          enabled
>        app-protocol                   SIP
>        strategy                       Hunt
>        dest
>                                       net2.bs.sip
>                                       net1.bs.sip
> 
> Make sure if you go the SAG route, that enum-sag-match is enabled in the
> sip-config on the SD, else it won't match back to the SAG.
> 
> -Tim
> 
> On 01/05/2012 02:59 PM, Robert Dawson wrote:
>> Perfect - thanks again.
>> 
>> Just to clarify, NetSrvr and NetSrvr2 are the actual names of the SAGs on the AP?
>> 
>>> -----Original Message-----
>>> From: Tim Thompson [mailto:timthompson at nicodem.us]
>>> Sent: Thursday, January 05, 2012 5:51 PM
>>> To: Robert Dawson
>>> Cc: voiceops at voiceops.org
>>> Subject: Re: [VoiceOps] Acme Packet/Broadsoft/ENUM
>>> 
>>> We also use powerdns, but use the pipe backend to pass it through some
>>> in-house code, which is itself backended by oracle. This works more or
>>> less the same, but you gain some additional control via the pipe
>>> backend.
>>> 
>>> Here's the results of a 'show enum lookup'. DNs and FQDNs have been
>>> changed to protect the innocent.
>>> 
>>> Enum Lookup Result:
>>> Query Name -->
>>>        +9165551212
>>> Answers -->
>>>        sip:+19165551212 at NetSrvr ttl= 120
>>>        sip:+19165551212 at NetSrvr2 ttl= 120
>>> 
>>> And the associated cache-entry:
>>> Query-->
>>>        Q:NAPTR 2.1.2.1.5.5.5.6.1.9.tld ttl=48
>>> Answers-->
>>> 
>>>           order=50 pref=1 "u" "E2U+sip"
>>> "!^.*$!sip:+19165551212 at NetSrvr!" ""
>>> 
>>>           order=50 pref=2 "u" "E2U+sip"
>>> "!^.*$!sip:+19165551212 at NetSrvr2!" ""
>>> 
>>> The same query via dig:
>>> 
>>> ;; ANSWER SECTION:
>>> 2.1.2.1.5.5.5.6.1.9.tld. 120 IN NAPTR 50 1 "u" "E2U+sip"
>>> "!^.*$!sip:+19165551212 at NetSrvr!" .
>>> 2.1.2.1.5.5.5.6.1.9.tld. 120 IN NAPTR 50 2 "u" "E2U+sip"
>>> "!^.*$!sip:+19165551212 at NetSrvr2!" .
>>> 
>>> 
>>> Both NetSrvr and NetSrvr2 are SAGs, with the two netservers'
>>> session-agents in reverse orders, per best practices. (i.e. Net1/Net2,
>>> Net2/Net1.)
>>> 
>>> Hope this helps,
>>> -Tim
>>> 
>>> 
>>> On 01/05/2012 02:19 PM, Robert Dawson wrote:
>>>> Sure, anything would be helpful. I am using powerdns with a mysql
>>> backend, sounds similar to your setup.
>>>> 
>>>> Thanks,
>>>> Rob
>>>> 
>>>>> -----Original Message-----
>>>>> From: voiceops-bounces at voiceops.org [mailto:voiceops-
>>>>> bounces at voiceops.org] On Behalf Of Tim Thompson
>>>>> Sent: Thursday, January 05, 2012 4:01 PM
>>>>> To: voiceops at voiceops.org
>>>>> Subject: Re: [VoiceOps] Acme Packet/Broadsoft/ENUM
>>>>> 
>>>>> Rob,
>>>>> 
>>>>> We use a custom in-house ENUM solution that queries a database in
>>> real
>>>>> time, so I can't offer you an actual zone snippet. I could give some
>>>>> examples of what 'show enum lookup' or dig would return, if that
>>> would
>>>>> be helpful.
>>>>> 
>>>>> -Tim
>>>>> 
>>>>> 
>>>>> On 01/05/2012 11:12 AM, Robert Dawson wrote:
>>>>>> Is anyone using ENUM with their Acme/BS deployment that wouldn't
>>> mind
>>>>>> sharing a snippet of their zone file showing the proper record
>>>>>> configuration?
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> Thanks,
>>>>>> 
>>>>>> Rob
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> _______________________________________________
>>>>>> VoiceOps mailing list
>>>>>> VoiceOps at voiceops.org
>>>>>> https://puck.nether.net/mailman/listinfo/voiceops
>>>>> _______________________________________________
>>>>> VoiceOps mailing list
>>>>> VoiceOps at voiceops.org
>>>>> https://puck.nether.net/mailman/listinfo/voiceops
>> 
> 
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops