So are you saying that * does not see the callerid but it should. Is this a possible bug in the callerid application. RIght now I am seeing that callerid isn't recognized 100% of the time (or possibly not transmitted) when I receive calls from VP Connect. If I do a NoOp(${CALLERIDNUM}) on incoming calls, a lot of times it comes back UNAVAILABLE when I know the person calling has callerid being transmitted. Just trying to figure out if this a bug in * or with VP.
This could also be related to why PrivacyManager is not working properly. * has received the callerid info from the carrier but couldn't translate it for some reason, so it says that callerid is present but then sets it to UNAVAILABLE. Just a thought. On Tue, 25 Jan 2005 10:43:57 -0500, Joseph Finley <[EMAIL PROTECTED]> wrote: > Well, it is also happens with Zaptel. I've had times where CallerID > does not pickup and prompts the user to enter their phone number. They > will hang up and call right back and it works. This only happens about > 15% of the time though. > > _______________________________________________ > 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 > _______________________________________________ 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