<br><font size=2 face="sans-serif">If it's the voltage sensor that enables
caller id....Why no support for MGCP? </font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>"Matt Slaga \(US\)"
<Matt.Slaga@us.didata.com></b> </font>
<br><font size=1 face="sans-serif">Sent by: cisco-voip-bounces@puck.nether.net</font>
<p><font size=1 face="sans-serif">03/19/2007 01:31 PM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">"Paul Choi" <asobihoudai@yahoo.com>,
<cisco-voip@puck.nether.net></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: [cisco-voip] caller id already in?</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt>No, you are correct. The second gen FXO cards
should have the voltage<br>
sensor necessary for caller-id.<br>
<br>
You need to enable it under the voice-port x/x/x - caller-id enable.<br>
<br>
<br>
<br>
-----Original Message-----<br>
From: cisco-voip-bounces@puck.nether.net<br>
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Paul Choi<br>
Sent: Monday, March 19, 2007 1:07 PM<br>
To: cisco-voip@puck.nether.net<br>
Subject: Re: [cisco-voip] caller id already in?<br>
<br>
So this<br>
<br>
NAME: "2nd generation four port FXO voice interface<br>
daughtercard on Slot 0 SubSlot 3", DESCR: "2nd<br>
generation four port FXO voice interface daughtercard"<br>
PID: VIC2-4FXO , VID: V01 , SN: FOC10390M7A<br>
<br>
is not going to enable caller-id?<br>
<br>
This is frustrating. I would like the customer to have<br>
caller-id whereever possible.<br>
<br>
--- "Matt Slaga (US)" <Matt.Slaga@us.didata.com><br>
wrote:<br>
<br>
> It requires an FXO-M1 and H323, unless Cisco has<br>
> fixed this in later<br>
> versions. The M1 is definitely required in the US.<br>
> <br>
> <br>
> <br>
> <br>
> <br>
> -----Original Message-----<br>
> From: cisco-voip-bounces@puck.nether.net<br>
> [mailto:cisco-voip-bounces@puck.nether.net] On<br>
> Behalf Of Voll, Scott<br>
> Sent: Monday, March 19, 2007 11:57 AM<br>
> To: Paul Choi; Adam; cisco-voip@puck.nether.net<br>
> Subject: Re: [cisco-voip] caller id already in?<br>
> <br>
> My understanding is that it works only on h323.<br>
> <br>
> Scott<br>
> <br>
> -----Original Message-----<br>
> From: cisco-voip-bounces@puck.nether.net<br>
> [mailto:cisco-voip-bounces@puck.nether.net] On<br>
> Behalf Of Paul Choi<br>
> Sent: Saturday, March 17, 2007 5:07 PM<br>
> To: Adam; cisco-voip@puck.nether.net<br>
> Subject: Re: [cisco-voip] caller id already in?<br>
> <br>
> I don't recall ever seen caller ID work over FXO<br>
> ports<br>
> before. Please let me know if you get it working.<br>
> <br>
> --- Adam <cisco@adman.net> wrote:<br>
> <br>
> > I have site with an FXO port that will not receive<br>
> > caller id<br>
> > information. I watched a "debug vpm signal" and<br>
> > found an entry that<br>
> > said "Error caller id already in progress" and<br>
> > cannot work out what<br>
> > that means. A copy of the debug output is included<br>
> > below.<br>
> > <br>
> > Any suggestions?<br>
> > <br>
> > -Adam<br>
> > <br>
> > Mar 16 15:05:49.888: htsp_process_event: [1/0/0,<br>
> > FXOLS_ONHOOK, E_DSP_SIG_0000]fx<br>
> > ols_onhook_ringing<br>
> > Mar 16 15:05:49.888: htsp_timer3 - 5600 msec<br>
> > Mar 16 15:05:49.888: [1/0/0]<br>
> > htsp_start_caller_id_rx. Error caller id already<br>
> in<br>
> > progress<br>
> > Mar 16 15:05:49.888: htsp_timer - 125 msec<br>
> > Mar 16 15:05:50.016: htsp_process_event: [1/0/0,<br>
> > FXOLS_WAIT_RING_MIN, E_HTSP_EVE<br>
> > NT_TIMER]fxols_wait_ring_min_timer<br>
> > Mar 16 15:05:50.016: htsp_timer - 10000 msec<br>
> > Mar 16 15:05:51.979: htsp_process_event: [1/0/0,<br>
> > FXOLS_RINGING, E_DSP_SIG_0100]<br>
> > Mar 16 15:05:51.979: fxols_ringing_not<br>
> > Mar 16 15:05:51.979: htsp_timer_stop<br>
> > Mar 16 15:05:51.979: htsp_timer_stop3<br>
> htsp_setup_ind<br>
> > Mar 16 15:05:51.979: [1/0/0]<br>
> > get_fxo_caller_id:Caller ID receive failed. <br>
> parseC<br>
> > allerIDString:no data.<br>
> > Mar 16 15:05:51.979: [1/0/0] get_local_station_id<br>
> > calling num= calling name= cal<br>
> > ling time=03/16 15:05 orig called=<br>
> > Mar 16 15:05:51.987: htsp_process_event: [1/0/0,<br>
> > FXOLS_WAIT_SETUP_ACK, E_HTSP_SE<br>
> > TUP_ACK]<br>
> > Mar 16 15:05:51.987: fxols_wait_setup_ack:<br>
> > Mar 16 15:05:51.987: [1/0/0] set signal state =<br>
> 0xC<br>
> > timestamp = 0fxols_check_aut<br>
> > o_call<br>
> > Mar 16 15:05:52.003: htsp_process_event: [1/0/0,<br>
> > FXOLS_PROCEEDING, E_HTSP_PROCEE<br>
> > DING]fxols_offhook_proc<br>
> > Mar 16 15:05:52.003: htsp_timer - 120000<br>
> > msechtsp_alert_notify<br>
> > Mar 16 15:05:52.092: htsp_process_event: [1/0/0,<br>
> > FXOLS_PROCEEDING, E_HTSP_ALERT]<br>
> ><br>
><br>
fxols_offhook_alerthtsp_call_service_msghtsp_call_service_msg<br>
> > not EFXS (2)<br>
> > Mar 16 15:05:52.176: htsp_process_event: [1/0/0,<br>
> > FXOLS_PROCEEDING, E_DSP_SIG_011<br>
> > 0]fxols_rvs_battery<br>
> > Mar 16 15:05:52.176: htsp_timer_stop2<br>
> > htsp_call_service_msghtsp_call_service_msg<br>
> > not EFXS (2)<br>
> > Mar 16 15:05:52.260: htsp_call_bridged invoked<br>
> > Mar 16 15:05:52.268: htsp_process_event: [1/0/0,<br>
> > FXOLS_PROCEED_RVS_BT, E_HTSP_CO<br>
> > NNECT]fxols_offhook_connect<br>
> > Mar 16 15:05:52.272: htsp_timer_stop<br>
> > Mar 16 15:05:52.468: htsp_process_event: [1/0/0,<br>
> > FXOLS_CONNECT, E_HTSP_VOICE_CUT<br>
> > _THROUGH]fxols_connect_proc_voice<br>
> > _______________________________________________<br>
> > cisco-voip mailing list<br>
> > cisco-voip@puck.nether.net<br>
> ><br>
> https://puck.nether.net/mailman/listinfo/cisco-voip<br>
> > <br>
> <br>
> <br>
> <br>
> <br>
><br>
________________________________________________________________________<br>
> ____________<br>
> 8:00? 8:25? 8:40? Find a flick in no time <br>
> with the Yahoo! Search movie showtime shortcut.<br>
> http://tools.search.yahoo.com/shortcuts/#news<br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> cisco-voip@puck.nether.net<br>
> https://puck.nether.net/mailman/listinfo/cisco-voip<br>
> <br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> cisco-voip@puck.nether.net<br>
> https://puck.nether.net/mailman/listinfo/cisco-voip<br>
> -----------------------------------------<br>
> Disclaimer:<br>
> <br>
> This e-mail communication and any attachments may<br>
> contain<br>
> confidential and privileged information and is for<br>
> use by the<br>
> designated addressee(s) named above only. If you<br>
> are not the<br>
> intended addressee, you are hereby notified that you<br>
> have received<br>
> this communication in error and that any use or<br>
> reproduction of<br>
> this email or its contents is strictly prohibited<br>
> and may be<br>
> unlawful. If you have received this communication<br>
> in error, please<br>
> notify us immediately by replying to this message<br>
> and deleting it<br>
> from your computer. Thank you.<br>
> <br>
<br>
<br>
<br>
<br>
________________________________________________________________________<br>
____________<br>
The fish are biting. <br>
Get more visitors on your site using Yahoo! Search Marketing.<br>
http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php<br>
_______________________________________________<br>
cisco-voip mailing list<br>
cisco-voip@puck.nether.net<br>
https://puck.nether.net/mailman/listinfo/cisco-voip<br>
-----------------------------------------<br>
Disclaimer:<br>
<br>
This e-mail communication and any attachments may contain<br>
confidential and privileged information and is for use by the<br>
designated addressee(s) named above only. If you are not the<br>
intended addressee, you are hereby notified that you have received<br>
this communication in error and that any use or reproduction of<br>
this email or its contents is strictly prohibited and may be<br>
unlawful. If you have received this communication in error, please<br>
notify us immediately by replying to this message and deleting it<br>
from your computer. Thank you.<br>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
cisco-voip@puck.nether.net<br>
https://puck.nether.net/mailman/listinfo/cisco-voip<br>
</tt></font>
<br>