UC520 the CO line does not disconnect in Saudi arabia

[majid omeir]

I went to today for implementation with client for uc520 when user call then hang up the  CO line does  not disconnect  and I try all supervision  signal but does not work really , the sad story Panasonic pbx 300$ cost What the customer has now  it disconnect the line properly I cannot tell the customer this provider problem as he see his old technology Panasonic works fine

Please help , I start lose confidante in  selling cisco uc solutions

[David Trad]

Hi Majid,

When I was working in Dubai I seen this problem a lot but was able to resolve it after talking with Etisalate, you may need to ask STC what signaling format they prefer and or use and then look at what the UC520 can support.

Can you post the voice-port configuration?

Also can you please explain the scenario a little better, for instance:

• Lines lock-up on outgoing calls and or incoming calls
• Lines only lock-up when a call comes in and it is forwarded to another external number, this means you have two PSTN lines being used up
• If the (B) end ends the call the channel clears (Tears Down) but the (A) end on the system does not?

As much information you can provide on the issue even though it is a common one would be much appreciated, also if you can capture a debug of the call, this would go a long way, you can capture it by running the following command "ROUTER# term mon" and then run "ROUTER# debug vpm singal" and then show us the output of a call where the line locks up.

Also is this happening on every single call or just some?

And do you have SSH access to this system so we can do some testing? And is this system a pure CCA build or is it a CLI build? Maybe even a Hybrid build??

Cheers,

David.

[majid omeir]

HI david thank for support, i called for as sson as i heared the auttoattandante message i just close the line

debug result

UC520#debug vpm sign  
UC520#debug vpm signal
Voice Port Module signaling debugging is enabled
UC520#
001273: May 17 09:44:34.017: htsp_process_event: [0/1/0, FXOLS_ONHOOK, E_DSP_SIG_0000]fxols_onhook_ringing
001274: May 17 09:44:34.017: htsp_timer - 125 msec
001275: May 17 09:44:34.145: htsp_process_event: [0/1/0, FXOLS_WAIT_RING_MIN, E_HTSP_EVENT_TIMER]fxols_wait_ring_min_timer
001276: May 17 09:44:34.145: htsp_timer - 10000 msec
001277: May 17 09:44:34.145: htsp_timer3 - 5600 msec
001278: May 17 09:44:34.145: [0/1/0] htsp_start_caller_id_rx:BELLCORE
001279: May 17 09:44:34.145: htsp_start_caller_id_rx create dsp_stream_manager
001280: May 17 09:44:34.145: [0/1/0] htsp_dsm_create_success  returns 1
001281: May 17 09:44:35.309: htsp_process_event: [0/1/0, FXOLS_RINGING, E_DSP_SIG_0100]
001282: May 17 09:44:35.309: fxols_ringing_not
001283: May 17 09:44:35.309: htsp_timer_stop
001284: May 17 09:44:35.309: htsp_timer - 10000 msec
001285: May 17 09:44:39.745: htsp_process_event: [0/1/0, FXOLS_RINGING, E_HTSP_EVENT_TIMER3]fxols_snoop_clid_stop
001286: May 17 09:44:39.745: htsp_timer_stop3
001287: May 17 09:44:39.833: htsp_process_event: [0/1/0, FXOLS_RINGING, E_DSP_SIG_0000]
001288: May 17 09:44:41.121: htsp_process_event: [0/1/0, FXOLS_RINGING, E_DSP_SIG_0100]
001289: May 17 09:44:41.121: fxols_ringing_not
001290: May 17 09:44:41.121: htsp_timer_stop
001291: May 17 09:44:41.121: htsp_timer_stop3
001292: May 17 09:44:41.121: [0/1/0] htsp_stop_caller_id_rx. message length 0htsp_setup_ind
001293: May 17 09:44:41.121: [0/1/0] get_fxo_caller_id:Caller ID receive failed.  parseCallerIDString:no data.
001294: May 17 09:44:41.121: [0/1/0] get_local_station_id calling num= calling name= calling time=05/17 02:44  orig called=
001295: May 17 09:44:41.125: [0/1/0] htsp_dsm_close_done
001296: May 17 09:44:41.125: htsp_process_event: [0/1/0, FXOLS_WAIT_SETUP_ACK, E_HTSP_SETUP_ACK]
001297: May 17 09:44:41.125: fxols_wait_setup_ack:
001298: May 17 09:44:41.125: htsp_timer - 6000 msec
001299: May 17 09:44:41.133: htsp_process_event: [0/1/0, FXOLS_PROCEEDING, E_HTSP_PROCEEDING]fxols_offhook_prochtsp_alert_notify
001300: May 17 09:44:41.341: htsp_process_event: [0/1/0, FXOLS_PROCEEDING, E_HTSP_ALERT]fxols_offhook_alert
001301: May 17 09:44:41.393: htsp_call_bridged invoked
001302: May 17 09:44:41.397: htsp_process_event: [0/1/0, FXOLS_PROCEEDING, E_HTSP_CONNECT]fxols_offhook_connect
001303: May 17 09:44:41.397: [0/1/0] set signal state = 0xC timestamp = 0
001304: May 17 09:44:41.397: htsp_timer_stop
001305: May 17 09:44:41.405: htsp_process_event: [0/1/0, FXOLS_CONNECT, E_HTSP_VOICE_CUT_THROUGH]fxols_connect_proc_voice
001306: May 17 09:45:01.121: htsp_call_bridged invoked
001307: May 17 09:45:01.129: htsp_timer_stop3 htsp_setup_req
001308: May 17 09:45:01.133: htsp_process_event: [50/0/33.1, EFXS_ONHOOK, E_HTSP_SETUP_REQ]efxs_onhook_setup
001309: May 17 09:45:01.133: htsp_ephone_start_caller_id_tx calling num=601 calling name = called num=AA601A4904 orig called num=
001310: May 17 09:45:01.133: [50/0/33.1] set signal state = 0x0 timestamp = 0
001311: May 17 09:45:01.137: efxs_onhook_setup: local target is available
htsp_alert
001312: May 17 09:45:01.149: htsp_process_event: [0/1/0, FXOLS_CONNECT, E_HTSP_VOICE_CUT_THROUGH]fxols_connect_proc_voice
001313: May 17 09:45:01.149: htsp_process_event: [0/1/0, FXOLS_CONNECT, E_HTSP_VOICE_CUT_THROUGH]fxols_connect_proc_voice
001314: May 17 09:45:01.153: htsp_process_event: [0/1/0, FXOLS_CONNECT, E_HTSP_VOICE_CUT_THROUGH]fxols_connect_proc_voicehtsp_call_service_msghtsp_call_service_msg not EFXS (2)
001315: May 17 09:45:09.141: htsp_timer_stop3
001316: May 17 09:45:09.145: htsp_process_event: [50/0/33.1, EFXS_WAIT_OFFHOOK, E_HTSP_RELEASE_REQ]efxs_waitoff_release
001317: May 17 09:45:09.145: [50/0/33.1] set signal state = 0x4 timestamp = 0
001318: May 17 09:45:09.153: htsp_timer_stop3 htsp_setup_req
001319: May 17 09:45:09.153: htsp_process_event: [50/0/37.1, EFXS_ONHOOK, E_HTSP_SETUP_REQ]efxs_onhook_setup
001320: May 17 09:45:09.153: htsp_ephone_start_caller_id_tx calling num=601 calling name = called num=AA601A4905 orig called num=
001321: May 17 09:45:09.157: [50/0/37.1] set signal state = 0x0 timestamp = 0
001322: May 17 09:45:09.157: efxs_onhook_setup: local target is available
htsp_alerthtsp_call_feature:feature 25
htsp_call_feature: caller id enable 0x3 call_connected 0
001323: May 17 09:45:09.165: htsp_process_event: [50/0/37.1, EFXS_WAIT_OFFHOOK, E_HTSP_CALLERID_WAITING]
001324: May 17 09:45:09.165: efxs_callerid_update
001325: May 17 09:45:09.165: efxs_callerid_update process caller_id_string
001326: May 17 09:45:09.165: efxs_callerid_update process caller_id_string OK
001327: May 17 09:45:09.165: efxs_callerid_update number= [601] name= []htsp_call_service_msghtsp_call_service_msg not EFXS (2)
001328: May 17 09:45:17.161: htsp_timer_stop3
001329: May 17 09:45:17.165: htsp_process_event: [50/0/37.1, EFXS_WAIT_OFFHOOK, E_HTSP_RELEASE_REQ]efxs_waitoff_release
001330: May 17 09:45:17.165: [50/0/37.1] set signal state = 0x4 timestamp = 0
001331: May 17 09:45:17.173: htsp_timer_stop3 htsp_setup_req
001332: May 17 09:45:17.177: htsp_process_event: [50/0/35.1, EFXS_ONHOOK, E_HTSP_SETUP_REQ]efxs_onhook_setup
001333: May 17 09:45:17.177: htsp_ephone_start_caller_id_tx calling num=601 calling name = called num=AA601A4900 orig called num=
001334: May 17 09:45:17.177: [50/0/35.1] set signal state = 0x0 timestamp = 0
001335: May 17 09:45:17.177: efxs_onhook_setup: local target is available
htsp_alerthtsp_call_feature:feature 25
htsp_call_feature: caller id enable 0x3 call_connected 0
001336: May 17 09:45:17.185: htsp_process_event: [50/0/35.1, EFXS_WAIT_OFFHOOK, E_HTSP_CALLERID_WAITING]
001337: May 17 09:45:17.185: efxs_callerid_update
001338: May 17 09:45:17.185: efxs_callerid_update process caller_id_string
001339: May 17 09:45:17.185: efxs_callerid_update process caller_id_string OK
001340: May 17 09:45:17.185: efxs_callerid_update number= [601] name= []htsp_call_service_msghtsp_call_service_msg not EFXS (2)
001341: May 17 09:45:25.185: htsp_timer_stop3
001342: May 17 09:45:25.185: htsp_process_event: [50/0/35.1, EFXS_WAIT_OFFHOOK, E_HTSP_RELEASE_REQ]efxs_waitoff_release
001343: May 17 09:45:25.185: [50/0/35.1] set signal state = 0x4 timestamp = 0
001344: May 17 09:45:25.193: htsp_timer_stop3 htsp_setup_req
001345: May 17 09:45:25.197: htsp_process_event: [50/0/38.1, EFXS_ONHOOK, E_HTSP_SETUP_REQ]efxs_onhook_setup
001346: May 17 09:45:25.197: htsp_ephone_start_caller_id_tx calling num=601 calling name = called num=AA601A4901 orig called num=
001347: May 17 09:45:25.197: [50/0/38.1] set signal state = 0x0 timestamp = 0
001348: May 17 09:45:25.197: efxs_onhook_setup: local target is available
htsp_alerthtsp_call_feature:feature 25
htsp_call_feature: caller id enable 0x3 call_connected 0
001349: May 17 09:45:25.205: htsp_process_event: [50/0/38.1, EFXS_WAIT_OFFHOOK, E_HTSP_CALLERID_WAITING]
001350: May 17 09:45:25.205: efxs_callerid_update
001351: May 17 09:45:25.205: efxs_callerid_update process caller_id_string
001352: May 17 09:45:25.205: efxs_callerid_update process caller_id_string OK
001353: May 17 09:45:25.205: efxs_callerid_update number= [601] name= []htsp_call_service_msghtsp_call_service_msg not EFXS (2)
001354: May 17 09:45:33.201: htsp_timer_stop3
001355: May 17 09:45:33.205: htsp_process_event: [50/0/38.1, EFXS_WAIT_OFFHOOK, E_HTSP_RELEASE_REQ]efxs_waitoff_release
001356: May 17 09:45:33.205: [50/0/38.1] set signal state = 0x4 timestamp = 0
001357: May 17 09:45:33.213: htsp_timer_stop3 htsp_setup_req
001358: May 17 09:45:33.217: htsp_process_event: [50/0/34.1, EFXS_ONHOOK, E_HTSP_SETUP_REQ]efxs_onhook_setup
001359: May 17 09:45:33.217: htsp_ephone_start_caller_id_tx calling num=601 calling name = called num=AA601A4903 orig called num=
001360: May 17 09:45:33.217: [50/0/34.1] set signal state = 0x0 timestamp = 0
001361: May 17 09:45:33.217: efxs_onhook_setup: local target is available
htsp_alerthtsp_call_feature:feature 25
htsp_call_feature: caller id enable 0x3 call_connected 0
001362: May 17 09:45:33.225: htsp_process_event: [50/0/34.1, EFXS_WAIT_OFFHOOK, E_HTSP_CALLERID_WAITING]
001363: May 17 09:45:33.225: efxs_callerid_update
001364: May 17 09:45:33.225: efxs_callerid_update process caller_id_string
001365: May 17 09:45:33.225: efxs_callerid_update process caller_id_string OK
001366: May 17 09:45:33.225: efxs_callerid_update number= [601] name= []htsp_call_service_msghtsp_call_service_msg not EFXS (2)
UC520#
UC520#
UC520#
UC520#undebug
001367: May 17 09:45:41.221: htsp_timer_stop3
001368: May 17 09:45:41.225: htsp_process_event: [50/0/34.1, EFXS_WAIT_OFFHOOK, E_HTSP_RELEASE_REQ]efxs_waitoff_release
001369: May 17 09:45:41.225: [50/0/34.1] set signal state = 0x4 timestamp = 0
001370: May 17 09:45:41.233: htsp_timer_stop3 htsp_setup_req
001371: May 17 09:45:41.233: htsp_process_event: [50/0/33.1, EFXS_ONHOOK, E_HTSP_SETUP_REQ]efxs_onhook_setup
001372: May 17 09:45:41.233: htsp_ephone_start_caller_id_tx calling num=601 calling name = called num=AA601A4904 orig called num=
001373: May 17 09:45:41.237: [50/0/33.1] set signal state = 0x0 timestamp = 0 all
All possible debugging has been turned off
UC520#
001374: May 17 09:45:41.237: efxs_onhook_setup: local target is available
htsp_alerthtsp_call_feature:feature 25
htsp_call_feature: caller id enable 0x3 call_connected 0
001375: May 17 09:45:41.241: htsp_process_event: [50/0/33.1, EFXS_WAIT_OFFHOOK, E_HTSP_CALLERID_WAITING]
001376: May 17 09:45:41.241: efxs_callerid_update
001377: May 17 09:45:41.245: efxs_callerid_update process caller_id_string
001378: May 17 09:45:41.245: efxs_callerid_update process caller_id_string OK
001379: May 17 09:45:41.245: efxs_callerid_update number= [601] name= []htsp_call_service_msghtsp_call_service_msg not EFXS (2)

see it will contine like that for ever

config for port

voice-port 0/1/0
trunk-group ALL_FXO 64
cptone SA
connection plar opx 401
description Configured by CCA 4 FXO-0/1/0-Custom-AA
caller-id enable
!

this problem happens when ppl call from outside to uc520 PSTN lines

reagrds,

[David Trad]

Hi Majid,

You have good timing

I'll give you a quick response as I am ready to wind down in front of the TV and hope to fall a sleep real soon

The logs were great and yes I can see that the call clear down procedure is not happening how it should be.

Lets make some modifications to your Voice-Port and do some testing, when I wake up tomorrow I will look at your response and we can work it from there.

Please change your configuration:

voice-port 0/1/0
 trunk-group ALL_FXO 64
 cptone SA
 connection plar opx 401
 description Configured by CCA 4 FXO-0/1/0-Custom-AA
 caller-id enable

To this configuration please:

voice-port 0/1/0
 trunk-group ALL_FXO 64
 supervisory disconnect dualtone mid-call
 compand-type a-law
 cptone SA
 timeouts call-disconnect 3
 timeouts wait-release 3
 connection plar opx immediate 401
 impedance complex1
 description Configured by CCA 4 FXO- 0/1/0-BG
 caller-id enable

You can copy and paste the above directly into the CLI in configuration mode, however make sure you leave the description as it is, I added that in just incase you use CCA to configure the system, this way the above configuration does resemble what CCA would do.

If this still does not work, we will need to play around with the supervisory disconnect until we get the right one for Saudi, however I am confident the above will work, although the only thing I am not all too certain of is the compand-type, my memory is a little vague at the moment but STC might actually be uLaw, you may want to ask them about this but regardless give it a try anyway

I truly hope this resolves your issue.

Cheers,

David.

[David Trad]

[UPDATE]

Spent about 3 hours debugging the issue last night with Majid and we discovered the following:

• IN order to obtain Caller-ID you have to change the CPTONE from "SA" progress tone to "BR", this made no sense but it worked, it must be something to do with STC and the way they have their PSTN lines configured to operate at an exchange level
  
  
• Changing the CPTON to "BR" then required you to add in specific alerting commands to allow the caller-id to pass through otherwise it would not be presented, the following is a sample code:
  
  

  voice-port 0/3/3
   trunk-group ALL_FXO 64
   supervisory disconnect dualtone mid-call
   compand-type a-law
   cptone BR
   timeouts call-disconnect 3
   timeouts wait-release 3
   connection plar opx immediate XXX
   impedance complex1
   description Configured by CCA 4 FXO- 0/3/3-BG
   caller-id enable
   caller-id alerting line-reversal
   caller-id alerting dsp-pre-allocate

  
  
• Everything listed in BOLD and RED are important in order for it to work
• FXO lines going straight through to an AA and then pushing the call to a blast group yields some unwanted results, the success rate of a successful call clear down (Tear Down) is hit and miss and at times can take longer than 10 seconds to clear down, or just lock the port up, however the above configuration minimized the issue to a certain degree
• FXO lines passed directly to an extension would clear down immediately or within the designated timeouts as set on the voice-port configuration

I think again this highlights an annoying problem when replacing a KTS/Analogue system with an IP-PBX system, whilst the Analogue system can clear all analogue lines down immediately the UC's are quite miserable at doing this, they fail on many aspects of clearing a line and result the system in semi locked ports or full locked ports, and given that in Saudi Arabia ISDN/BRI services are vastly more expensive than FXO/PSTN services, there is very little options to upgrade a client unless they have an ICT budget that can afford the migration.

Why the only the Brazil call progress tone would work is beyond me, given that there is a Saudi progress tone on the system, have Cisco got this wrong? STC have not changed their network in many years, has Cisco done any tests with their analogue settings within Saudi Arabia (STC in particular) ?

Regardless the system is semi resolved and it had been debugged to death, over 15 different config combinations were tested last night to finally arrive to the above settings, I truly hope this helps someone else within that region and saves them some hassles... NOTE: This had to be configured using CLI we just could not get the configuration right using CCA.

Cheers,

David.

[paolo bevilacqua]

David,

your findings are coherent with the general experience: Cisco's support for clid and disconnect detection are vastly inferior to those of any decent PBX. And yes it appears that cisco doesn't care much and have done very testing in the area. So getting these to work is often a nightmare.

Altough in this case I understand the BR tones worked for you, if you make new findings and care about helping the "community", you can update the tones you found at: http://www.3amsystems.com/wireline/tone-search.htm

One observation: compand-type has absolutely no effect on analog circuits, actually Cisco should remove the command from CLI altogether.

[David Trad]

Unwarranted post.

Suffice to say, it would be best to avoid an analogue trunk altogether. It would be wrong to think that Cisco appliances are the only one to suffer from these issues, I work around LG-Nortel, Avaya and Samsung systems, of which each one of them share similar problems, they all just handle them in there own way.

I do my best these days to get the sales guys to upgrade the clients to ISDN/BRI or PRI trunks, less hassles and more functionality, FXO/PSTN trunks are a thorn in my side no matter what system is used.

Anyway Majid's problem was handled by investigating the VPM signaling, and making the adjustments accordingly, no tones were captured or even listened to, he is in Saudi and I am In Australia everything was done via remote desktop.

It is up to Majid now if he wants to get support to capture tones and or signaling and for them to make the appropriate changes to the system.

Cheers,

David.

Posted from my mobile device.

[paolo bevilacqua]

Suffice to say, it would be best to avoid an analogue trunk altogether. It would be wrong to think that Cisco appliances are the only one to suffer from these issues, I work around LG-Nortel, Avaya and Samsung systems, of which each one of them share similar problems, they all just handle them in there own way.
I do my best these days to get the sales guys to upgrade the clients to ISDN/BRI or PRI trunks, less hassles and more functionality, FXO/PSTN trunks are a thorn in my side no matter what system is used.

Words of wisdom. But, as you noted before, sometime there is no alternative to good old FXO.

Anyway Majid's problem was handled by investigating the VPM signaling, and making the adjustments accordingly, no tones were captured or even listened to, he is in Saudi and I am In Australia everything was done via remote desktop
It is up to Majid now if he wants to get support to capture tones and or signaling and for them to make the appropriate changes to the system.

Yes, with a little patience and ingenuity, most problems can be fixed no matter where one sits. The real problem is when the end-user expect the product to work perfectly just out of the box, but doesn't want to pay for the expertise needed.

[edwincharles]

hello david,

i have the problem

• Lines only lock-up when a call comes in and it is forwarded to another external number, this means you have two PSTN lines being used up
  

debug as below

UC_iSupply#sh voice port summary

IN OUT

PORT CH SIG-TYPE ADMIN OPER STATUS STATUS EC

=============== == ============ ===== ==== ======== ======== ==

0/0/0 -- fxs-ls up dorm on-hook idle y

0/0/1 -- fxs-ls up dorm on-hook idle y

0/0/2 -- fxs-ls up dorm on-hook idle y

0/0/3 -- fxs-ls up dorm on-hook idle y

0/1/0 -- fxo-ls up dorm idle on-hook y

0/1/1 -- fxo-ls up dorm idle on-hook y

0/1/2 -- fxo-ls up dorm idle on-hook y

0/1/3 -- fxo-ls up dorm idle on-hook y

0/4/0 -- moh-imd up up idle seized y

50/0/9 1 efxs up up off-hook idle y

50/0/293 1 efxs up dorm on-hook idle y

50/0/293 2 efxs up dorm on-hook idle y

50/0/294 1 efxs up dorm on-hook idle y

50/0/294 2 efxs up dorm on-hook idle y

50/0/295 1 efxs up dorm on-hook idle y

50/0/295 2 efxs up dorm on-hook idle y

50/0/296 1 efxs up dorm on-hook idle y

50/0/296 2 efxs up dorm on-hook idle y

50/0/297 1 efxs up dorm on-hook idle y

50/0/297 2 efxs up dorm on-hook idle y

50/0/298 1 efxs up up on-hook idle y

50/0/299 1 efxs up dorm on-hook idle y

50/0/300 1 efxs up dorm on-hook idle y

PWR FAILOVER PORT PSTN FAILOVER PORT

================= ==================

UC_iSupply#debug vpm signal

Voice Port Module signaling debugging is enabled

UC_iSupply#

000173: Mar 6 07:00:47.872: htsp_process_event: [0/1/0, FXOLS_ONHOOK, E_DSP_SIG_0000]fxols_onhook_ringing

000174: Mar 6 07:00:47.872: htsp_timer - 125 msec

000175: Mar 6 07:00:48.000: htsp_process_event: [0/1/0, FXOLS_WAIT_RING_MIN, E_HTSP_EVENT_TIMER]fxols_wait_ring_min_timer

000176: Mar 6 07:00:48.000: htsp_timer - 10000 msec

000177: Mar 6 07:00:48.000: htsp_timer3 - 5600 msec

000178: Mar 6 07:00:48.000: [0/1/0] htsp_start_caller_id_rx:BELLCORE

000179: Mar 6 07:00:48.000: htsp_start_caller_id_rx create dsp_stream_manager

000180: Mar 6 07:00:48.000: [0/1/0] htsp_dsm_create_success returns 1

000181: Mar 6 07:00:48.860: htsp_process_event: [0/1/0, FXOLS_RINGING, E_DSP_SIG_0100]

000182: Mar 6 07:00:48.860: fxols_ringing_not

000183: Mar 6 07:00:48.860: htsp_timer_stop

000184: Mar 6 07:00:48.860: htsp_timer - 10000 msec

000185: Mar 6 07:00:52.776: htsp_process_event: [0/1/0, FXOLS_RINGING, E_DSP_SIG_0000]

000186: Mar 6 07:00:53.600: htsp_process_event: [0/1/0, FXOLS_RINGING, E_HTSP_EVENT_TIMER3]fxols_snoop_clid_stop

000187: Mar 6 07:00:53.600: htsp_timer_stop3

000188: Mar 6 07:00:53.884: htsp_process_event: [0/1/0, FXOLS_RINGING, E_DSP_SIG_0100]

000189: Mar 6 07:00:53.884: fxols_ringing_not

000190: Mar 6 07:00:53.884: htsp_timer_stop

000191: Mar 6 07:00:53.884: htsp_timer_stop3

000192: Mar 6 07:00:53.884: [0/1/0] htsp_stop_caller_id_rx. message length 0htsp_setup_ind

000193: Mar 6 07:00:53.884: [0/1/0] get_fxo_caller_id:Caller ID receive failed. parseCallerIDString:no data.

000194: Mar 6 07:00:53.884: [0/1/0] get_local_station_id calling num= calling name= calling time=03/06 10:00 orig called=

000195: Mar 6 07:00:53.888: [0/1/0] htsp_dsm_close_done

000196: Mar 6 07:00:53.888: htsp_process_event: [0/1/0, FXOLS_WAIT_SETUP_ACK, E_HTSP_SETUP_ACK]

000197: Mar 6 07:00:53.888: fxols_wait_setup_ack:

000198: Mar 6 07:00:53.888: [0/1/0] set signal state = 0xC timestamp = 0fxols_check_auto_call

000199: Mar 6 07:00:53.892: htsp_process_event: [0/1/0, FXOLS_PROCEEDING, E_HTSP_PROCEEDING]fxols_offhook_proc

000200: Mar 6 07:00:53.892: htsp_timer - 120000 msechtsp_alert_notify

000201: Mar 6 07:00:53.960: htsp_process_event: [0/1/0, FXOLS_PROCEEDING, E_HTSP_ALERT]fxols_offhook_alert

000202: Mar 6 07:00:54.040: htsp_call_bridged invoked

000203: Mar 6 07:00:54.040: htsp_process_event: [0/1/0, FXOLS_PROCEEDING, E_HTSP_CONNECT]fxols_offhook_connect

000204: Mar 6 07:00:54.044: htsp_timer_stop

000205: Mar 6 07:00:54.044: htsp_process_event: [0/1/0, FXOLS_CONNECT, E_HTSP_VOICE_CUT_THROUGH]fxols_connect_proc_voice

000206: Mar 6 07:00:58.352: htsp_digit_ready(0/1/0): digit = 1

000207: Mar 6 07:00:59.052: htsp_digit_ready(0/1/0): digit = 0

000208: Mar 6 07:00:59.732: htsp_digit_ready(0/1/0): digit = 3

000209: Mar 6 07:01:05.112: htsp_timer_stop3 htsp_setup_req

000210: Mar 6 07:01:05.116: htsp_process_event: [0/1/1, FXOLS_ONHOOK, E_HTSP_SETUP_REQ]fxols_onhook_setup

000211: Mar 6 07:01:05.116: [0/1/1] set signal state = 0xC timestamp = 0

000212: Mar 6 07:01:05.116: htsp_timer - 1300 msec

000213: Mar 6 07:01:06.416: htsp_process_event: [0/1/1, FXOLS_WAIT_DIAL_TONE, E_HTSP_EVENT_TIMER]fxols_wait_dial_timer htsp_dial

000214: Mar 6 07:01:08.464: htsp_process_event: [0/1/1, FXOLS_WAIT_DIAL_DONE, E_DSP_DIALING_DONE]fxols_wait_dial_done htsp_alert

000215: Mar 6 07:01:08.464: htsp_timer - 350 msec

000216: Mar 6 07:01:08.468: htsp_call_bridged invoked

000217: Mar 6 07:01:08.468: htsp_call_bridged invoked

000218: Mar 6 07:01:08.472: htsp_process_event: [0/1/1, FXOLS_WAIT_CUT_THRU, E_HTSP_VOICE_CUT_THROUGH]fxols_handle_cut_thru

000219: Mar 6 07:01:08.472: htsp_timer_stop

000220: Mar 6 07:01:08.472: htsp_process_event: [0/1/0, FXOLS_CONNECT, E_HTSP_VOICE_CUT_THROUGH]fxols_connect_proc_voice

UC_iSupply#

UC_iSupply#

UC_iSupply#sh voice port summary

IN OUT

PORT CH SIG-TYPE ADMIN OPER STATUS STATUS EC

=============== == ============ ===== ==== ======== ======== ==

0/0/0 -- fxs-ls up dorm on-hook idle y

0/0/1 -- fxs-ls up dorm on-hook idle y

0/0/2 -- fxs-ls up dorm on-hook idle y

0/0/3 -- fxs-ls up dorm on-hook idle y

0/1/0 -- fxo-ls up up idle off-hook y

0/1/1 -- fxo-ls up up idle off-hook y

0/1/2 -- fxo-ls up dorm idle on-hook y

0/1/3 -- fxo-ls up dorm idle on-hook y

0/4/0 -- moh-imd up up idle seized y

50/0/9 1 efxs up up off-hook idle y

50/0/293 1 efxs up dorm on-hook idle y

50/0/293 2 efxs up dorm on-hook idle y

50/0/294 1 efxs up dorm on-hook idle y

50/0/294 2 efxs up dorm on-hook idle y

50/0/295 1 efxs up dorm on-hook idle y

50/0/295 2 efxs up dorm on-hook idle y

50/0/296 1 efxs up dorm on-hook idle y

50/0/296 2 efxs up dorm on-hook idle y

50/0/297 1 efxs up dorm on-hook idle y

50/0/297 2 efxs up dorm on-hook idle y

50/0/298 1 efxs up up on-hook idle y

50/0/299 1 efxs up dorm on-hook idle y

50/0/300 1 efxs up dorm on-hook idle y

PWR FAILOVER PORT PSTN FAILOVER PORT

================= ==================

　

[edwincharles]

attached my current config