Welcome Guest ( Log In | Register )


 
Reply to this topicNew Topic
transfer request Gateway to Interpel
enmanuelor
post Oct 12 2009, 03:50 PM
Post #1


Contributor
**

Group: Members
Posts: 21
Joined: 24-April 09
Member No.: 480


Hi:

I'm trying to make a transfer request from Gateway to Interpel in Mode Initator-Send but I'm getting some error in both sides:

Log Gateway:
FPSIT025I 06.10.2008 21:10:23 INTRAWEB01(20) [0] connection request sent by DEVSRV01.
NET101I 06.10.2008 21:10:23 (21) outgoing connection request [src_add="/0",dest_add="172.16.0.22/6330"].
NET104I 06.10.2008 21:10:23 (21) outgoing connection confirmation [resp_add="172.16.0.20/59982"].
NET105I 06.10.2008 21:10:24 (21) disconnection request [reason="0"].
SUP006W 06.10.2008 21:10:24 INTRAWEB01(31457300) connection in requester mode refused: reason="166, Connection failure" / prot.diag="301, Called party identification not known".

Log Interpel
NET102I 07.10.2009 07:22:51 (21) incoming connection indication [src_add="172.16.0.20/59982",dest_add="172.16.0.22/6330"].
NET103I 07.10.2009 07:22:51 (21) incoming connection response [resp_add="172.16.0.20/59982"].
FPS024I 07.10.2009 07:22:52 DEVSRV01(20) [0] connection request received for INTRAWEB01.
SUP004I 07.10.2009 07:22:52 DEVSRV01(20) connection in server mode refused: reason="13, Invalid local identifier ".

From Interpel to Gateway and mode send/pull is working fine.

If you need some extra information, don't hesitate in asking me

I hope you can help me.

Regards
Go to the top of the page
 
+Quote Post
jmmahieu
post Oct 13 2009, 05:43 PM
Post #2


Contributor
**

Group: Members
Posts: 14
Joined: 6-November 08
From: Puteaux
Member No.: 140


QUOTE (enmanuelor @ Oct 12 2009, 05:50 PM) *
Hi:

I'm trying to make a transfer request from Gateway to Interpel in Mode Initator-Send but I'm getting some error in both sides:

Log Gateway:
FPSIT025I 06.10.2008 21:10:23 INTRAWEB01(20) [0] connection request sent by DEVSRV01.
NET101I 06.10.2008 21:10:23 (21) outgoing connection request [src_add="/0",dest_add="172.16.0.22/6330"].
NET104I 06.10.2008 21:10:23 (21) outgoing connection confirmation [resp_add="172.16.0.20/59982"].
NET105I 06.10.2008 21:10:24 (21) disconnection request [reason="0"].
SUP006W 06.10.2008 21:10:24 INTRAWEB01(31457300) connection in requester mode refused: reason="166, Connection failure" / prot.diag="301, Called party identification not known".

Log Interpel
NET102I 07.10.2009 07:22:51 (21) incoming connection indication [src_add="172.16.0.20/59982",dest_add="172.16.0.22/6330"].
NET103I 07.10.2009 07:22:51 (21) incoming connection response [resp_add="172.16.0.20/59982"].
FPS024I 07.10.2009 07:22:52 DEVSRV01(20) [0] connection request received for INTRAWEB01.
SUP004I 07.10.2009 07:22:52 DEVSRV01(20) connection in server mode refused: reason="13, Invalid local identifier ".

From Interpel to Gateway and mode send/pull is working fine.

If you need some extra information, don't hesitate in asking me

I hope you can help me.

Regards


You have the answer in the interpel log
SUP004I 07.10.2009 07:22:52 DEVSRV01(20) connection in server mode refused: reason="13, Invalid local identifier

That's means that Interpel is using the default local identifier attached to the key and you try to transfer from Gateway to a partner which is not this identifier. Check the Remote site definition in Gateway where the protocol identifier should correspond to the local identifier of Interpel. Otherwise define another local site in Interpel and attach it to the remote site in Interpel.

It's working fine in the other way as Gateway accept any local site name which will be created automatically. You could find it in the local partner with a prefix $L_.....

Regards
JMM


--------------------
JM MAHIEU
Go to the top of the page
 
+Quote Post
enmanuelor
post Oct 13 2009, 06:58 PM
Post #3


Contributor
**

Group: Members
Posts: 21
Joined: 24-April 09
Member No.: 480


QUOTE (jmmahieu @ Oct 13 2009, 06:43 PM) *
You have the answer in the interpel log
SUP004I 07.10.2009 07:22:52 DEVSRV01(20) connection in server mode refused: reason="13, Invalid local identifier

That's means that Interpel is using the default local identifier attached to the key and you try to transfer from Gateway to a partner which is not this identifier. Check the Remote site definition in Gateway where the protocol identifier should correspond to the local identifier of Interpel. Otherwise define another local site in Interpel and attach it to the remote site in Interpel.

It's working fine in the other way as Gateway accept any local site name which will be created automatically. You could find it in the local partner with a prefix $L_.....

Regards
JMM


Hi JMM:

I've defined both remote site in both sides, In gateway I defined Intepel(INTRAWEB01) in Gateway Navigator and Gateway(DEVSRV01) in Interpel. I think it is something else because it's working from Interpel to Gateway with the same Remote Sites (pull/receive). I tried to attach some images but these are a little heavy, if you want I can send you the images so that you can see more details about this problem.

Regards

Go to the top of the page
 
+Quote Post

Reply to this topicNew Topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 

Skin designed by IPB Forum Skins