Remote Call Forward problems

[HUGWideBoy]

Local switch is a 81 running Succesion 4

Remote switch is a 61 running 25.40

Looked at all the standard things..

Both have SCPW lenghs of 4
Both use *5 as the activation FFC

Remote switch
TYPE FFC_DATA
CUST 00
CCRS UNR
SCPL 4
SBUP YES
FFCS NO
STRL 1
STRG #
ADLD 0

Local Switch
TYPE FFC_DATA
CUST 00
CCRS TLD
SCPL 4
SBUP YES
FFCS NO
STRL 0
STRG
ADLD 0
DFLT_SCPW NO



Remote Switch


DCH 13 IMSG FACILITY REF 00000000 CH 0 TOD 15:43:08
FEAT :RCFW

DCH 13 OMSG FACILITY REF 00000000 CH 0 TOD 15:43:08
FEAT :RCFW

DCH 13 IMSG FAC REJ REF 00000000 CH 0 TOD 15:43:08
FEAT :RCFW

DCH 13 OMSG FACILITY REF 00000000 CH 0 TOD 15:43:08
FEAT :NONE

DCH 13 IMSG FACILITY REF 00000000 CH 0 TOD 15:43:08
FEAT :NONE



Local Switch

DCH 26 OMSG FACILITY REF 00000000 CH 0 TOD 15:43:08
STATUS: UNKNOWN
FEAT :RCFW

DCH 26 IMSG FACILITY REF 00000000 CH 0 TOD 15:43:08
FEAT :RCFW

DCH 26 OMSG FAC REJ REF 00000000 CH 0 TOD 15:43:08
STATUS: UNKNOWN
FEAT :RCFW

DCH 26 IMSG FACILITY REF 00000000 CH 0 TOD 15:43:08
FEAT :NONE

DCH 26 OMSG FACILITY REF 00000000 CH 0 TOD 15:43:08
STATUS: UNKNOWN
FEAT :NONE


Any Idea what's going wrong ?

 

[mluckie1]

What are you trying to accomplish? Cannot determine from your post.

 

[HUGWideBoy]

trying to get remote call forwarding working....

But all I get is a horrible reject messages

 

[mluckie1]

To activate RCFW from outside of the local switch, you must use the Direct Inward System Access (DISA) DN.

 

[HUGWideBoy]

Trying to activate from another meridian within the same local network over ISDN tie lines.

 

[johnpoole]

dial the acod of the pri ties between the switches, then *5 + scpw +dn +forward dest #

john poole
bellsouth business
columbia,sc

 

[kprintz]

What are you dialing to activate RCFW? Based on what I see, you should be dialing *5 + 4 + number of the set to be forwarded + number of the set calls will be forwarded + #.
The number of the set to be forwarded and the set which will receive the calls must be dialed the same way as you dial them on your network.

 

[johnpoole]

what i am seeing is *5 on your 81c is a feature code, it never hits the remote network. if the acod does not work, i would use a vacant dn to build a dsc, then a dgt to delete the actual dialed digits and insert the *5

john poole
bellsouth business
columbia,sc

 

[HUGWideBoy]

John, Kprintz,

Food for thought there guys, cheers.

Sure though that I had this working before on 4 option 11's with the *5 travelling the network.

It's certainly strange...you can see the feature getting sent down the D channel, reaching the other switch..2 more messages are sent between the switchs before the reject message.

This is a new network I've just started looking after, and networked features hasn't been used much...(you may have seen another post this week about network time sync not working on all of them)

I'm still leaning towards some sorta conflict between the succession 4 switches and those on 25.40

well lads, I recon I'm gunna be bug fixing these for a few more weeks....if I find any soluction I'll be sure to post them here.

as Usual many many thanks

Wide

 

[johnpoole]

could be that interface problem, since the *5 does hit a trunk, my concern would be how does the switch decide where to send the *5? this problem and network time sync could both be caused by a single switch with the pni number not a match in the cdb as well as network trunks not marked internal.. had a network time problem a few years back that was caused by that. even though the routes were internal, i set up call forward by call type and one opt 11, refused to follow the internal hunt. that turned out to require a patch, but had to be rls 21 or so

john poole
bellsouth business
columbia,sc

 

[johnpoole]

another thing to test, it seems that it could work host to user, but might conflict user to host because of the path of the (p)data

john poole
bellsouth business
columbia,sc

 

[HASAGO]

Does it work the other way? From the 61C to 81C? I am curios as the documentation does state as previously mentioned that to activate the feature remotley you must dial in via a DISA and then enter the codes? Another thing you could check is that there is no STRG configured on the local PABX. You could try configuring. I really think you will need to get across to the other PABX first then dial the *5 etc...
Hope this helps?

 

[johnpoole]

seems like disa for a non networked switch is a must, if i dial disa to my switch, i can rcfw because i access 81c dialtone. in a networked switch i would think that i would need to access the 61c dialtone before *5. BUT if my network allows me to dial 1234 direct to an ext on the 81, *5 7777 1234 should find 1234 just the same patch as the dial pattern. that may be why you don't need disa or tie trunk acod to rcfw on an intergrated network. might be looking at a patch

john poole
bellsouth business
columbia,sc

 

[HUGWideBoy]

Just a small update...

after much hair pulling we found a couple of switches in our network that managed to do this..

after checking working and non working config's

found that some of our switches has LOC defined under NET, ISDN in ld 15

removing these entries, solved the problem.

Thanks again for everyone that helped out

 

[johnpoole]

that would block network wide features a problem

john poole
bellsouth business
columbia,sc