Problems inviting to dests behind ipv6 gateway (event [nua_r_invite] status [904][Operation has no matching challenge ])
Hi all, I'm trying to configure FS to have a SIP gateway that points to an ipv6 address, but somehow proxy-auth doesn't work.. Situation: IPv4 UA ---INVITE---> IPv4 SIP Profile @ FS1 / IPv6 SIP Profile @ FS1 ---INVITE---> IPv6 SIP Profile @ FS2 I defined a sip-profile on FS1 containing this gateway: <profile name="transit-v6"> <gateway name="sv-dev-v6"> <param name="ping" value="0"/> <param name="caller-id-in-from" value="false"/> <param name="register" value="true"/> <param name="username" value="fs-home"/> <param name="proxy" value="[2001::2]"/> <param name="context" value="default"/> <param name="realm" value="test.org"/> <param name="password" value="secret"/> </gateway> ..etc.. And on FS2, the directory contains that same user. First of all the registration (www-auth) from FS1 to FS2 works perfectly, though it took me some time to figure out that the proxy attribute in the gateway definition on FS1 needed to be in square brackets (this is correct, isn't it ?) Now if I send an INVITE from FS1 to FS2: bridge - sofia/gateway/sv-dev-v6/555 Via: SIP/2.0/UDP [2001::1];rport;branch=z9hG4bK6veN1ZQmKpe6K Max-Forwards: 69 From: "gigaset" <sip:fs-home@test.org;transport=udp>;tag=5mv546FcrjZDQ To: <sip:555@[2001::2]> Call-ID: 559effe2-13f4-122c-5687-00065b3a9659 CSeq: 105842223 INVITE Contact: <sip:fs-home@[2001::1]:5060;transport=udp> User-Agent: FreeSWITCH-mod_sofia/1.0.trunk-9854M Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE, SUBSCRIBE, NOTIFY, REFER, UPDATE, REGISTER, INFO Supported: precondition, path, replaces Allow-Events: talk Content-Type: application/sdp Content-Disposition: session Content-Length: 364 Remote-Party-ID: "test" <sip:test@fs-home.org>;screen=yes;privacy=off the latter replies - as expected - with a 407 Proxy Authentication Required: SIP/2.0 407 Proxy Authentication Required Via: SIP/2.0/UDP [2001::1];rport=5060;branch=z9hG4bK6veN1ZQmKpe6K From: "gigaset" <sip:fs-home@test.org;transport=udp>;tag=5mv546FcrjZDQ To: <sip:555@[2001::2]>;tag=8ZymyrBNppUrp Call-ID: 559effe2-13f4-122c-5687-00065b3a9659 CSeq: 105842223 INVITE User-Agent: FreeSWITCH-mod_sofia/1.0.trunk-9852M Accept: application/sdp Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE, SUBSCRIBE, NOTIFY, REFER, UPDATE, REGISTER, INFO Supported: precondition, path, replaces Allow-Events: talk Proxy-Authenticate: Digest realm="[2001::2]", nonce="c781992f- b5fa-49d1-a67c-a40b19e5b6b0", algorithm=MD5, qop="auth" Content-Length: 0 Debug log on FS1 show this: 2008-10-13 19:49:11 [DEBUG] sofia.c:2255 sofia_handle_sip_i_state() Channel sofia/transit-v6/555 entering state [calling] 2008-10-13 19:49:11 [DEBUG] sofia.c:200 sofia_event_callback() event [nua_r_invite] status [407][Proxy Authentication Required] session: sofia/transit-v6/555 2008-10-13 19:49:11 [DEBUG] sofia_reg.c:1134 sofia_reg_handle_sip_r_challenge() Authenticating 'FreeSWITCH' with 'Digest:"[2001::2]":fs-home:secret'. 2008-10-13 19:49:11 [DEBUG] sofia.c:200 sofia_event_callback() event [nua_r_invite] status [904][Operation has no matching challenge ] session: sofia/transit-v6/555 2008-10-13 19:49:11 [DEBUG] sofia.c:200 sofia_event_callback() event [nua_i_state] status [904][Operation has no matching challenge ] session: sofia/transit-v6/555 2008-10-13 19:49:11 [DEBUG] sofia.c:2255 sofia_handle_sip_i_state() Channel sofia/transit-v6/555 entering state [terminated] 2008-10-13 19:49:11 [NOTICE] sofia.c:2735 sofia_handle_sip_i_state() Hangup sofia/transit-v6/555 [CS_CONSUME_MEDIA] [NORMAL_UNSPECIFIED] 2008-10-13 19:49:11 [DEBUG] switch_channel.c:1434 switch_channel_perform_hangup() Send signal sofia/transit-v6/555 [KILL] 2008-10-13 19:49:11 [DEBUG] switch_core_session.c:727 switch_core_session_signal_state_change() Send signal sofia/transit- v6/555 [BREAK] 2008-10-13 19:49:11 [DEBUG] switch_core_state_machine.c:444 switch_core_session_run() (sofia/transit-v6/555) State CONSUME_MEDIA going to sleep 2008-10-13 19:49:11 [DEBUG] switch_core_state_machine.c:367 switch_core_session_run() sofia/transit-v6/555 Running State Change CS_HANGUP 2008-10-13 19:49:11 [DEBUG] switch_core_state_machine.c:395 switch_core_session_run() (sofia/transit-v6/555) State HANGUP After which FS1 sends a 500 Internal Server Error to the IPv4 UA that sent the initial invite. Does anyone know what the "status [904][Operation has no matching challenge ]" means ? The invite does work when FS2 has auth-calls set to false on the incoming profile. thanks, Leon
That could be the fact we aren't a proxy but a b2bua. You will need to either auth each leg end to end along the call path or not auth calls. /b On Oct 13, 2008, at 1:41 PM, Leon de Rooij wrote:
proxy-auth doesn't work..
Of course, I know fs is a b2bua. But FS sends 407 Proxy-Authentication required for authenticating an INVITE. Only for REGISTERs it sends WWW- Authenticate req messages. That's what I meant. So do you mean the "status [904][Operation has no matching challenge ]" message on the originating switch is because the terminating switch sent a Proxy-Authenticate req message ? regards, Leon On Oct 13, 2008, at 10:50 PM, Brian West wrote:
That could be the fact we aren't a proxy but a b2bua. You will need to either auth each leg end to end along the call path or not auth calls.
/b
On Oct 13, 2008, at 1:41 PM, Leon de Rooij wrote:
proxy-auth doesn't work..
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Can you start FreeSWITCH with TPORT_LOG=1 ./freeswitch and see if you can get a sip trace or even use sipgrep to get the trace of what is going on? /b On Oct 14, 2008, at 1:16 AM, Leon de Rooij wrote:
Of course, I know fs is a b2bua. But FS sends 407 Proxy-Authentication required for authenticating an INVITE. Only for REGISTERs it sends WWW- Authenticate req messages. That's what I meant.
So do you mean the "status [904][Operation has no matching challenge ]" message on the originating switch is because the terminating switch sent a Proxy-Authenticate req message ?
regards,
Leon
Hi Brian, I'll try starting the switch with the arguments today. I've always been using ngrep for tracing (sip) traffic, but somehow, it won't show ipv6 traffic :-/ Now, while typing this mail, I discover scripts/trace/sipgrep that comes with fs :-) But it seems to also use ngrep, so it doesn't work.. Ah well, I'll try getting the trace from fs and play with this later. regards, Leon On Oct 14, 2008, at 4:28 PM, Brian West wrote:
Can you start FreeSWITCH with TPORT_LOG=1 ./freeswitch and see if you can get a sip trace or even use sipgrep to get the trace of what is going on?
/b
On Oct 14, 2008, at 1:16 AM, Leon de Rooij wrote:
Of course, I know fs is a b2bua. But FS sends 407 Proxy- Authentication required for authenticating an INVITE. Only for REGISTERs it sends WWW- Authenticate req messages. That's what I meant.
So do you mean the "status [904][Operation has no matching challenge ]" message on the originating switch is because the terminating switch sent a Proxy-Authenticate req message ?
regards,
Leon
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Hi, Sorry it took a while, but I wanted to see for myself whether I could find out what the problem is, though I still don't see it.. Part of sofia.conf on the originating switch: http://pastebin.freeswitch.org/5881 Trace of the call that goes wrong: http://pastebin.freeswitch.org/5882 Thanks, Leon On Oct 14, 2008, at 4:28 PM, Brian West wrote:
Can you start FreeSWITCH with TPORT_LOG=1 ./freeswitch and see if you can get a sip trace or even use sipgrep to get the trace of what is going on?
/b
On Oct 14, 2008, at 1:16 AM, Leon de Rooij wrote:
Of course, I know fs is a b2bua. But FS sends 407 Proxy- Authentication required for authenticating an INVITE. Only for REGISTERs it sends WWW- Authenticate req messages. That's what I meant.
So do you mean the "status [904][Operation has no matching challenge ]" message on the originating switch is because the terminating switch sent a Proxy-Authenticate req message ?
regards,
Leon
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
I think I see what is going on here, will try to get it set up to test. Mike On Oct 17, 2008, at 7:49 AM, Leon de Rooij wrote:
Hi,
Sorry it took a while, but I wanted to see for myself whether I could find out what the problem is, though I still don't see it..
Part of sofia.conf on the originating switch: http://pastebin.freeswitch.org/5881
Trace of the call that goes wrong: http://pastebin.freeswitch.org/5882
Thanks,
Leon
On Oct 14, 2008, at 4:28 PM, Brian West wrote:
Can you start FreeSWITCH with TPORT_LOG=1 ./freeswitch and see if you can get a sip trace or even use sipgrep to get the trace of what is going on?
/b
On Oct 14, 2008, at 1:16 AM, Leon de Rooij wrote:
Of course, I know fs is a b2bua. But FS sends 407 Proxy- Authentication required for authenticating an INVITE. Only for REGISTERs it sends WWW- Authenticate req messages. That's what I meant.
So do you mean the "status [904][Operation has no matching challenge ]" message on the originating switch is because the terminating switch sent a Proxy-Authenticate req message ?
regards,
Leon
participants (3)
-
Brian West
-
Leon de Rooij
-
Michael Jerris