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