Route (e911) calls out an FXO port connected to a local POTS line

[san.carlos]

CUCM 8.5

        Currently our e911 calls (CER in place) sent out our primary vgw (PRI/T1) circuit works just fine. So route patterns, partitions and CSSes are configured appropriately here. For a specific WAN remote location, I am wanting to route e911 calls out a second vgw that is local to the remote site. This is for correct address reporting to the local PSAP.

The route pattern (for the remote location) was set to send e911 calls out an FXO port connected to a local POTS line on our secondary vgw. When dialing I am getting a delayed fast busy signal when attempted to make a e911 call. If I attached an analog phone directoly to the line, I get a tone and am able to dial out, so I wonder if I have a configuration problem here.

Can anyone shed any lilght on what might be missing here. The calling party's device and FXO port are both on the same CSS which contains the e911 route partition.

Please advise.

Thanks,

- Carlos

[Chris Deren]

Provide "debug voice dialpeer" and "debug vpm signal", also use DNA to see if CUCM is seeing it as expected.

Chris

[san.carlos]

Chris,

DNA is complaining that is it still initializing... so it looks like I may have to restart those services, but prefer not to perform them now.

"debug voice dialpeer provides no results".

I used "debug vpm signal" and "debug voice ccapi inout" and the results are below. I also provided the dial plan on the vgw. The "...ccapi inout" debug output is showing "outgoing dial-peer=0, the default dial-peer. So not sure why it is not matching a dial-peer correctly.

"DIAL PLAN on VGW"

dial-peer voice 999010 pots
service mgcpapp
port 0/1/0
!
dial-peer voice 999011 pots
service mgcpapp
port 0/1/1
!
dial-peer voice 10 pots
preference 1
destination-pattern 911
port 0/1/0
forward-digits all
!
dial-peer voice 20 pots
preference 1
destination-pattern 9911
port 0/1/0
forward-digits 3
!
dial-peer voice 30 pots
preference 1
destination-pattern 9T
port 0/1/1
!
dial-peer voice 40 pots
service mgcpapp
destination-pattern 0T
!
dial-peer voice 1010 voip
preference 1
destination-pattern 46..
session target ipv4:10.18.0.5
!
dial-peer voice 999013 pots
service mgcpapp
port 0/1/3

"DEBUG VPM SIGNAL"

005210: Jun 24 08:17:54 MST: htsp_timer_stop3 htsp_setup_req
005211: Jun 24 08:17:54 MST: htsp_process_event: [0/1/0, FXOGS_ONHOOK, E_HTSP_SE
TUP_REQ]fxogs_onhook_setup
005212: Jun 24 08:17:54 MST: [0/1/0] set signal state = 0x0 timestamp = 0
005213: Jun 24 08:17:54 MST: htsp_timer - 10000 msec
005214: Jun 24 08:18:04 MST: htsp_process_event: [0/1/0, FXOGS_WAIT_TIP_GROUND,
E_HTSP_EVENT_TIMER]fxogs_offhook_disc
005215: Jun 24 08:18:04 MST: htsp_timer_stop
005216: Jun 24 08:18:04 MST: [0/1/0] set signal state = 0x4 timestamp = 0
005217: Jun 24 08:18:04 MST: htsp_timer - 2000 msec
005218: Jun 24 08:18:04 MST: htsp_process_event: [0/1/0, FXOGS_ONHOOK, E_HTSP_RE
LEASE_REQ]fxogs_onhook_release
005219: Jun 24 08:18:04 MST: htsp_timer_stop2
005220: Jun 24 08:18:04 MST: htsp_timer_stop3
005221: Jun 24 08:18:04 MST: htsp_process_event: [0/1/0, FXOGS_ONHOOK, E_DSP_SIG
_0110]
005222: Jun 24 08:18:04 MST: fxogs_line_reversal_clid_wait. On_hook line reversa
l detected possibily due to crossed cable
005223: Jun 24 08:18:06 MST: htsp_process_event: [0/1/0, FXOGS_ONHOOK, E_HTSP_EV
ENT_TIMER]

"DEBUG VOICE CCAPI INOUT"

005170: Jun 24 07:58:16 MST: //-1/xxxxxxxxxxxx/CCAPI/ccIFCallSetupRequestPrivate
:
   Interface=0x12FDDBCC, Interface Type=6, Destination=911, Mode=0x9,
   Call Params(Calling Number=,(Calling Name=)(TON=Unknown, NPI=Unknown, Screeni
ng=Not Screened, Presentation=Allowed),
   Called Number=911(TON=Unknown, NPI=Unknown), Calling Translated=FALSE,
   Subscriber Type Str=, FinalDestinationFlag=FALSE, Outgoing Dial-peer=0, Call
Count On=FALSE,
   Source Trkgrp Route Label=, Target Trkgrp Route Label=, tg_label_flag=0, Appl
ication Call Id=A000000002f1c14a000000F5)
005171: Jun 24 07:58:16 MST: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

005172: Jun 24 07:58:16 MST: :cc_get_feature_vsa malloc success
005173: Jun 24 07:58:16 MST: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

005174: Jun 24 07:58:16 MST:  cc_get_feature_vsa count is 1
005175: Jun 24 07:58:16 MST: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

005176: Jun 24 07:58:16 MST: :FEATURE_VSA attributes are: feature_name:0,feature
_time:167808072,feature_id:2712
005177: Jun 24 07:58:16 MST: //2712/55D1A36982B8/CCAPI/ccIFCallSetupRequestPriva
te:
   SPI Call Setup Request Is Success; Interface Type=6, FlowMode=1
005178: Jun 24 07:58:16 MST: //2712/55D1A36982B8/CCAPI/ccCallSetContext:
   Context=0x16C0E5A0
005179: Jun 24 07:58:16 MST: //-1/xxxxxxxxxxxx/CCAPI/ccIFCallSetupRequestPrivate
:
   Interface=0x133E01E4, Interface Type=9, Destination=0.0.0.0, Mode=0x9,
   Call Params(Calling Number=,(Calling Name=)(TON=Unknown, NPI=Unknown, Screeni
ng=Not Screened, Presentation=Allowed),
   Called Number=(TON=Unknown, NPI=Unknown), Calling Translated=FALSE,
   Subscriber Type Str=, FinalDestinationFlag=FALSE, Outgoing Dial-peer=0, Call
Count On=TRUE,
   Source Trkgrp Route Label=, Target Trkgrp Route Label=, tg_label_flag=0, Appl
ication Call Id=A000000002f1c14a000000F5)
005180: Jun 24 07:58:16 MST: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

005181: Jun 24 07:58:16 MST: :cc_get_feature_vsa malloc success
005182: Jun 24 07:58:16 MST: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

005183: Jun 24 07:58:16 MST:  cc_get_feature_vsa count is 2
005184: Jun 24 07:58:16 MST: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

005185: Jun 24 07:58:16 MST: :FEATURE_VSA attributes are: feature_name:0,feature
_time:167807848,feature_id:2713

[Chris Deren · Accepted solution]

Your FXO line is not workin properly, as seen here " fxogs_line_reversal_clid_wait. On_hook line reversa

l detected possibily due to crossed cable"

If this indeed is Ground start chnage your polarity on your cable, if you are not sure if this is ground change to loop to see if that works.

Chris

[san.carlos]

Chris,

Changed the port to LS and the calls are going through now - thanks!