http://lists.digium.com/pipermail/asterisk-users/2004-October/065540.html I saw this post about the M(x) option for the Dial command, but I could not find a reply questions posed here. I am wanting to pass the Zap channel that the original call came from to my macro embedded in the Dial command. I've tried to add arguments to the macro by using the syntax M(x,arg1), and I always get the following errors. Dec 2 15:57:53 WARNING[96234416]: app_dial.c:629 dial_exec: Could not find macro to which we should jump. Dec 2 15:57:53 WARNING[96234416]: app_dial.c:636 dial_exec: Macro flag set without trailing ') Is there a patch that would allow me to do this? Or is there a way to get the Zap channel name that requested the Dial on the outbound trunk from within the macro? Regards, Shaun Tierney
> -----Original Message----- > From: Shaun Tierney [mailto:stierney@prairiestream.com] > Sent: 02 December 2004 22:37 > To: Asterisk Users > Subject: [Asterisk-Users] Dial Command M(x) Option > > > http://lists.digium.com/pipermail/asterisk-users/2004-October/ > 065540.htmlI never did find a solution to the above problem! So if you / anyone does I would be very interested.> > I saw this post about the M(x) option for the Dial command, > but I could not find a reply questions posed here. I am > wanting to pass the Zap channel that the original call came > from to my macro embedded in the Dial command. I've tried to > add arguments to the macro by using the syntax M(x,arg1), and > I always get the following errors. > > Dec 2 15:57:53 WARNING[96234416]: app_dial.c:629 dial_exec: > Could not find macro to which we should jump. Dec 2 15:57:53 > WARNING[96234416]: app_dial.c:636 dial_exec: Macro flag set > without trailing ') > > Is there a patch that would allow me to do this? Or is there > a way to get the Zap channel name that requested the Dial on > the outbound trunk from within the macro? > > Regards, > > Shaun Tierney >This email and any attached files are confidential and copyright protected. If you are not the addressee, any dissemination, distribution or copying of this communication is strictly prohibited. Unless otherwise expressly agreed in writing, nothing stated in this communication shall be legally binding.
http://bugs.digium.com/bug_view_page.php?bug_id=0002905> This email and any attached files are confidential and copyright > protected. If you are not the addressee, any dissemination, distribution > or copying of this communication is strictly prohibited. Unless otherwise > expressly agreed in writing, nothing stated in this communication shall be > legally binding.FYI these types of disclaimers ARE STUPID... And crack me up when I see them... bkw
When terminating calls on * via Analog circuits the Caller Name gets placed in the callerid field. This does not appear to be the case with ISDN PRI circuits. Does anyone know if Caller Name (CNAM) can be delivered in ISDN PRI in addition to Caller Telephone Number? -- Mike
Michael B. Murdock wrote:> When terminating calls on * via Analog circuits the Caller Name gets placed > in the callerid field. This does not appear to be the case with ISDN PRI > circuits. Does anyone know if Caller Name (CNAM) can be delivered in ISDN > PRI in addition to Caller Telephone Number?Yes, your telco will need to configure your PRI as NI-2 signaling, and you will need to wait at least one second on incoming calls before doing anything that requires the Calling Name information (it is not delivered in the initial Call Setup packet, it is delivered in an additional packet later in the call).
On Fri, 2004-12-03 at 10:37 -0600, Michael B. Murdock wrote:> When terminating calls on * via Analog circuits the Caller Name gets placed > in the callerid field. This does not appear to be the case with ISDN PRI > circuits. Does anyone know if Caller Name (CNAM) can be delivered in ISDN > PRI in addition to Caller Telephone Number?You may need to wait a moment as the name is sent after call setup. Check your CDRs and see if you see the names in there. We have an app that we had to put a wait in so we would get the name before starting the AGI up as the AGI only cares about the data it has in hand at start up time. -- Steven Critchfield <critch@basesys.com>
I forgot to mention that the switch is a Lucent 5ESS... Is NI-2 available on the 5ESS? -- Mike> Michael B. Murdock wrote: > > When terminating calls on * via Analog circuits the Caller Name getsplaced> > in the callerid field. This does not appear to be the case with ISDN PRI > > circuits. Does anyone know if Caller Name (CNAM) can be delivered inISDN> > PRI in addition to Caller Telephone Number? > > Yes, your telco will need to configure your PRI as NI-2 signaling, and > you will need to wait at least one second on incoming calls before doing > anything that requires the Calling Name information (it is not delivered > in the initial Call Setup packet, it is delivered in an additional > packet later in the call). > _______________________________________________ > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >