- This topic has 2 replies, 1 voice, and was last updated 20 years, 3 months ago by Teodor Georgiev.
-
AuthorPosts
-
7th October 2004 at 13:17 #28226ohmsGuest
please my system was working well till some time now. My box gives me this message:2000/01/01|00:04:32:575 OrigNum=0112379365946 NormNum=01123793659
46 TranNum=0112379365946 OrigDest=.
ch |01/01| 2000/01/01|00:04:32:600 h323[33]: tcall:stackSendSetup, media typ
e=9
ch |01/01| 2000/01/01|00:04:32:600 H323TermCall: relaying calling party # =
2370029.
ch |01/01| 2000/01/01|00:04:32:600 h323[0]: h323mgr:newCall
ch |01/01| 2000/01/01|00:04:32:670 CasManager: [2,0,1,1] Received message fr
om cas: InbandSigDone.
ch |01/01| 2000/01/01|00:04:32:700 [33/0]: Trying Route to 66.165.170.165ch |01/01| 2000/01/01|00:04:32:700 tcall[33]:DoOutboundSetup() iprgIndex=0 n
umOutCalls=1/-1 maxTalkTime=0 digitRelay=0.
ch |01/01| 2000/01/01|00:04:32:700 h323[33] [0]: tcall:doTranslation inc=0 i
prgIndex=0.
excp |01/01| 2000/01/01|00:04:35:730 323call : OSCF: Remote IP: 66.165.170.165ch |01/01| 2000/01/01|00:04:35:735 h323[33] [0]: tcall:RcvRelComp, cause=34
reason=0.
ch |01/01| 2000/01/01|00:04:35:735 OBCSM[33]: Release from peer=0x962bd9a4 c
ause=0x22 redir=.
ch |01/01| 2000/01/01|00:04:35:735 TBCSM [33]: Release complete from peer=0x
962bc998.
ch |01/01| 2000/01/01|00:04:35:735 OBCSM[33]: Trying another route.
ch |01/01| 2000/01/01|00:04:35:735 Route response [33]: result=0 cause=34.
ch |01/01| 2000/01/01|00:04:35:735 CallInfo [33]: sendFailed Event.
ch |01/01| 2000/01/01|00:04:35:735 tsi connect: 000 1009 10
ch |01/01| 2000/01/01|00:04:35:785 CasManager: [2,0,1,1] Sent message to cas
: Alert.
ch |01/01| 2000/01/01|00:04:37:990 CasManager: [2,0,1,1] Received message fr
om cas: RelComp.
ch |01/01| 2000/01/01|00:04:37:990 CallInfo[33]: disconnected event. cause=1
6 legno=0.
what can be the problem.i think there is a problem at my relay or somethig. please help8th October 2004 at 02:01 #28227NonameGuestLooks like a call to Cameroon got rejected by the remote end, or the termina ting point.
The gateway is up, but for some reason it does not accept the call from you.Best regards
8th October 2004 at 07:32 #28228Teodor GeorgievGuestOSCF error message comes from (On Socket Connect Fail), which means that you can not open a TCP socket to the t e r m i n a t e d gateway. It is a pure IP problem, rather than VoIP.
-
AuthorPosts
- The forum ‘Voice over IP’ is closed to new topics and replies.