Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

How can i set an analog FXS/DID

Hello

I have a 3925 router and a 4 port FXS/DID on it. I connect the one of FXS/DID port to tow different type of PBXs.

The first PBX is my company PBX that i have not access on it, i connected a FXS/DID port to one of the outlet port on the wall. I knew the PBX did not send any digit toward the FXS/DID port, then on the FXS/DID port i set command: "connection plar 5002", where 5002 was number of a CIPC. after that when i called the FXS/DID number, for example 3061, FXS/DID port connected and i had just one short beep on the CIPC, after that automatically connection was hooked on.

I tried 3 types of the FXS/DID signaling: wink-start, Delayed dial, Immediate, but behavior of them were same. I run a syslog server and enable debug vpm signal and log is like following: [Signaling is wink-start]

 Jul 24 11:04:02 192.168.2.3 113: *Jul 24 06:34:53.327: htsp_process_event: [2/0/1, DID_ONHOOK, E_DSP_SIG_1100]did_onhook_offhook htsp_setup_ind
Jul 24 11:04:02 192.168.2.3 114: *Jul 24 06:34:53.327: [2/0/1] get_local_station_id calling num= calling name= calling time=07/24 06:34  orig called=
Jul 24 11:04:02 192.168.2.3 115: *Jul 24 06:34:53.327: htsp_process_event: [2/0/1, DID_WAIT_SETUP_ACK, E_HTSP_SETUP_ACK]did_wait_setup_ack_get_ack
Jul 24 11:04:02 192.168.2.3 116: *Jul 24 06:34:53.327: htsp_timer2 - 100 msec
Jul 24 11:04:02 192.168.2.3 117: *Jul 24 06:34:53.331: htsp_timer_stop3
Jul 24 11:04:02 192.168.2.3 118: *Jul 24 06:34:53.331: htsp_process_event: [2/0/1, DID_WAIT_SETUP_ACK, E_HTSP_PROCEEDING]htsp_setup_req
Jul 24 11:04:02 192.168.2.3 119: *Jul 24 06:34:53.331: htsp_process_event: [50/0/2.1, EFXS_ONHOOK, E_HTSP_SETUP_REQ]efxs_onhook_setup
Jul 24 11:04:02 192.168.2.3 120: *Jul 24 06:34:53.331: htsp_ephone_start_caller_id_tx calling num= calling name = called num=5002 orig called num=
Jul 24 11:04:02 192.168.2.3 121: *Jul 24 06:34:53.331: [50/0/2.1] set signal state = 0x0 timestamp = 0
Jul 24 11:04:02 192.168.2.3 122: *Jul 24 06:34:53.331: efxs_onhook_setup: local target is available
Jul 24 11:04:02 192.168.2.3 123: htsp_alerthtsp_alert_notify
Jul 24 11:04:03 192.168.2.3 124: *Jul 24 06:34:53.339: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 192.168.1.111 port 514 started - CLI initiated
Jul 24 11:04:03 192.168.2.3 125: *Jul 24 06:34:53.379: htsp_process_event: [2/0/1, DID_WAIT_SETUP_ACK, E_DSP_SIG_0100]did_wait_setup_ack_onhook
Jul 24 11:04:03 192.168.2.3 126: *Jul 24 06:34:53.379: did_start_timer: 300 ms
Jul 24 11:04:03 192.168.2.3 127: *Jul 24 06:34:53.379: htsp_timer - 300 msec
Jul 24 11:04:03 192.168.2.3 128: *Jul 24 06:34:53.427: htsp_process_event: [2/0/1, DID_WAIT_SETUP_ACK, E_HTSP_EVENT_TIMER2]did_wait_prewink_timer  did_offhook
Jul 24 11:04:03 192.168.2.3 129: *Jul 24 06:34:53.427: [2/0/1] set signal state = 0x6 timestamp = 0 did_onhook
Jul 24 11:04:03 192.168.2.3 130: *Jul 24 06:34:53.427: [2/0/1] set signal state = 0x4 timestamp = 200
Jul 24 11:04:03 192.168.2.3 131: *Jul 24 06:34:53.487: htsp_process_event: [2/0/1, DID_OFFHOOK, E_DSP_SIG_1100]did_offhook_offhook
Jul 24 11:04:03 192.168.2.3 132: *Jul 24 06:34:53.487: did_stop_timer
Jul 24 11:04:03 192.168.2.3 133: *Jul 24 06:34:53.487: htsp_timer_stop wrong offhook event
Jul 24 11:04:03 192.168.2.3 134: *Jul 24 06:34:53.783: htsp_process_event: [2/0/1, DID_OFFHOOK, E_DSP_SIG_0100]did_offhook_onhook
Jul 24 11:04:03 192.168.2.3 135: *Jul 24 06:34:53.783: did_start_timer: 300 ms
Jul 24 11:04:03 192.168.2.3 136: *Jul 24 06:34:53.783: htsp_timer - 300 msec
Jul 24 11:04:03 192.168.2.3 137: *Jul 24 06:34:54.083: htsp_process_event: [2/0/1, DID_OFFHOOK, E_HTSP_EVENT_TIMER]did_offhook_timeout
Jul 24 11:04:03 192.168.2.3 138: *Jul 24 06:34:54.083: htsp_timer_stop2
Jul 24 11:04:03 192.168.2.3 139: *Jul 24 06:34:54.083: did_start_timer: 400 ms
Jul 24 11:04:03 192.168.2.3 140: *Jul 24 06:34:54.083: htsp_timer - 400 msec
Jul 24 11:04:03 192.168.2.3 141: *Jul 24 06:34:54.083: htsp_timer_stop3
Jul 24 11:04:03 192.168.2.3 142: *Jul 24 06:34:54.083: htsp_process_event: [50/0/2.1, EFXS_WAIT_OFFHOOK, E_HTSP_RELEASE_REQ]efxs_waitoff_release
Jul 24 11:04:03 192.168.2.3 143: *Jul 24 06:34:54.083: [50/0/2.1] set signal state = 0x4 timestamp = 0
Jul 24 11:04:04 192.168.2.3 144: *Jul 24 06:34:54.083: htsp_process_event: [2/0/1, DID_GUARD_ALL, E_HTSP_RELEASE_REQ]did_onhook_release  did_onhook
Jul 24 11:04:04 192.168.2.3 145: *Jul 24 06:34:54.083: [2/0/1] set signal state = 0x4 timestamp = 0
Jul 24 11:04:04 192.168.2.3 146: *Jul 24 06:34:54.483: htsp_process_event: [2/0/1, DID_GUARD_ALL, E_HTSP_EVENT_TIMER]did_guard_all_timer
Jul 24 11:04:04 192.168.2.3 147: *Jul 24 06:34:54.483: htsp_process_event: [2/0/1, DID_PARK, E_DSP_SIG_0100]did_park_onhook
Jul 24 11:04:04 192.168.2.3 148: *Jul 24 06:34:54.483: htsp_timer_stop

 

On the second type of PBX that i access on it, i connected one of its ports to FXS/DID port, but its behavior was different. The CIPC automatically went to ringing state, without any call on the FXS/DID port. I used the wink-start signalling and log was generated was like below, i used another signalings too, the log was different but behavior was same.

Jul 24 12:38:41 192.168.2.3 298: *Jul 24 08:09:32.147: htsp_process_event: [2/0/1, DID_ONHOOK, E_DSP_SIG_1100]did_onhook_offhook htsp_setup_ind
Jul 24 12:38:41 192.168.2.3 299: *Jul 24 08:09:32.147: [2/0/1] get_local_station_id calling num= calling name= calling time=07/24 08:09  orig called=
Jul 24 12:38:41 192.168.2.3 300: *Jul 24 08:09:32.147: htsp_process_event: [2/0/1, DID_WAIT_SETUP_ACK, E_HTSP_SETUP_ACK]did_wait_setup_ack_get_ack
Jul 24 12:38:41 192.168.2.3 301: *Jul 24 08:09:32.147: htsp_timer2 - 100 msec
Jul 24 12:38:41 192.168.2.3 302: *Jul 24 08:09:32.151: htsp_timer_stop3
Jul 24 12:38:41 192.168.2.3 303: *Jul 24 08:09:32.151: htsp_process_event: [2/0/1, DID_WAIT_SETUP_ACK, E_HTSP_PROCEEDING]htsp_setup_req
Jul 24 12:38:41 192.168.2.3 304: *Jul 24 08:09:32.151: htsp_process_event: [50/0/2.1, EFXS_ONHOOK, E_HTSP_SETUP_REQ]efxs_onhook_setup
Jul 24 12:38:42 192.168.2.3 305: *Jul 24 08:09:32.151: htsp_ephone_start_caller_id_tx calling num= calling name = called num=5002 orig called num=
Jul 24 12:38:42 192.168.2.3 306: *Jul 24 08:09:32.151: [50/0/2.1] set signal state = 0x0 timestamp = 0
Jul 24 12:38:42 192.168.2.3 307: *Jul 24 08:09:32.151: efxs_onhook_setup: local target is available
Jul 24 12:38:42 192.168.2.3 308: htsp_alerthtsp_alert_notify
Jul 24 12:38:42 192.168.2.3 309: *Jul 24 08:09:32.247: htsp_process_event: [2/0/1, DID_WAIT_SETUP_ACK, E_HTSP_EVENT_TIMER2]did_wait_prewink_timer  did_offhook
Jul 24 12:38:42 192.168.2.3 310: *Jul 24 08:09:32.247: [2/0/1] set signal state = 0x6 timestamp = 0 did_onhook
Jul 24 12:38:42 192.168.2.3 311: *Jul 24 08:09:32.247: [2/0/1] set signal state = 0x4 timestamp = 200

 

I'm newbie to VoIP world, i do not know what i must do.

Thanks for any help

7 REPLIES
Silver

First of all you use FXS port

First of all you use FXS port for connecting endpoint device (analog phone, fax...) and you don't use "connection plar" there...you should use "station number" "id" etc on that kind of ports. Attach some analog phone on FXS and give port number let's say 5005...dial that from your registered CIPC and it should work. Then, if you have FXO on your PBX and you have let's say analog endpoint on that PBX with number for example 4004 - then just put station number 4004 on FXS and when you dial 4004 from CIPC your PBX analog phone should ring...

Second if you have FXS on your Cisco equipment you need FXO port on your PBXs equipment for interconnection.

After that configuration you should be able to have successfull calls between your different systems.

BR,

Dragan

HTH, Dragan
New Member

Hi Dragan,Thanks a lot for

Hi Dragan,

Thanks a lot for your quick response.

I know FSX port is for connecting endpoints, but the ports used on router are FXS/DID and in DID mode. I don't know, do i think correctly? but i think the FXS ports in DID mode are like FXO and you can connect CO to this ports. I can't order DID support from PSTN, but i have a PBX and must be connected to router. First of all my question is which port of this PBX must be connected to FXS/DID? I connected and FXS port on the PBX to FXS/DID port on router, but after that FXS/DID port immediately seized. after lots of searching, i understood DID trunk port on PBX must be connected to FXS/DID, but i dont know what is DID trunk port? Does it mean CO trunk port on PBX? because i have a CO port on PBX that i can connect to PSTN.

I want to know, Do I think correctly? and if I'm correct, what i must do on router side and also PBX side for connecting these tow?

 

Thanks in advance.

Silver

I don't know your type of old

I don't know your type of old PBX but you neeed FXO type port there. If you used that PBX for PSTN access before Cisco then use ports which were connected to PSTN to connect to Cisco FXS ports.

It should work if configured OK...I have several implementations involving some old PBX (Selta, Alcatel. etc - without IP interface smiley) and connecting them to Cisco.

BR,

Dragan

HTH, Dragan
New Member

Drangan,Sorry for bothering

Dragan,

Sorry for bothering you,

I have a question that i want sure. Isn't there any difference between FXS port and FXS/DID port?

because I've read must connect PSTN to FXS/DID port, and you know connecting PSTN to FXS port could damage port, Then i think FXS/DID port is like FXO port and if it's like FXO port, Does it connect to FXO port on PBX?

I'm confused about it and i want sure.

Thanks

 

Silver

Well first FXS cards were

Well first FXS cards were only FXS and newer one are with FXS/DID (Direct Inward Dialing) feature - but concept is same meaning those cards are ment for terminating analog equipment - phones, fax, modems etc.

DID feature is a service offered by telephone companies that enables callers to dial directly into an extension on a PBX and not use an auto-attendant. So it means that your FXS card can work in that mode too but primary function is same - you connect end equipment there.

So conclusion - connect your FXS port on Cisco to FXO port on PBX and it should be fine...

BR,

Dragan 

HTH, Dragan
New Member

Dragan,Just one more question

Dragan,

Just one more question, if i want to use DID mode in FXS card, i know the PBX must send DNIS for dialing directly into an extension, then what i must config in side of old PBX?

My PBX isn't a well-known brand and i couldn't find a reference in internet for setting up that, then i want to know if there is an example about what i must do in side of PBX for sending DNIS toward router? for example instructions for a well-known old PBX.

Thanks a lot

Silver

Well I can't answer on that

Well I can't answer on that smiley

Mostly because I don't know type of your PBX or how it works...but most of time if you know dialing plan of your PBX it's enough to successfully make calls - just send those digits to PBX and it will know what to do with them. I have some real examples where I only know number plan and used that for making good calls...

I believe you that you can't find good documentation about your PBX - it's same for all vendors from that time and that type of old PBXs.

BR,

Dragan

HTH, Dragan
151
Views
0
Helpful
7
Replies
CreatePlease login to create content