CallManager 6.1 SIP trunk to sr140 -brooktrout

Unanswered Question
May 5th, 2009

Trying to get a sip trunk in 6.1 to talk to a brooktrout sr140 (rightfax) card. Have the sip trunk built in CCM and on the sr140 however we only get fast busy. Can anyone provide a link to a setup or troubleshooting doc, or provide some guidance if you have set this up. Thanks

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Average Rating: 0 (0 ratings)
minkdennis Tue, 05/05/2009 - 05:55

do you have any route patterns point to go across the sip trunk?

steelcity39 Tue, 05/05/2009 - 06:02

yes. we have route patterns setup pointing to the trunks. its almost like the trunk is not active (but no way to tell)

minkdennis Tue, 05/05/2009 - 06:09

I would make a test call, note the timestamp and collect the trace file, and see, if callmanager tries to set up the call via the trunk.

spotlight41 Wed, 07/08/2009 - 05:55

steelcity39,

Any luck configuring this? I am about to start this same project.

spotlight41 Tue, 10/20/2009 - 05:54

Yes! I had to add translation patterns specific to the DID's for the Rightfax server. Let me know if you need help.

steelcity39 Tue, 10/20/2009 - 07:32

thank you.

some questions:

do we need to use H323 or can we use SIP?

also, since the DID's are coming in on our MGCP controller gateways, do we need to allow t38 on those gateways?

spotlight41 Tue, 10/20/2009 - 08:48

We used SIP. We had to be sure the "Fax Relay" package was installed on our gateway.

When you do a sh run, do you see the "no mgcp package-capability fxr-package" line? If it is missing, then the fxr-package is enabled. If it is still there first try:

Log into the gateway, then issue the following:

conf t

no mgcp

mgcp

This will force the gateway to reset again. Maybe something happened and the reset from CallManager didn't do anything. If the package is still not correct, then enter the following:

conf t

mgcp package-capability fxr-package

no mgcp

mgcp

exit

Now check again to be sure it's missing. *One note, our IOS version had a bug. When I installed the Fax Relay package and reloaded the gateway, it reverted back to no package being installed, even though I had saved it.

steelcity39 Tue, 10/20/2009 - 08:56

did you need to do anything for the SIP trunk besides setup the trunk in CCM and then setup the sr140 for sip pointing to the IP of the CCM server?

I have the trunk built and a route pattern pointing to the rightfax server, however when I call it goes right to fast busy. looks like the sip trunk is not active..

thanks for your help

steelcity39 Tue, 10/20/2009 - 09:33

yes its there

the problem we are having it with the sip trunk itself. we are trying internal calls (from phone to the rightfax) and get immediate fast busy.

here is what we did:

built sip trunk in the CCM to the ip address of the rightfax machine.

created routepattern to point to the sip trunk.

translated numbers to point to route pattern.

when we call the numbers, we get immediate fast busy.. no answer..

any suggestions?

spotlight41 Tue, 10/20/2009 - 09:34

how many digits is the carrier passing to you. That will determine how your translation patterns need to be set.

steelcity39 Tue, 10/20/2009 - 09:44

carrier is passing us 10 digits.

we take the 10 digits and translate to a 4 digit route pattern that is pointed to the sip trunk.

from what i can tell, we either need a route pattern to tell CCM where to send the call .. there is no way to tell CCM to send the call to the sip trunk using just a translation pattern.

spotlight41 Tue, 10/20/2009 - 10:00

We also have carrier passing 10 digits. To get ours to work, we created translation patterns for each range of DIDs:

(areacode)229.33xx

that "dot" is important. At the bottom of the TP, we configured the "discard digits" to "PreDot".

Then our 4 digit route patterns worked.

Also make sure your SIP config is using UDP for SIP Trunk Security Profile.

spotlight41 Tue, 10/20/2009 - 12:34

the mgcp configuration is for the fax relay package, to allow the fax traffic thru to my UCM. From UCM I have same network SIP to Rightfax.

Nicholas Matthews Tue, 10/20/2009 - 12:40

I see, MGCP for PSTN, SIP to Rightfax.

MGCP T38 is hard to configure recently, due to some bugs.

Notably:

CSCta26864

CSCsy29533

CSCsw39039

CSCso69794

Basically - only 12.4(22)T is safe.

You need 'no mgcp fax t38 inhibit' and 'mgcp package fxr', and to reset the gateway. Make sure there aren't slips, and you should be set for T38.

-nick

Actions

Login or Register to take actions

This Discussion

Posted May 5, 2009 at 5:29 AM
Stats:
Replies:19 Avg. Rating:
Views:2229 Votes:0
Shares:0
Tags: No tags.

Discussions Leaderboard

Rank Username Points
1 21,026
2 15,047
3 10,314
4 7,999
5 4,856
Rank Username Points
135
90
72
66
55