Hi,
I have found the solution for me.
So, if you have an Asterisk PBX, you have to allow the 484, because
Asterisk PBX will cancel the REFER with 484.
sip/sip_util.c
case 484: /* Address Incomplete */
case 485: /* Ambiguous */
/** @par 484 Address Incomplete and 485 Ambiguous
Similar to 404 and 410, these
responses came to a request whose Request-URI was provided by the
peer in a @Contact header field. Something has gone fundamentally
wrong, and the dialog and all of its usages are destroyed.
*/
if (method == sip_method_refer)
{
*return_graceful_terminate_usage = 0;
return 0;
}
return terminate_dialog;
If that is also interessting for the main branch, I can create an patch!
Best regards,
Bernhard Suttner
Am Mittwoch, den 14.01.2009, 13:50 +0100 schrieb Bernhard Suttner:
Hi,
If I senda refer to the PBX, the PBX does answer with 484 Address
Incomplete. Afterwards, the sofia sip stack does change the call state
from ready to terminated and will fire and event to the application
which does hangup the call. Is there any reason to do it like that?
If I get a 403 Forbidden, the call will not be terminated. Can I
somehow disable that behaviour to termiante the call?
Here is the debug output:
send 623 bytes to udp/[10.42.1.81]:5060 at 13:37:42.946933:
REFER sip:3...@10.42.1.81 SIP/2.0
Via: SIP/2.0/UDP 10.42.1.27:12000;rport;branch=z9hG4bK2gm1v3KN8ytSF
Max-Forwards: 70
From: sip:7...@10.42.1.27:12000;tag=1U6Q21Dmv8tFN
To: Int3323 sip:3...@10.42.1.81;tag=as27479c05
Call-ID: 331f916157810eb56ef065fc361cb...@10.42.1.81
CSeq: 109851795 REFER
Contact: sip:7...@10.42.1.27:12000
User-Agent: APPL
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE,
SUBSCRIBE, NOTIFY, REFER, UPDATE, REGISTER, INFO
Supported: precondition, timer, pref
Refer-To: sip:03521463221532...@10.42.1.81
Referred-By: sip:7...@10.42.1.81
Content-Length: 0
nta: sent REFER (109851795) to */10.42.1.81:5060
nta: timer shortened to 500 ms
nua(0xb6002eb8): event r_refer 100 Trying
recv 482 bytes from udp/[10.42.1.81]:5060 at 13:37:42.947820:
SIP/2.0 484 Address Incomplete
Via: SIP/2.0/UDP
10.42.1.27:12000;branch=z9hG4bK2gm1v3KN8ytSF;received=10.42.1.27;rport=12000
From: sip:7...@10.42.1.27:12000;tag=1U6Q21Dmv8tFN
To: Int3323 sip:3...@10.42.1.81;tag=as27479c05
Call-ID: 331f916157810eb56ef065fc361cb...@10.42.1.81
CSeq: 109851795 REFER
User-Agent: APPL
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Contact: sip:3...@10.42.1.81
Accept: application/sdp
Content-Length: 0
nta: received 484 Address Incomplete for REFER (109851795)
nta: 484 Address Incomplete is going to a transaction
nta_outgoing: RTT is 1.517 ms
nua(0xb6002eb8): event r_refer 484 Address Incomplete
nua(0xb6002eb8): removing subscribe usage with event refer
nua(0xb6002eb8): removing session usage
nua(0xb6002eb8): call state changed: ready - terminated
nua(0xb6002eb8): event i_state Terminated
nua(0xb6002eb8): event i_terminated Terminated
Thanks for every hint!
Best regards,
Bernhard
--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___ Sofia-sip-devel mailing list
Sofia-sip-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
Sofia-sip-devel mailing list
Sofia-sip-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
