Insert a pause to a call forward number

[flctech]

I would appreciate any assistance on this.

I have a MICS 6.1xc with PRI. My client wants to forward an extension to their cell number which is long distance from the office. They are using LD codes and the problem is adding the LD code to the forward number string.

I enter Feature 4, Route code (9) + tel# + Feature 78 + LD code. When I enter Feature 78, it just inserts a blank space not the clock symbol. When I call the ext, the call disconnects. If I transfer to a local number, no problem. If I transfer to an LD# without the pause, it prompts for an LD code when I call the extension.

I also tried to bury this into a route using a destination code and I get the same result.

The question is, how do I add a pause into a call forward number?

Thanks in advance.

Flctech

 

[cook1082]

That only works with analog lines.I don't think there is a way to add any pause in the string for a PRI.

 

[flctech]

Thanks cook1092 for the reply.

Actually it does work on PRI. I have another client with the same configuration and it will accept a pause. I am aware that LINK will not work on a PRI (F78).

Having tested this a little further, it would seem that the culprit is the pause. It does put a space in the string and regardless of the number (Local or LD) once the pause is reached it disconnects the call.

I can't see a restriction problem as I have removed all restrictions from the set and the lines but same problem exists.

Any thoughts? Thanks

Flctech

 

[cook1082]

Could it be the dial plan digit leingth,Public.

 

[flctech]

I don't see a problem with digit length although I see your reasoning. I have digit length set to 11 for direct dialed LD calls.

What really has me stumped is the disconnect when it reaches the pause. It treats it almost like a restriction filter would, however there are no restrictions set on the PRI or the set. I am thinking a possible problem on the carrier side, perhaps the PRI doesn't like a pause.

Thanks again for your reply.

Flctech

 

[fireeater]

check with the telco it may not be allowing trk to trk transfers on long distance calls (security feature)

have you tried to transfer it manually

HALLOWED ARE THE ORI

mike

http://www.ics-on.ca

 

[flctech]

Hi Fireeater,

Yes it will transfer manually but I hear the LD code prompt and then enter the code so I don't think it is a transfer restriction by the carrier.

Just to get to the bottom of the problem, I setup a call forward to a local number and added the pause after the local 10 digits and sure enough it drops the call. I then just did a call forward to "9" + Pause and it dropped it as well. The problem is clearly that it doesn't like the pause. I have another client with an identical setup and it works fine, can't see any obvious difference between the 2 systems. I'm beginning to wonder if I have a buggy system with a unique problem.

Can you think of anything that would cause this in programming?

Thanks,

Flctech

 

[kwtaylor]

add additional pauses each pause is only a 1.5 secs. Sounds like your not giving your system enough time to wait until the ld request hits.

 

[flctech]

Thanks for the reply,

I have tried several pauses with same result. It never gets to the point of prompting as the call disconnects on the first pause. I think the problem is that the system doesn't like the pause although I'm not sure why.

Any thoughts?

Flctech

 

[jerryreeve]

I dont like making the cust dial more digits than necessary.

If you set up a destination code for this (say lets use 876) with absorb length 3 route table 876
then set up a route table 876 to dial out 1800nnxxxxxpppp123456789

then use feat 4 876 to forward the phone.

----------------------------
Hill?? What hill??
I didn't see any $%@#(*$ Hill!!
----------------------------
JerryReeve
Communication Systems Int'l
com-sys.com

 

[kwtaylor]

I'll check and get back to you... I can't image it's the pauses itself is causing the problem but, I have been wrong.

 

[flctech]

Hi Jerry,

Yes I tried that but got the same result. Even when setup as a route and detination code, as soon as it gets to the pause it terminates the call. Really confuses me on this one. I wondered if there was a timer issue but can't seem to see anything that relates to pause.

Is it possible the RLT (Release Line Trunking) could have an impact? I'm not sure if they have the feature as I haven't talked to the telco yet.

Any thoughts? (Thanks for the reply)

Flctech

 

[jerryreeve]

sorry I didn't note PRI Try setting the route to Pool 15 (a non existing pool)


----------------------------
Hill?? What hill??
I didn't see any $%@#(*$ Hill!!
----------------------------
JerryReeve
Communication Systems Int'l
com-sys.com