Openscape 4000 V7 link to Openscape Business X8: OS4000 cannot call to X8 numbers

[Hertz]

Hello Gents,

I hope you guys are all good.

MY OS4000 cannot call to a OSBIZ X8 station. But if the call is vice versa(X8 to 4K) call is good and passing thru.

The calls are thru IP (ECMAV2). You can check the image below

Here's reg format as well
ADD-BUEND:507,"OS4000 -> X8 ",60 ,0 ,* ,2 ,ON ,0 ,0 ,NEUTRAL;
ADD-TDCSU:NEW ,1-01-085-0,202,203,0,0,200,1,1," ",250 ,ECMAV2,8,,NONE,,,,GDTR,N,TIE,NONE,N,0,,,,,, ,10,MANY,250,0,1,1,EMPTY,202,5,N,
,,,,,16,8,1,10,,EC&G711&G729AOPT
,"",507,DSC,Y,TRADITIO,0,60,60,HG3550IP,
1&&10
,N,1,,0,0,0,0,0,N
;
ADD-GKREG:871,EXTGW,192.168.1.39,796999,0,0,1,"",TRADITIO;
ADD-COT: 202,PRI&RCL&XFER&ANS&USD&AEOD&KNOR&CEBC&CBBN&CBFN&COTN&IEVT&BSHT&BLOC&PROV&LWNC&ATRS&ROPT&NLCR&TSCS&TRSC&DFNN& CFOS&NLRD&PINR&AOCC&LINO&NQPI&NOFT&NQNP&AMFC&IBBA&NTON;
ADD-COP:203,ANS&SFRM&RLSA&DTN&NO1A,TA,TA;
ADD-COSSU:,200,,,,,,,,"";
CHA-COSSU:COS,200,TA&TSUID&TNOTCR&CDRC&FWDNWK;
CHA-COSSU:COS,200,,NOCO&NOTIE;
CHA-COSSU:COS,200,,,NOCO&NOTIE;
ADD-RICHT:CD,507,***205,,,0,VCE,"OS4000 -> X8 ",,,507,,,,250,,,,,,250,,,250,NEUTRAL,NO,NO,,NO;
CHANGE-RICHT:CD,***205,,0,VCE,DTMF,FIX,DIGITS,"PLEASE WAIT ",PP80;

Good quality on OSBIZ X8 to 4K but when a station dialed from my 4K dialed a station going to OSBIZ 8. It goes busy even if the local is good.





Best
Hertz

 

[Moriendi]

You haven't posted your CGWB for the STMI or the LDAT for the NWLCR. You haven't defined protocol in the GKREG (SIPQ)

You can use RDS (tracer) on the Assistant to have a closer look at what is happening, does it send setup to the STMI, does it not, etc.

 

[hipath4k]

Also please check in CGWB whehter gatekeeper is showung registered?

 

[Hertz]

Hello @Moriendi,

here's my CGWB and the LDAT

ADD-CGWB:1,85,NORMAL,192.168.1.224,255.255.255.0;
CHANGE-CGWB:CGW,1,85,GLOBIF,,,213,NO,0,0.0.0.0,,100MBFD,0,0,10,0,4061,0.0.0.0,0.0.0.0,NO,5060,5061;
CHANGE-CGWB:CGW,1,85,SERVIF,"TRM";
CHANGE-CGWB:CGW,1,85,ASC,29100,30099,184,104,YES,NO,YES,YES,PRIO1,G711A,NO,30;
CHANGE-CGWB:CGW,1,85,ASC,,,,,,,,,PRIO2,G729A,NO,20;
CHANGE-CGWB:CGW,1,85,ASC,,,,,,,,,PRIO3,G723,NO,30;
CHANGE-CGWB:CGW,1,85,ASC,,,,,,,,,PRIO4,NONE,NO,20;
CHANGE-CGWB:CGW,1,85,ASC,,,,,,,,,PRIO5,NONE,NO,20;
CHANGE-CGWB:CGW,1,85,ASC,,,,,,,,,PRIO6,NONE,NO,20;
CHANGE-CGWB:CGW,1,85,ASC,,,,,,,,,PRIO7,G729AB,YES,20;
CHANGE-CGWB:CGW,1,85,GKDATA,,1719,"PRIMARYRASMANAGERID",,,1719,"SECONDARYRASMANAGERID",,120;
CHANGE-CGWB:CGW,1,85,MGNTDATA,,8000,,443,CLASSIC;
CHANGE-CGWB:CGW,1,85,DMCDATA,0;
CHANGE-CGWB:CGW,1,85,WBMDATA,"HP4K-DEVEL",,ENGR;
CHANGE-CGWB:CGW,1,85,WBMDATA,"HP4K-SU",,SU;
CHANGE-CGWB:CGW,1,85,WBMDATA,"HP4K-ADMIN",,ADMIN;
CHANGE-CGWB:CGW,1,85,WBMDATA,"HP4K-READER",,READONLY;
CHANGE-CGWB:CGW,1,85,GWDATA,"PRIMARYRASMANAGERID",;
CHANGE-CGWB:CGW,1,85,H235DATA,NO,NO,"h235securedgateway",,100,242-191-30-119-188-83-173-161-43-0-70-36-218-74-169-221-78-102-174-170;
CHANGE-CGWB:CGW,1,85,LEGKDATA,870,810000,NO;
CHANGE-CGWB:CGW,1,85,SIPTRERH,NO,,,;
CHANGE-CGWB:CGW,1,85,SIPTRSSA,NO,0.0.0.0,5060,5061,300,0.0.0.0,5060,5061;
CHANGE-CGWB:CGW,1,85,DLSDATA,,10444,NO;
CHANGE-CGWB:CGW,1,85,JB,40,120,20,4,60,200,2;
CHANGE-CGWB:CGW,1,85,MANLANIF,0.0.0.0,0.0.0.0,NO,0,0.0.0.0;

ADD-LDAT:507,VCE,1,,507,207,1,,1,EMPTY,WCHREG,250,4,,,,,,,,871-0,,,,;

thanks in advance

Best
Hertz

 

[Moriendi]

OK, what I really wanted to know was did you specify your GW1 in the LDAT, and you have. So that's OK.

1 - Did you change your IP addresses? Your IP address for CGWB does not match your GKREG INTGW.
2 - You have specified 10 channels of H323 trunk in your CGWB, but 4K has not supported H323 (unless Xpr) since V6 R2.
What software is your 4K?
3 - Your GKREG contains no protocol, you need to CHA-GKREG. I expected SIPQ but I don't see H323 either.

I would correct GKREG, then use RDS to determine if 4K sends a SETUP to the STMI (and you have an issue with STMI configuration) or there is not even a SETUP (and you have a 4K LCR problem).

If there is a SETUP to the STMI, then a Wireshark trace is always very useful here (you can stream directly to Wireshark from the rpcap daemon on the STMI, as long as loadware is not too old).

Correct GKREG and try again...