qsig to cisco callmanager

[bpg1]

hi all

have a tie on qsig with isgf, problem is when 2 cisco ip sets have call forward to each other: ext 9115 to ext 9100.
i get disconnect with cause 98.

anyone know of a patch or anyting else i can do?

 

[johnpoole]

is the call forward in a single direction? not 9155 to 9100 AND 9100 to 9155? that will cause a loop problem but not usualy a disconect. bcm to bcm should be handled via the cisco. that should never be an issue with the merridian. i have the same setup, i never see the forward, a single trunk on the qsig, trad 156 1 shows the original dialed digits eventhough the call has been forwarded to another cisco wireless. when the cisco is routed rna to the mail, it drops the pri trunk and traces from the calling station to the call pilot

john poole
bellsouth business
columbia,sc

 

[bpg1]

hi john

it is only one direction, 9115 to 9100.

the trace of d-canal.


DCH 32 UIPE_OMSG CC_SETUP_REQ REF 00000BB4 CH 4 26 TOD 12:40:14 CK 79FB7FA5
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:1123 NUM PLAN: PRIVATE TON: ESN CDP

CALLED #:9115 NUM PLAN: PRIVATE TON: ESN CDP

DCH 32 UIPE_IMSG CC_PROCEED_IND REF 00000BB4 CH 4 26 TOD 12:40:14 CK 79FB8182


DCH 32 UIPE_IMSG CC_ALERT_IND REF 00000BB4 CH 4 26 TOD 12:40:14 CK 79FB8195
PROGRESS: INBAND INFO OR PATTERN IS AVAIL

DCH 32 UIPE_IMSG CC_DISC_IND REF 00000BB4 CH 4 26 TOD 12:40:14 CK 79FB81AE
CAUSE: #98 - MSG NOT COMPATIBLE WITH STATE

ext 1123 a meridian ext call to cisco ext 9115 that is call forwared to 9100 also cisco ext.

 

[johnpoole]

can you call from a cisco set and follow the forward? the cisco is trying to send that back to the nortel, a call going out on a route is not going to come back on the same route and them go back out on the same route. trmb is not working so the switch see a loop, if that worked and the call could busy out all vacant trunks, not usually a good idea. check the ccm to make sure they are uing the cisco call forward feature code..

john poole
bellsouth business
columbia,sc