06-07-2011 08:34 PM - edited 03-16-2019 05:20 AM
We have a Cisco 2811 that is in between our RightFax Server and our Cisco 3845 Cube Router. We have SIP trunks but our provider is not T.38 compliant so that is why the 2811 was put in place. This has been in place for over a year without any troubles. We have now come across a particular local number that we are unable to fax to. We can call this fax number for our IP Phones and get a fax tone. We ran WireShark from RightFax server to find that the SIP invite gets a 404 code which may mean it does not know how to route the call.
I also see the follwing from the 2811 log,
//204128/B3FB5F1E857D/CCAPI/ccCallDisconnect:
Cause Value=1, Call Entry(Responsed=TRUE, Cause Value=1)
9070044: Jun 7 22:34:43.970: //204128/B3FB5F1E857D/CCAPI/cc_api_call_disconnect_done:
Disposition=0, Interface=0x47A6245C, Tag=0x0, Call Id=204128,
Call Entry(Disconnect Cause=1, Voice Class Cause Code=0, Retry Count=0)
//204128/B3FB5F1E857D/CCAPI/ccCallDisconnect:
Cause Value=1, Call Entry(Responsed=TRUE, Cause Value=1)
9070044: Jun 7 22:34:43.970: //204128/B3FB5F1E857D/CCAPI/cc_api_call_disconnect_done:
Disposition=0, Interface=0x47A6245C, Tag=0x0, Call Id=204128,
Call Entry(Disconnect Cause=1, Voice Class Cause Code=0, Retry Count=0)
I could attach the number being dialed and the dial peers off that router if helpful.
Thanks.
Solved! Go to Solution.
06-10-2011 12:57 AM
Can you make a test call from the IP Phone then the rigthfax server to the same number.
Collect the debugs.
debug voip ccapi inout
debug ccsip messages
on both the 2811 and the CUBE router.
It looks like a dialplan issue. Check your dial-peers else give me these debugs and the relevant dial-peers. (probably the entire set of dial-peers on both routers.)
/divin
06-08-2011 12:21 AM
Yeah please attach the dial-peers
and a full debug of the call.
Debug ccsip message
debug voip ccapi inout
06-08-2011 05:11 PM
Thanks for the reply.
I was not able to see any debug output with either Debug ccsip message or Debug voip ccapi inout. Not sure if I did not see any output with those debug commands on since this router is in between RightFax and the Cube Router. Doing a show debug lists that they are actively debugging and I issued the terminal monitor command as well.
Below are the dial peers on this router. Sorry I only knew to paste them into this reply. I tried to label the few dial peers that point to an ip.
Hope this information is helpful.
Thanks again for any insight you may be able to give.
The fax number dialed that we are having the issue with is 982-0xxx. I am not sure which dial peer this number would attempt to use.
voice 104 voip
translation-profile outgoing Strip_nine_star
preference 1
destination-pattern xxx2559[4-8].. ### xxx is local area code
progress_ind setup enable 3
progress_ind progress enable 8
voice-class codec 1
session protocol sipv2
session target ipv4:10.xxx.xx.25 ### RightFax NIC
dtmf-relay rtp-nte
!
dial-peer voice 103 voip
translation-profile incoming eight_star
preference 2
session protocol sipv2
incoming called-number .T
dtmf-relay rtp-nte
codec g711ulaw
!
dial-peer voice 500 voip
description PRIMARY.CUCM.IN/OUT DIAL-PEER.FAXING
translation-profile incoming FAX.CONVERSION
preference 1
voice-class codec 1
session target ipv4:10.xxx.xx.10 ### Call Mgr Publisher
incoming called-number 9.
dtmf-relay h245-alphanumeric
no vad
!
dial-peer voice 501 voip
description BACKUP.CUCM.IN/OUT DIAL-PEER.FAXING
translation-profile incoming FAX.CONVERSION
preference 2
voice-class codec 1
session target ipv4:10.xxx.xx.11 ### Call Mgr Subscriber
incoming called-number 9.
dtmf-relay h245-alphanumeric
no vad
!
dial-peer voice 1 pots
destination-pattern 1[2-9]..[2-9]......
progress_ind setup enable 3
progress_ind progress enable 8
incoming called-number .
direct-inward-dial
port 1/0:23
forward-digits all
!
dial-peer voice 2 pots
destination-pattern [2-9]......
progress_ind setup enable 3
progress_ind progress enable 8
incoming called-number .
direct-inward-dial
port 1/0:23
!
dial-peer voice 3 pots
destination-pattern 011.
progress_ind setup enable 3
progress_ind progress enable 8
direct-inward-dial
port 1/0:23
forward-digits all
!
dial-peer voice 105 voip
preference 1
session protocol sipv2
incoming called-number 011T
dtmf-relay rtp-nte
codec g711ulaw
06-09-2011 12:20 AM
Hi,
For the Fax number 982-0xxx, the below dial-peer would be matched.
dial-peer voice 2 pots
destination-pattern [2-9]......
progress_ind setup enable 3
progress_ind progress enable 8
incoming called-number .
direct-inward-dial
port 1/0:23
You need to make sure that the call routing is properly been implemented..
Mohsin..
06-09-2011 06:28 AM
I guess I am a little confused since the dial-peer on this router (dial-peer voice 2 pots) appears to be sending the call over to the Cube Router on port 1/0:23. Our IP Phones go through the Cube Router and they are able to dial the fax number and get fax tone. That would tell me the Cube Router knows how to route the call. I have just done some testing to find out that any 986-xxx or 987-xxxx fax number is having the same issue. It appears that any local fax number that starts with 9xx-xxxx is having trouble. With that said, IP Phones dial a "9" to get outside line. Would this point more to 2811 or Cube Router issue?
06-10-2011 12:50 AM
You can try show dialplan number
Else run
debug voip ccapi inout
Search for "outgoing" in the debug.
/divin
06-10-2011 12:57 AM
Can you make a test call from the IP Phone then the rigthfax server to the same number.
Collect the debugs.
debug voip ccapi inout
debug ccsip messages
on both the 2811 and the CUBE router.
It looks like a dialplan issue. Check your dial-peers else give me these debugs and the relevant dial-peers. (probably the entire set of dial-peers on both routers.)
/divin
06-10-2011 12:58 AM
FYI Disconnect Cause=1 points to unallocated number
06-10-2011 07:51 PM
It was definitely a dial-peer issue but more specifically the translation-rule on the dial peer.
With some TAC assistance a new translation-rule was created and used with the dial-peer.
The dial-peer being used when 9xx-xxxx was being faxed was stripping the leading "9" so only sending 6 digits to the CUBE. This dial-peer is also used for another purpose for certain calls coming out of CUCM. CUCM calls require a "9" for outside line access.
It was using this translation-rule
voice translation-rule XXX
rule 1 /91/ /1/
rule 2 /9/ //
This was the translation-rule added
voice translation-rule XXX
rule 1 /^9\(......\)$/ /9\1/
rule 2 /91/ /1/
rule 3 /9\(..........\)$/ /\1/
rule 4 /^9\(.......\)$/ /\1/
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide