Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

IPS to SV8500 tandem calls problem 1

Status
Not open for further replies.

phadobas

Technical User
Jul 30, 2005
612
US
I have an SV8500 in my "Central office" and an IPS 2000 in one of my remote offices. The two are connected over CCIS via a point-to-point T1 provided by telco. All trunking is done by the 8500 otherwise.

Outgoing calls from the 2000 supposed to go to the 8500 via the ccis and then to telco via a PRI.

The 8500 has no problems whatsoever. All its stations can call out local, long-dist and international. They can also call the ips and all its stations no problems.

However, calls from the ips have some problems. You can call all sta in the 8500, you can make local and you can make long-dist calls, but international calls always fail with fast busy.

LCR access code on the 8500 is "1". It gets stripped every time a call is sent to local or long distance carriers.

On the ips, the lcr access code is also "1", and its not stripped when the call is sent to the 8500, so in theory the 8500 should just handle it as a call from any of its stations. But somehow it does not. It always rejects international calls.

Monitoring trunks and routes shows that international calls from the ips do grab a trunk in the ccis to reach the 8500, but not sure what happens then. I also know that the calls coming from the IPS are seen by the 8500, but the 8500 never attempts to connect the call to an outgoing PRI line. An ISMC trace on the 8500 of such call coming from the ips does show all digits arriving to the 8500, including the "1" access code. But then again, ISMC has no detailed documentation. I can barely make out from the Hex garble the calling station number of the ips, and the called number.

I'm not even sure if the problem is with the 8500 or the ips...

Anybody has a clue?
 
Actually I don't really have a clue but I will take a shot in the dark and ask if you have considered digit length to be the problem (in the IPS that is)?
 
I did, and actually, you are probably on the right track.

Its easy with local and ld domestic call since their digit length is always the same. So CM857 was set for those accordingly, and when I dial those numbers on the IPS, I see the system grabbing a CCIS trunk and sending the call to the 8500 as soon as I finish dialing the last digit.

However, when I call international, there is always a lag before I see a CCIS channel being grabbed, no matter what I put into CM857>1011>xx and no matter how many digits the international number consists of...
 
You can test using a # as the last digit of your number as that tells the system you have finished dialing and the call should go out straight away!
 
Dear Ozzy,

I did that and for whatever reason, it did not send the call immediately. It still had that few seconds lag before the CCIS trunk was grabbed.

 
Ok

Aol we will have to follow this through the lcr. How IPS literate are you?
 
There is an FAQ here that should get you started.....


It's a bit involved but if you compare how a local call is treated with how the problem calls are handled it may be all the help you need in conjunction with a command manual!
 
Allright. I checked that link you refer to and I'm literate enough to read, understand and implement as applicable. I won't be at the site today, so the next time I go I'll check this out.

For the life of me, I can't access the system remotely, although that would make things a lot more easy. I programmed and extension number for the built-in modem on the MP card, but when I dial it from my laptop, the IPS answers, gives the usual modem handshake beeps for like 30 seconds, and the laptop says "no carrier", or it may say "Connected at 28800KBPS", but then says "Couldn't connect to PBX"...
 
Problem solved. I needed to change a setting:
CMA710>0>15 to CMA710>0>14. It's a timer on the CCIS channel and gives more time for the IPS2000 to wait for an ACM signal (whatever that is) to come back from the SV8500 once the dialed digits were sent. Basically, on international calls, you can't specify the exact amount of maximum digits dialed by CM85, since the number of digits vary country-by-country.

So when you finished dialing, the IPS waits a certain amount of time before it thinks dialing is complete and starts processing the call. When it sends the digits to the 8500, it does the same thing: waits for a certain amount before it starts processing the call. I assume, that's the point when it sends back an ACM signal to the IPS (it must be some sort of acknowledge signal). It appears the problem was that the IPS didn't wait long enough for the ACM signal coming back from the 8500 before it said "well, looks like nobody cares on the other end that I'm trying to send out a call, so I give up" and gave fast busy for the caller even before the 8500 had a chance to look at the digits sent to it by the IPS.

So when I increased the wait time from 15 sec to 28 sec, that was enough, and calls started to go through.

All this, I decoded from the ISMC command of the 8500 monitoring messages for successful domestic calls and unsuccessful international calls, and doing a search for "ACM" on the IPS Command Manual.

Thanks for all your helps.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top