BlindTransfer with 482 Loop Detected help? #441
Replies: 3 comments 3 replies
-
|
I'll need a SIP trace, either from Wireshark or from the sipsorcery logs. To activate logs from a sipsorcery app call |
Beta Was this translation helpful? Give feedback.
-
|
Grateful for the return, follow SipTransport logs 2021-03-05 12:24:16.9605|DEBUG|PRACK sip:[email protected]:5060 SIP/2.0 2021-03-05 12:24:16.9605|INFO|INVITE v=0 2021-03-05 12:24:17.0379|DEBUG|SIP/2.0 200 Ok 2021-03-05 12:24:17.0616|DEBUG|Request received: udp:192.168.20.56:5060<---udp:192.168.20.190:5060 2021-03-05 12:24:19.8590|INFO|Paulinho.wav 2021-03-05 12:24:39.0747|INFO|OPTIONS 2021-03-05 12:24:39.1898|DEBUG|Response sent: udp:192.168.20.56:5060--->udp:192.168.20.170:5060 2021-03-05 12:24:39.5015|DEBUG|Request received: udp:192.168.20.56:5060<---udp:192.168.20.170:5060 2021-03-05 12:24:39.5255|INFO|OPTIONS 2021-03-05 12:24:39.5680|DEBUG|Response sent: udp:192.168.20.56:5060--->udp:192.168.20.170:5060 2021-03-05 12:24:40.5173|DEBUG|Request received: udp:192.168.20.56:5060<---udp:192.168.20.170:5060 2021-03-05 12:24:40.6032|INFO|OPTIONS 2021-03-05 12:24:40.6850|DEBUG|Response sent: udp:192.168.20.56:5060--->udp:192.168.20.170:5060 2021-03-05 12:24:41.2784|INFO|Transferindo para sip:[email protected]:5060=========================> 2021-03-05 12:24:41.4178|DEBUG|Response received: udp:192.168.20.56:5060<---udp:192.168.20.190:5060 2021-03-05 12:24:41.4522|DEBUG|Request received: udp:192.168.20.56:5060<---udp:192.168.20.190:5060 SIP/2.0 100 Trying 2021-03-05 12:24:41.4916|INFO|Saiu SIP/2.0 100 Trying 2021-03-05 12:24:41.5114|INFO|NOTIFY SIP/2.0 100 Trying 2021-03-05 12:24:41.5673|INFO|NOTIFY 2021-03-05 12:24:41.5872|DEBUG|NOTIFY sip:192.168.20.56:5060 SIP/2.0 SIP/2.0 482 Loop Detected 2021-03-05 12:24:41.6074|INFO|NOTIFY 2021-03-05 12:24:41.6657|INFO|NOTIFY SIP/2.0 100 Trying 2021-03-05 12:24:41.7276|INFO|NOTIFY sip:192.168.20.56:5060 SIP/2.0 SIP/2.0 482 Loop Detected |
Beta Was this translation helpful? Give feedback.
-
|
I received a call from "Paulinho" sip: [email protected]: 5060 to sip: [email protected]: 5060, I answered activeAgent.BlindTransfer method used, when i receive from another location if not from sipproxy i can transfer normal, only when i receive a call from sipproxy and i will transfer to another extension of the same siproxy i get the loop |
Beta Was this translation helpful? Give feedback.
-
|
I removed Rota: sip: [email protected]: 5060; transport = udp; lr, I saw that if he has a Route he sends it to the route instead of sending it to the Refer-To, but an error persists. |
Beta Was this translation helpful? Give feedback.
-
|
The INVITE OK response is missing. It can contain some important headers that dictate the REFER request construction. Assuming the OK response is stock standard then the REFER request from the application using the sipsorcery library looks normal except that the URI: This means the SIP server listening on
Technically that's permitted but given the While the INVITE OK response would shed a bit more light my first suggestion would be to remove any If you've already tried that and that my next guess is due to the indication it looks like you might be running the at least one of the SIP servers on AWS. If that's the case then you may be using the |
Beta Was this translation helpful? Give feedback.
-
|
Thank you very much for the information, I help a lot, really the server is rejecting it. Congratulations on the library, very good! |
Beta Was this translation helpful? Give feedback.
-
Hello,
I need help, I have an error trying to transfer to a sipproxy, I get the loop detected, my scenario is ... I get a call from siproxy, I answer and transfer to another extension of the sip proxy, sipuseragent answers and transfers.
Grateful!
Beta Was this translation helpful? Give feedback.
All reactions