I have not read the MS Teams article, but from a SIP perspective your ACK is 
malformed. The Request URI in the ACK - and any other sequential requests - 
must be the Contact URI from the 200 OK response. Your ACK Request URI has the 
parameters from the Contact header, but the domain/host is different. I'm 
guessing your script may be modifying that value as it passes the ACK through?

Also, your ACK does not contain the complete Route set from the 200 OK, it only 
contains the first entry.

Ben Newlin 

On 4/29/20, 10:00 AM, "Users on behalf of Santi Anton" 
<users-boun...@lists.opensips.org on behalf of santi.an...@quarea.com> wrote:

    Hello Ben,

    I agree. These are the INVITE and 200 OK. I only could see that to and from
    tag an Call-ID are the same. I think that in the article there is nothing
    about modifying ACK headers to make it work.


    INVITE sip:5...@sip.pstnhub.microsoft.com SIP/2.0
    Record-Route:
    <sip:sbc.xxxxxxxxxx.com:5067;transport=tls;lr;did=12a.a46808d1;r2=on>
    Record-Route: <sip:195.xx.xx.xx:5060;lr;did=12a.a46808d1;r2=on>
    Via: SIP/2.0/TLS 195.xx.xx.xx:5067;branch=z9hG4bK2f83.ee24a46.0
    Via: SIP/2.0/UDP
    
80.xx.xx.xx.xx:5060;received=80.xx.xx.xx.xx;branch=z9hG4bK4df6ca5c;rport=5060
    Max-Forwards: 69
    From: <sip:935441...@80.xx.xx.xx.xx>;tag=as7659f57d
    To: <sip:5...@sbc.xxxxxxxxxx.com:5068>
    Contact: <sip:935441...@80.xx.xx.xx.xx:5060>
    Call-ID: 433371746cb44b7d76fdc42013bf9...@80.xx.xx.xx.xx:5060
    CSeq: 102 INVITE
    User-Agent: FPBX-12.0.76.6(11.20.0)
    Date: Mon, 27 Apr 2020 16:25:24 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO,
    PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Type: application/sdp
    Content-Length: 1470


    SIP/2.0 200 OK
    FROM: <sip:935441...@80.xx.xx.xx.xx>;tag=as7659f57d
    TO: <sip:5...@sbc.xxxxxxxxxx.com:5068>;tag=50fe42a7fdb64fe583c1089a0b47f44a
    CSEQ: 102 INVITE
    CALL-ID: 433371746cb44b7d76fdc42013bf9...@80.xx.xx.xx.xx:5060
    VIA: SIP/2.0/TLS 195.xx.xx.xx:5067;branch=z9hG4bK2f83.ee24a46.0,SIP/2.0/UDP
    
80.xx.xx.xx.xx:5060;received=80.xx.xx.xx.xx;branch=z9hG4bK4df6ca5c;rport=5060
    RECORD-ROUTE:
    
<sip:sip-du-a-eu.pstnhub.microsoft.com:5061;transport=tls;lr>,<sip:sbc.xxxxxxxxxx.com:5067;transport=tls;lr;did=12a.a46808d1;r2=on>,<sip:195.xx.xx.xx:5060;lr;did=12a.a46808d1;r2=on>
    CONTACT:
    
<sip:api-du-b-euwe.pstnhub.microsoft.com:443;x-i=0c135a71-ddec-454c-a506-91079cb038d7;x-c=385a4453fc885c0bb6276a40d7796d3a/s/1/e1c45d052842415e9c0b3b0b04e32791>
    CONTENT-LENGTH: 827
    SUPPORTED: timer
    CONTENT-TYPE: application/sdp
    ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY
    SESSION-EXPIRES: 3600;refresher=uas
    SERVER: Microsoft.PSTNHub.SIPProxy v.2020.4.20.2 i.EUWE.6

    Best Regards,



    --
    Sent from: 
http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html

    _______________________________________________
    Users mailing list
    Users@lists.opensips.org
    http://lists.opensips.org/cgi-bin/mailman/listinfo/users


_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to