[priv]
type=3Dfriend
dbsecret=3Ddundi/secret
context=3Dlongdistance
Hope this helps, in your case Dundi will save you a world of work on
configuring that many systems, in fact if you structure Dundi like
spokes around a small number of master servers, the config gets real
easy.Let me know how it goes.
On Wed, Apr 16, 2008 at 8:41 AM, Jeremy Mann <jmann at txhmg.com>
wrote:>
>
>
>
> I'm a little confused with DUNDi and SIP as the backend channel type:
>
>
>
> Dundi.conf:
>
> [mappings]
>
> priv =3D> dundi-priv-local,0,SIP,${NUMBER}@a.b.c.d,nopartial
>
>
>
> Using the above, the dial string passed to the person on the other box is
> SIP/${NUMBER}@a.b.c.d
>
>
>
> How can you use authentication, along with SIP, along with specifying
> extension?
>
>
>
> My sip.conf has a friend defined:
>
>
>
> [priv]
>
> host=3Ddynamic
>
> secret=3Dpriv
>
> disallow=3Dall
>
> allow=3Dulaw
>
> canreinvite=3Dno
>
> nat=3Dno
>
> context=3Dfrom-internal\
>
> type=3Dfriend
>
>
>
> I need to specify the sip channel to use the priv peer, priv secret, and
> pass the extension. I've tried defining my mapping as:
>
>
>
> Priv =3D> dundi-priv-local,0,SIP,priv:priv at
a.b.c.d/${NUMBER},nopartial
>
>
>
> But obviously the console on the far end complains that peer
> a.b.c.d/${NUMBER} cannot be found.
>
>
>
> Thanks for any insight into this. I'd prefer not having to define a
sip
> peer per box(I have 25 connected in my dundi cloud), nor would I like to
> enable anonymous SIP calls, as I have the ports open to the world for
> inbound sip from bandwidth.com
>
>
>
>
> ________________________________
> This e-mail, facsimile, or letter and any files or attachments transmitted
> with it contains information that is confidential and privileged. This
> information is intended only for the use of the individual(s) and
> entity(ies) to whom it is addressed. If you are the intended recipient,
> further disclosures are prohibited without proper authorization. If you are
> not the intended recipient, any disclosure, copying, printing, or use of
> this information is strictly prohibited and possibly a violation of federal
> or state law and regulations. If you have received this information in
> error, please notify Texas Health Management Group immediately at
> 1-817-310-4999. Texas Health Management Group, its subsidiaries, and
> affiliates hereby claim all applicable privileges related to this
> information.
>
> _______________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-users
>
--
*****************************
Bruce Reeves, dCAp
EUS Networks
Office: 212-624-5943
Web: www.euscorp.com
****************************
_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
This e-mail, facsimile, or letter and any files or attachments transmitted with
it contains information that is confidential and privileged. This information is
intended only for the use of the individual(s) and entity(ies) to whom it is
addressed. If you are the intended recipient, further disclosures are prohibited
without proper authorization. If you are not the intended recipient, any
disclosure, copying, printing, or use of this information is strictly prohibited
and possibly a violation of federal or state law and regulations. If you have
received this information in error, please notify Texas Health Management Group
immediately at 1-817-310-4999. Texas Health Management Group, its subsidiaries,
and affiliates hereby claim all applicable privileges related to this
information.
