[Spce-user] [spce mr3.2.1] Peering server failover issue

[Daniel Grotti]

Hi,
regarding peering weights:

"Weight is an integer value from 1 to 254. Weight implementation is
fast, but unfair favoring larger weight values at the expense smaller
ones. For example, if two gateways have weights 1 and 2, probability
that the gateway with weight 1 is tried first is 1/4, not 1/3."


So, weights are just a probability to choose a gateway instead of the other.

Regarding the TO header, this is the normal behaviour.
TO contains the original called SIP URI.


8.1.1.2 To

   The To header field first and foremost specifies the desired
   "logical" recipient of the request, or the address-of-record of the
   user or resource that is the target of this request.  This may or may
   not be the ultimate recipient of the request.


During failover ther R-URI changes, not the TO header. So if you are
registered on your peer, it should ask you for the INVITE authentication
sending back a "407 Proxy Authentication Required", and NGCP will add
the "Proxy-Authorization:" in the subsequent INVITE.


Daniel





On 06/18/2014 06:55 PM, JV wrote:
> Hi all,
>
> We have the following situation:
>
> PBX (3CX) (subscriber)=== [SPCE] ==== peer group (outbound) (
> PEER_ONE (weight 1) , PEER_TWO (weight 2) )
>                                         [ 3.2.1 ] ==== peer group
> (inbound)  ( pstn to sip gateway)
>
> I have defined two peering groups: one for outbound calls and one for
> inbound calls.
> We have problems with the outbound peer group.
> This peer group consists of two peering servers, outbound calls should
> go first through PEER_ONE (weight 1) and in case of failure through
> PEER_TWO (weight 2).
> I have configured the peering servers with both the IP address and a
> hostname. Authentication ( user + password + domain ) is also enabled.
>
> Initially, PEER_ONE worked perfectly fine. To test the failover in the
> peering group. I blocked PEER_ONE's ip address and could make calls
> successfully through PEER_TWO.
> I allowed traffic again for PEER_ONE's in order to restore the
> original situation. But for some unknown reason sipwise didn't
> failover to PEER_ONE.
> Calls still were directed to PEER_TWO. After I changed the ip address
> in SPCE to something invalid for PEER_TWO, calls were initiated again
> through PEER_ONE but sipwise didn't pick up the correct host part in
> the SIP TO: field , so calls are not working anymore. Please check the
> trace at the bottom of this message.
>
> Why didn't my sipwise failover automatically to PEER_ONE after this
> peer came available again? Why is sipwise sending a SIP invite to
> PEER_ONE with the wrong host (from PEER_TWO) in the To header field?
> Does sipwise store somewhere the last state for a peer? Any hints are
> welcome! thanks in advance.
>
> U 2014/06/18 16:10:23.198921 sipwise_IP:5060 -> peer_ONE_IP:5060
> INVITE sip:0613XXXXXX at hostname.peer_ONE.com SIP/2.0'
> Max-Forwards: 10'
> Record-Route: <sip:sipwise_IP;r2=on;lr=on;ftag=2F7341FF-53A19DCF000302E5-1A7EC700;ngcplb=yes>'
> Record-Route: <sip:127.0.0.1;r2=on;lr=on;ftag=2F7341FF-53A19DCF000302E5-1A7EC700;ngcplb=yes>'
> Via: SIP/2.0/UDP
> sipwise_IP;branch=z9hG4bKe29a.ce853c511d2dafc252609146749c1697.0'
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKg67DRaXb;rport=5080'
> From: <sip:user_peer_ONE at peer_ONE.com>;tag=2F7341FF-53A19DCF000302E5-1A7EC700'
> To: <sip:0613XXXXXX at hostname.PEER_TWO.com>'
> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! < this should be
> hostname.PEER_ONE.Com !!!!!! how does this come? >
> CSeq: 10 INVITE'
> Call-ID: NmQxZTU2MzM0OGJjZTRmNDZkODFkNjIzNjZiYWVjYzU._b2b-1'
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY,
> REFER, INFO, MESSAGE'
> Supported: replaces'
> P-Asserted-Identity: <sip:318XXXXXXXX at sipwise_IP>'
> P-Preferred-Identity: <sip:8XXXXXXXX at sipwise_IP>'
> Content-Type: application/sdp'
> Content-Length: 447'
> Contact: <sip:ngcp-lb at sipwise_IP:5060;ngcpct=7369703a3132372e302e302e313a35303830>'
>
> ...
> U 2014/06/18 16:10:23.215850 peer_ONE_IP:5060 -> sipwise_IP:5060
> SIP/2.0 401 Unauthorized'
> ...
>
> Regards,
> Joeri
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> http://lists.sipwise.com/listinfo/spce-user