On 26/03/2012, at 9:21 PM, Jeremy Malcolm wrote: > Thanks for the tip, it looks like UDP packets to the server I'm forwarding to > are being blocked somewhere. :-( Will take this up with my ISP, or something.
No, sorry but I can rule that out now: I did some test calls from my static-IP opensips box to my dynamic-IP Asterisk box and they worked. I can also confirm I am receiving calls from my DID provider to my static-IP machine and that opensips is trying to redirect them, but the DID provider is not following the redirection. This is what ngrep sees on my static-IP box when a call is made by the DID provider (11.22.33.44 or dynamic.ip.box is my dynamic-IP box, 55.66.77.88 or static.ip.box is my static IP box, 99.00.11.22 is the DID provider, 33.44.55.66 is the caller); it sees the redirect going out to the DID provider, and the acknowledgement of that: # U 55.66.77.88:5060 -> 99.00.11.22:5060 SIP/2.0 302 Redirect. Via: SIP/2.0/UDP 99.00.11.22;branch=z9hG4bK4d2d.45a98547.0. Via: SIP/2.0/UDP 33.44.55.66:16000;received=33.44.55.66;branch=z9hG4bK-d8754z-2d409d3e55d94f1e-1---d8754z-;rport=16000. To: <sip:[email protected]:5060>;tag=61ae7837698e5c9f3ea027df6cb50162.f190. From: "caller"<sip:[email protected]>;tag=7b050e32. Call-ID: NDcxNDQyYjAwNWI5MTEzMjgwNDBkMWU1NDY0OTY4NTk.. CSeq: 1 INVITE. Contact: sip:[email protected], sip:[email protected]:9. Server: OpenSIPS (1.8.0-beta-notls (x86_64/linux)). Content-Length: 0. . # U 99.00.11.22:5060 -> 55.66.77.88:5060 ACK sip:[email protected] SIP/2.0. Via: SIP/2.0/UDP 99.00.11.22;branch=z9hG4bK4d2d.45a98547.0. Max-Forwards: 69. To: <sip:[email protected]:5060>;tag=61ae7837698e5c9f3ea027df6cb50162.f190. From: "caller"<sip:[email protected]>;tag=7b050e32. Call-ID: NDcxNDQyYjAwNWI5MTEzMjgwNDBkMWU1NDY0OTY4NTk.. CSeq: 1 ACK. Content-Length: 0. . So this is all correct, and should make the DID provider redirect the call? If so, where to troubleshoot from here? Nothing is coming through at the dynamic-IP box at all. I also tried using the dynamic-IP box's IP address instead of its domain name, in case it was a DNS caching issue. Is the DID provider at fault for not following the redirect as it should? -- Jeremy Malcolm PhD LLB (Hons) B Com Internet and Open Source lawyer, consumer advocate and geek host -t NAPTR 5.9.8.5.2.8.2.2.1.0.6.e164.org|awk -F! '{print $3}
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
