[Spce-user] MR4.4.1 and extrange error with NAT

Fri Aug 26 08:47:19 EDT 2016

I can update information. I have continue with this solution
https://www.sipwise.com/doc/mr3.8.6/spce/ar01s05.html#_audiocodes_devic
es_workaround

but then I can see next error in log

NOTICE: <script>: Appending P-D-URI 'sip:lb at 127.0.0.1;lr;socket=sip:192
.168.220.20:5060' - R=sip:VP770000200 at 88.26.250.100:5066;user=phone ID=
75541f4b1b9b283d526afe7b0d5d529f at 185.51.108.56 UA='Digium Gateway'
2016-08-26T12:48:18.421018+02:00 voip proxy[30633]: NOTICE: <script>:
Forcing request via B2BUA 'sip:192.168.70.2:5080' - R=sip:VP770000200 at 8
8.26.250.100:5066;user=phone ID=75541f4b1b9b283d526afe7b0d5d529f at 185.51
.108.56 UA='Digium Gateway'

In this way LB can route responses to end ua. 

Any idea? We ra using last release 4.4.1

Regards,

Sergio

El jue, 25-08-2016 a las 15:01 +0200, Sergio Serrano escribió:
> Hi all,
> 
> 	I have installed a SPCE with two peers. This SPCE has LAN
> 192.168.220.0 with router 192.168.220.1, in this router you can go to
> the first PEERS with Public IP of Vodafone and all works fine. It's
> said,
> 
> 192.168.220.20 <->(192.168.220.1)Router(Public IP) <-> Vodafone Peer,
> all works fine. 
> 
> Connected to that router there is other Class A with a Gateway
> SIP/ISDN. When you launch a call from PUblic PSTN and this call
> arrive to Gateway and then resend to SPCE, you can see in attachment
> that 100 TRING is route correctly, but after that message SPCE can't
> route SIP MESSAGES. IN logs of kamailio.lb I can see next messages:
> 
> NOTICE: <script>: New request on lb - M=INVITE R=sip:951001104 at 192.16
> 8.220.20 F=sip:649976042 at 192.168.220.20 T=sip:951001104 at 192.168.220.2
> 0 IP=udp:10.254.254.2:5060 ID=223e28ec6a0afa2e0c32749a75a64be3 at 192.16
> 8.220.20 UA='Digium Gateway'
> Aug 25 14:49:22 voip lb[12532]: NOTICE: <script>: Relaying request,
> du='sip:127.0.0.1:5062', fs='udp:127.0.0.1:5060' - R=sip:951001104 at 19
> 2.168.220.20 ID=223e28ec6a0afa2e0c32749a75a64be3 at 192.168.220.20
> UA='Digium Gateway'
> Aug 25 14:49:22 voip lb[12542]: NOTICE: <script>: Reply from Inbound
> - S=100 - Trying M=INVITE IP=udp:127.0.0.1:5062 ID=223e28ec6a0afa2e0c
> 32749a75a64be3 at 192.168.220.20 UA='<null>'
> Aug 25 14:49:22 voip lb[12542]: NOTICE: <script>: Sending reply,
> fs='udp:192.168.220.20:5060' - ID=223e28ec6a0afa2e0c32749a75a64be3 at 19
> 2.168.220.20 UA='<null>'
> Aug 25 14:49:23 voip lb[12541]: NOTICE: <script>: New request on lb -
> M=INVITE R=sip:VP770000200 at B.B.B.B:5066;user=phone F=sip:649976042 at A.
> A.A.A T=sip:VP770000200 at A.A.A.A IP=udp:127.0.0.1:5080 ID=223e28ec6a0a
> fa2e0c32749a75a64be3 at 192.168.220.20_b2b-1 UA='<null>'
> Aug 25 14:49:23 voip lb[12541]: NOTICE: <script>: Relaying request,
> du='<null>', fs='udp:192.168.220.20:5060' - R=sip:VP770000200 at B.B.B.B
> :5066;user=phone ID=223e28ec6a0afa2e0c32749a75a64be3 at 192.168.220.20_b
> 2b-1 UA='<null>'
> Aug 25 14:49:23 voip lb[12534]: NOTICE: <script>: Reply from Outbound
> - S=100 - Trying M=INVITE IP=udp:88.26.250.100:5066 ID=223e28ec6a0afa
> 2e0c32749a75a64be3 at 192.168.220.20_b2b-1 UA='Grandstream GXP2135
> 1.0.7.78'
> Aug 25 14:49:23 voip lb[12534]: NOTICE: <script>: NATed reply
> detected - ID=223e28ec6a0afa2e0c32749a75a64be3 at 192.168.220.20_b2b-1
> UA='Grandstream GXP2135 1.0.7.78'
> Aug 25 14:49:23 voip lb[12534]: NOTICE: <script>: Sending reply,
> fs='udp:127.0.0.1:5060' - ID=223e28ec6a0afa2e0c32749a75a64be3 at 192.168
> .220.20_b2b-1 UA='Grandstream GXP2135 1.0.7.78'
> Aug 25 14:49:23 voip lb[12534]: ERROR: <core> [udp_server.c:550]:
> udp_send(): sendto(sock,0x7f9453857d20,590,0,88.26.250.100:5080,16):
> Invalid argument(22)
> Aug 25 14:49:23 voip lb[12534]: CRITICAL: <core> [udp_server.c:555]:
> udp_send(): invalid sendtoparameters#012one possible reason is the
> server is bound to localhost and#012attempts to send to the net
> Aug 25 14:49:23 voip lb[12534]: ERROR: <core> [forward.h:201]:
> msg_send_buffer(): udp_send failed
> Aug 25 14:49:23 voip lb[12533]: NOTICE: <script>: Reply from Outbound
> - S=180 - Ringing M=INVITE IP=udp:B.B.B.B:5066 ID=223e28ec6a0afa2e0c3
> 2749a75a64be3 at 192.168.220.20_b2b-1 UA='Grandstream GXP2135 1.0.7.78'
> Aug 25 14:49:23 voip lb[12533]: NOTICE: <script>: NATed reply
> detected - ID=223e28ec6a0afa2e0c32749a75a64be3 at 192.168.220.20_b2b-1
> UA='Grandstream GXP2135 1.0.7.78'
> Aug 25 14:49:23 voip lb[12533]: NOTICE: <script>: Sending reply,
> fs='udp:127.0.0.1:5060' - ID=223e28ec6a0afa2e0c32749a75a64be3 at 192.168
> .220.20_b2b-1 UA='Grandstream GXP2135 1.0.7.78'
> Aug 25 14:49:23 voip lb[12533]: ERROR: <core> [udp_server.c:550]:
> udp_send(): sendto(sock,0x7f94538539c0,955,0,B.B.B.B:5080,16):
> Invalid argument(22)
> Aug 25 14:49:23 voip lb[12533]: CRITICAL: <core> [udp_server.c:555]:
> udp_send(): invalid sendtoparameters#012one possible reason is the
> server is bound to localhost and#012attempts to send to the net
> Aug 25 14:49:23 voip lb[12533]: ERROR: <core> [forward.h:201]:
> msg_send_buffer(): udp_send failed 
> 
> When LB answer INVITE is work, but after that, once the INVITE is
> passed to proxy and return LB can't route message.
> 
> Any one can help me with this?
> 
> Regards,
> 
> Sergio
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: This is a digitally signed message part
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160826/9704804f/attachment-0001.asc>