[cisco-nas] Cisco 3640 does not collect Calling ID and Called ID

Tue Apr 6 13:47:39 EDT 2004

Collecting ANI and DNIS with R2 is a simple matter
of configuring the router to match the switch configuration.
R2 behaves differently from country to country, from telco
to telco within the same country, and even from switch to switch
within the same telco.  Therefore it is not possible in the
general case to explain how to make R2 work.

Debugs:

conf term
   service timestamp debug date msec
   modem call-record terse
   no logging console
   no logging rate-limit
   end

debug cas
debug modem csm

This will show what's happening.

tips on R2:

http://www.cisco.com/warp/public/788/signalling/e1_r2_sig.html
http://www.cisco.com/warp/public/471/e1_r2_config_data.html
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/5300/sw_conf/ios_121/5300r2.htm
http://www.cisco.com/warp/public/788/signalling/e1_r2_cas_custom.html

If it looks like the switch just isn't configured to send you ANI,
then you'll have to talk to the switch tech and get him to reconfigure
the switch.

Aaron

---

> Dear Aaron,

> Thanks for your reply. With our digital modem NAS (AS5300) that uses R2
> connected to PSTN also cannot collect the Calling ID, we can collect only the
> Called ID. Could you please suggest the configuration to collect both Calling
> and Called ID. The following is the log of my digital modem csm:

>   ras2#sh modem cs
>   ras2#sh modem csm 1/9
>   MODEM_INFO: slot 1, port 9, unit 0, tone r2-compelled, modem_mask=0x0000, modem_port_offset=0
>   tty_hwidb=0x620749E0, modem_tty=0x61A48C84, oobp_info=0x00000000, modem_pool=0x6180204C
>   tty statbits=0x20090440, statbits2=0x00000001
>   tty capabilities=0x00018C01, capabilities2=0x00008000
>   modem_status(0x2802): VDEV_STATUS_ACTIVE_CALL.VDEV_STATUS_ALLOCATED.VDEV_STATUS_NEGOTIATED.
>   device capabilities=0x0000AFDE
>   csm_state(0x0209)=CSM_IC7_CONNECTED, csm_event_proc=0x6017D828, current call thru CAS line
>   invalid_event_count=0, wdt_timeout_count=0
>   wdt_timestamp_started is not activated
>   wait_for_dialing:False, wait_for_bchan:False
>   pri_chnl=TDM_PRI_STREAM(s0, u1, c7), modem_chnl=TDM_MODEM_STREAM(s1, c9)
>   physical tdm port = 9, Backplane TDM Stream = 1, Channel = 1
>   dchan_idb_start_index=0, dchan_idb_index=0, call_id=0x0F86, bchan_num=6
>   csm_event=CSM_EVENT_DSX0_CONNECTED, cause=0x000E
>   Last 8 CSM states and events:
>      Number States                             Events
>      [0]    CSM_IC6_WAIT_FOR_CONNECT           CSM_EVENT_DSX0_CONNECTED
>      [1]    CSM_IC7_CONNECTED                  CSM_EVENT_DSX0_DISCONNECTED
>      [2]    CSM_OC8_DISCONNECTING              CSM_EVENT_NONE
>      [3]    CSM_IC3_WAIT_FOR_RES_RESP          CSM_EVENT_RESOURCE_OK
>      [4]    CSM_IC6_WAIT_FOR_CONNECT           CSM_EVENT_DSX0_CONNECTED
>      [5]    CSM_OC6_CONNECTED                  CSM_EVENT_NONE
>      [6]    CSM_IC3_WAIT_FOR_RES_RESP          CSM_EVENT_RESOURCE_OK
>      [7]    CSM_IC6_WAIT_FOR_CONNECT           CSM_EVENT_DSX0_CONNECTED
>   ring_no_answer=7, ic_failure=12, ic_complete=274
>   dial_failure=0, oc_failure=0, oc_complete=0
>   oc_busy=0, oc_no_dial_tone=0, oc_dial_timeout=0
>   remote_link_disc=65, stat_busyout=0, stat_modem_reset=0
>   oobp_failure=0
>   call_duration_started=4w0d, call_duration_ended=00:00:00, total_call_duration=3d12h
>   The calling party phone number =
>   The called party phone number  = 125
>   total_free_rbs_timeslot = 36, total_busy_rbs_timeslot = 0, total_dynamic_busy_rbs_timeslot = 0, total_static_busy_rbs_timeslot = 0,
>   total_sw56_rbs_timeslot = 0, total_sw56_rbs_static_bo_ts = 0,
>   total_free_isdn_channels = 0, total_auto_busy_isdn_channels = 0,
>   min_free_modem_threshold = 0

> As above log, there is no calling party phone number, but the called party phone number is '125' our access phone number for the NAS.

> Regards,
> Souphonh

> ----- Original Message -----
> From: "Aaron Leonard" <Aaron at cisco.com>
> To: "Souphonh" <souphonh at laopdr.com>
> Cc: <cisco-nas at puck.nether.net>
> Sent: Tuesday, April 06, 2004 11:03 AM
> Subject: Re: [cisco-nas] Cisco 3640 does not collect Calling ID and Called ID

> > Sorry, there is no way to collect this information from
> > the NM-AM (or any other analog modems) in a Cisco router.
> > To collect ANI and DNIS (calling / called number), you must
> > use a digital modem (for example, in the 3640, you would
> > use NM-DM MICA modems) and a signaling method that supports
> > both ANI and DNIS (for example, ISDN or R2.)
> >
> > Aaron
> >
> > ---
> >
> > > I am using cisco 3640 and analog module for dial up server. I have problem to get 3640 collecting Calling and Called ID from PSTN. Could you please suggest how can I configure our NAS to collect such information. The following is my modem csm log:
> >
> > >   ras3#sh modem csm 1/7
> > >   Modem 1/7, line 40 (analog)
> > >   CSM status: CALL_ACTIVE
> > >   CSM current state(0x00000006): CONNECTED_STATE
> > >   CSM last event: MODEM_CONNECTED, cause: 0x0000
> > >   current call thru CAS line; call_id 0, bchan_num -1
> > >   The calling party phone number:
> > >   The called party phone number:
> > >   wdt timer is not activated
> > >   invalid_events 0, wdt_timeouts 0
> > >   ic_failure 43, ic_complete 363, oc_failure 0, oc_complete 0
> > >   oc_busy 0, remote_link_disc 0, busyout 0, modem_reset 0
> > >   call started 2w3d, call ended 00:00:00, total modem active time 3d03h
> > >   tty_hwidb 0x6290B674, modem_tty 0x62909DCC, modem_pool 0x625C1BB0
> > >   total pri d-channels 0, last used pri d-channel 0
> > >   total_free_rbs_timeslot 0, total_busy_rbs_timeslot 0, min_free_modem_threshold 6
> >
> > > As above log, there is no value for called and calling party phone number.
> >
> > > Regards,
> > > Souphonh
> >