<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
for this t1 my settings are <br>
d4,ami<br>
sf<br>
em_w<br>
<br>
I was starting to suspect that em_w didn't support ANI.. I was hoping
that this wasn't the case as the telco told me to use e&m wink.<br>
<br>
I just went through "wink" nightmare with XO and i'm dreading repeating
it.. I'll give it a try, thanks!<br>
<br>
BJ Weschke wrote:
<blockquote cite="mid:472B3CEE.5050909@gmail.com" type="cite">
<pre wrap="">Dan Casey wrote:
</pre>
<blockquote type="cite">
<pre wrap="">does anyone know how to route a call coming in with ANI*DNIS*
Oct 31 12:47:41 VERBOSE[30056] logger.c: -- Executing
Set("Zap/49-1", "DID=1231234*4812*") in new stack
I tried making a route for _.*4812* but that matched everything rather
then just the dnis i wanted.. any ideas?
I would preferably like pass the callerid along to my extensions, but
for now the important thing is routing.
</pre>
</blockquote>
<pre wrap=""><!----> This shouldn't be necessary. I think with the correct signaling set in
zaptel.conf, chan_zap should be doing the parsing work for you. What
signaling are you set for now? You might want Feature Group D vs. EM_Wink?
_______________________________________________
--Bandwidth and Colocation Provided by <a class="moz-txt-link-freetext" href="http://www.api-digital.com">http://www.api-digital.com</a>--
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
<a class="moz-txt-link-freetext" href="http://lists.digium.com/mailman/listinfo/asterisk-users">http://lists.digium.com/mailman/listinfo/asterisk-users</a>
</pre>
</blockquote>
</body>
</html>