Solved: Rightfax and CME - 2901 Router

Phil.Garrelhas · ‎10-04-2010

Hello,

My apologies, but I am a novice with the backend VoIP CLI configuration. I only have experience using front-end web GUI.

We currently moved to a Cisco 2901 router with CME. We moved from an ICS 7750 solution.

There are two EHWIC slots. One T1/E0 used for the incoming PRI from our phone company. The phone company sends us 10 digits. The other T1/E1 is used to connect to a server handling the fax capabilities.

We have about 10 DIDs that are configured on the fax server for faxing. How do I send those DIDs to the Rightfax server?

Would the configuration be:

dial-peer voice 3012 pots

destination-pattern 6471234567

controller T1 0/1/0

Thanks,

Phil...

Steven Holl · ‎10-06-2010

The call first attempts to go to peer 3012 here:

Oct 6 15:41:47.023: //1271/0FEBD72F80E6/CCAPI/cc_api_display_ie_subfields:
   ccCallSetupRequest:
   cisco-username=
   ----- ccCallInfo IE subfields -----
   cisco-ani=4164340533
   cisco-anitype=2
   cisco-aniplan=1
   cisco-anipi=0
   cisco-anisi=1
   dest=6477229322
   cisco-desttype=2
   cisco-destplan=1
   cisco-rdie=FFFFFFFF
   cisco-rdn=
   cisco-rdntype=-1
   cisco-rdnplan=-1
   cisco-rdnpi=-1
   cisco-rdnsi=-1
   cisco-redirectreason=-1   fwd_final_type =0
   final_redirectNumber =
   hunt_group_timeout =0

Oct 6 15:41:47.023: //1271/0FEBD72F80E6/CCAPI/ccIFCallSetupRequestPrivate:
   Interface=0x31BB13A0, Interface Type=6, Destination=, Mode=0x0,
   Call Params(Calling Number=4164340533,(Calling Name=)(TON=National, NPI=ISDN, Screening=User, Passed, Presentation=Allowed),
   Called Number=6477229322(TON=National, NPI=ISDN), Calling Translated=FALSE,
   Subscriber Type Str=RegularLine, FinalDestinationFlag=TRUE, Outgoing Dial-peer=3012, Call Count On=FALSE,
   Source Trkgrp Route Label=ALL_T1E1, Target Trkgrp Route Label=, tg_label_flag=1, Application Call Id=)

The call fails with q/850 cause value 34, which is no circuit available:

Oct 6 15:41:47.027: //1272/0FEBD72F80E6/CCAPI/cc_api_call_disconnected:
Cause Value=34, Interface=0x31BB13A0, Call Id=1272

The call then hunts to Unity, but don't worry about that. The concern is why the initial outbound dial-peer match (the proper one) fails with no circuit.

I'm guessing the PRI on 0/1/0 isn't up. Make sure 'sh controller t1' shows the T1 up for 0/1/0. If it doesn't, you have a cabling/clocking/linecode/framing issue (layer 1 issue). What does 'sh isdn st' show? If it shows TEI_ASSIGNED, add 'isdn protocol-emulate network' to 'interface Serial0/1/0:23' and re-test/re-collect debugs.

View solution in original post

Vishal Mohanty · ‎10-04-2010

Hello Phil,

Yes you are on the right track, so assuming

Controller T1 0/1/0 connects to the Fax server, and that this is a PRI as well then there should be a voice-port 0/1/0:23 automatically created after you configured the controller for pri-group. If 6471234567 is one of the DIDs coming in then your dial-peer would be:

dial-peer voice 3012 pots

destination-pattern 6471234567

port 0/1/0:23

forward-digits all

If the 10 DIDs do not have any pattern between them then you will need to create 9 more POTS dial-peers with different tags and destination-patterns but with the same port number.

But if the 10 DIDs are in some specific range, for example 6471234560 to 6471234569 then the destiation-pattern would have been

647123456.

and only one dial-peer would have been enough.

For your future reading :

Understanding Inbound and Outbound Dial Peers Matching on IOS Platforms:

http://www.cisco.com/en/US/tech/tk652/tk90/technologies_tech_note09186a008010fed1.shtml

is an excellent document on how dial-peer matching is done in Cisco IOS.

Cheers,

Vishal

Phil.Garrelhas · ‎10-05-2010

Hi Vishal,

Thanks for your help so far!

The T1 connected to the Fax server looks like this:

controller T1 0/1/0
cablelength short 220
pri-group timeslots 1-12,24

The dial peer is:

dial-peer voice 3012 pots
destination-pattern 6477229322
port 0/1/0:23
forward-digits all

The voice-port created is:

voice-port 0/1/0:23
cptone CA

When I dial the 6471234567 number, I receive a "There is no mailbox associated with this extension. Goodbye."

Any ideas?

Phil...

Steven Holl · ‎10-05-2010

It sounds like RF doesn't have a mailbox associated with the DNIS or ANI, so it doesn't know whose email box to dump the fax into. Check your RF documentation to figure out what it keys off of int he q931 setup to determine what mailbox to dump the fax into. You can use a q931 debug to verify the formatting (length/plan/type) the ANI and DNIS are sent to the fax server.

And it may sound silly, but that error sounds like the phrasing we use for Unity when we can't find a mailbox, so make sure that that audio/error is actually coming from RightFax. It doesn't sound like 'the Unity girl' does it?

Phil.Garrelhas · ‎10-05-2010

Hi Steven,

It is definitely the Unity girl speaking. It's almost as if the call to 6471234567 isn't routing to the controller 0/1/0:23 port.

The RF server is set up correctly to receive the call. So, when I call, I should hear a fax tone. Or at least a busy signal. BUt I'm hearing the Unity girl instead.

Any other ideas?

Phil..

Steven Holl · ‎10-06-2010

Verify your call routing then. You're sending the call to the wrong destination, most likely.

How is this call supposed to come in from the PSTN? Is the PSTN circuit on the same gateway as the T1 to RF? If so, can you get:

debug voip ccapi inout

debug isdn q931

debug h225 asn1

debug mgcp pack

debug ccsip mess

If the PSTN gateway is a different gateway, collect that output from both gateways during a call.

Also post a full output of sh run.

Phil.Garrelhas · ‎10-06-2010

I've attached a brief current running config, along with the debugging output when I tried dialing the fax line from my cell phone.

The DID I am trying to forward to RF is 6477229322. The cell phone I'm testing the call with is 4164340533.

I'm sure that I'm missing something very simple here. Does the serial port (int serial0/1/0:23) have to be configured with the trunking group as well?

Thanks,

Phil...

Steven Holl · ‎10-06-2010

The call first attempts to go to peer 3012 here:

Oct 6 15:41:47.023: //1271/0FEBD72F80E6/CCAPI/cc_api_display_ie_subfields:
   ccCallSetupRequest:
   cisco-username=
   ----- ccCallInfo IE subfields -----
   cisco-ani=4164340533
   cisco-anitype=2
   cisco-aniplan=1
   cisco-anipi=0
   cisco-anisi=1
   dest=6477229322
   cisco-desttype=2
   cisco-destplan=1
   cisco-rdie=FFFFFFFF
   cisco-rdn=
   cisco-rdntype=-1
   cisco-rdnplan=-1
   cisco-rdnpi=-1
   cisco-rdnsi=-1
   cisco-redirectreason=-1   fwd_final_type =0
   final_redirectNumber =
   hunt_group_timeout =0

Oct 6 15:41:47.023: //1271/0FEBD72F80E6/CCAPI/ccIFCallSetupRequestPrivate:
   Interface=0x31BB13A0, Interface Type=6, Destination=, Mode=0x0,
   Call Params(Calling Number=4164340533,(Calling Name=)(TON=National, NPI=ISDN, Screening=User, Passed, Presentation=Allowed),
   Called Number=6477229322(TON=National, NPI=ISDN), Calling Translated=FALSE,
   Subscriber Type Str=RegularLine, FinalDestinationFlag=TRUE, Outgoing Dial-peer=3012, Call Count On=FALSE,
   Source Trkgrp Route Label=ALL_T1E1, Target Trkgrp Route Label=, tg_label_flag=1, Application Call Id=)

The call fails with q/850 cause value 34, which is no circuit available:

Oct 6 15:41:47.027: //1272/0FEBD72F80E6/CCAPI/cc_api_call_disconnected:
Cause Value=34, Interface=0x31BB13A0, Call Id=1272

The call then hunts to Unity, but don't worry about that. The concern is why the initial outbound dial-peer match (the proper one) fails with no circuit.

I'm guessing the PRI on 0/1/0 isn't up. Make sure 'sh controller t1' shows the T1 up for 0/1/0. If it doesn't, you have a cabling/clocking/linecode/framing issue (layer 1 issue). What does 'sh isdn st' show? If it shows TEI_ASSIGNED, add 'isdn protocol-emulate network' to 'interface Serial0/1/0:23' and re-test/re-collect debugs.

Phil.Garrelhas · ‎10-06-2010

Hi Steven,

You Sir, were 100% correct.

The PRI was up, and had TEI_ASSIGNED. I added 'isdn protocol-emulate network' to 'interface Serial0/1/0:23' and the calls went through.

Tested the faxing capabilities, and everything is working as it should.

Thank you very much for your help! You've been great!

Phil....