Hello , I have a old TDM04B card and newly bought TDM04B card. iam have a asterisk,zaptel verison 1.0.7. now i need to add another card to my server. then i bought a new TDM04B card.and changed the zapte.conf..but card is not loading. when i type zttool . it shows only one board. then i used zaptel 1.0.9 and asterisk verison 1.0.9 on another server and gave a try. its working properly. my problem is i cant upgrade all my servers to 1.0.9 . according ot my knowledge asterisk 1.0.7 IAX2 and IAX2 1.0.9 is not compatible...pls correct me if iam wrong. do i have another way to use this new TDM04B card with aterisk,zaptel. 1.0.7 version . OR can i use 1.0.7 on one end and othe end 1.0.9 ?? is it make any problem..to my IP Calls Via IAX2 channel . Thanks in advance Tharanga
On Fri, Oct 28, 2005 at 10:19:54AM +0600, Tharanga wrote:> do i have another way to use this new TDM04B card with aterisk,zaptel. 1.0.7 > version . > OR can i use 1.0.7 on one end and othe end 1.0.9 ?? is it make any > problem..to my IP Calls Via IAX2 channel .You can upgrade zaptel alone. No need to upgrade asterisk. Alternatively, see the diff between 1.0.8 and 1.0.9 . (IIRC) and try to apply it manually to your zaptel, and rebuild. -- Tzafrir Cohen | tzafrir@jbr.cohens.org.il | VIM is http://tzafrir.org.il | | a Mutt's tzafrir@cohens.org.il | | best ICQ# 16849755 | | friend
Well, I am batting close to zero where responses to my questions are
concerned, but I suppose I will just keep swinging.
I just set up an account with callpacket.com, and noticed that on
incoming calls through this provider the values of CALLERID(name) and
CALLERID(num) are "%23%23%23%23%23%23%23%23%23%23" when the caller
has either blocked callerid (tested with *67), or, apparently, sent
values that are unexpected (tested via friend who is, for whatever
reason, doing SetCallerID("caller 6398A" <>) on his outbound
calls).
I have "speak caller ID" macro that does a system() call to a script
on the local machine, and I have been tinkering with ways of handling
the different possible strings in some reasonably intelligent way.
My question is -- is %23 the escape for the # character here, as I
suspect, and if so, is there a way I can tell asterisk to interpret
it as such, or do I need to convert it back on my own?
Is the "%23%23%23%23%23%23%23%23%23%23" (or "###########")
any kind
of an industry standard string, that evaluates to something sensible
on a consumer CID display, or is it just some arbitrary barf that
callpacket has chosen to send in those cases?
Thanks for any info.
lyd