Jon Schøpzinsky
2007-May-23 05:27 UTC
[asterisk-users] What replaces SetCallerPres in 1.4
Hello SetCallerPres function seems to be removed from Asterisk 1.4. What function or application replaced it? Bit of a problem if you want to use CLIR on your PRI connections. Jon No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.467 / Virus Database: 269.7.6/815 - Release Date: 22-05-2007 15:49 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20070523/be9ca012/attachment.htm
Jon Sch?pzinsky wrote:> > Hello > > > > SetCallerPres function seems to be removed from Asterisk 1.4. >I have it in 1.4.4 drdos*CLI> core show application setcallerpres drdos*CLI> -= Info about application 'SetCallerPres' =- [Synopsis] Set CallerID Presentation [Description] SetCallerPres(presentation): Set Caller*ID presentation on a call. Valid presentations are: -- Ben Franklin quote: "Those who would give up Essential Liberty to purchase a little Temporary Safety, deserve neither Liberty nor Safety."
On Wed, 23 May 2007 10:43:04 -0400, in gmane.comp.telephony.pbx.asterisk.user you wrote:>Has anyone implemented Asterisk behind D-Link Router? >Got one pain in butt customer who wants to setup * system behind D-Link >router model DI-624?------------------------ sip.conf: [general] externip = the_public_IP_address localnet=192.168.0.0/255.255.255.0 nat=yes canreinvite=no qualify=yes [account_for_local_sip_device] [200] type=friend secret=test nat=no host=dynamic context=mycontext [account_for_remotel_sip_device] [201] type=friend secret=test nat=yes host=dynamic context=mycontext ------------------------ rtp.conf Choose beginning and end of range for RTP ports ------------------------ on local NAT router Open UDP5060 and the RTP range per above, and forward packets to the Asterisk server. HTH,
On 5/23/07, Nitesh Divecha <nitesh@vipernetworks.com> wrote:> > Hello All, > > I need to implement a clustered PBX System where parent * is connected > to one of the outbound carrier and other child * will register to parent > *. Reason for this implementation is because some of the child * are > behind NAT. Parent * is on Public IP Address and its connected to > outbound carrier. Child * will only send out long distances calls to > Parent * to terminate, rest are internal calls. > > Now which is the best way to implement this type of scenario... DUNDi? > or custom context?Hi why dont you looking this kind of solution DS3----TDMOVERIP----SER-----ASterisk---- ram Thanks,> Nitesh > > > _______________________________________________ > --Bandwidth and Colocation provided by Easynews.com -- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20070524/e0cfdfdc/attachment.htm