[Users] Re: un-asked-for CANCEL being generated

Well, I feel slightly foolish about the post below. The CANCEL I was seeing was perfectly sensible, as it was being sent to a second phone registered to the same username, to say "stop ringing". However, I am still having the same problem, with no good explanation. I don't know if the problem lies with openser or asterisk. But again, it looks like this: Works: Box A Box B ----------------- ------------------- pstn ----------> | openser |------| | | ----------------- | | asterisk | | asterisk |<---- | | ----------------- ------------------ Broken: Box A Box B ----------------- ------------------- pstn ----------> | openser |----------->| | ----------------- | asterisk | | asterisk | | | ----------------- ------------------ To be clear, all instances of openser and asterisk are explicitly bound to public IP addresses, and there are no cases of 127.0.0.1 being used in any config files. with openser acting as a fowarding proxy between asterisk A and asterisk B. If a pstn call coms in to openser and it forwards to asterisk A, everything works fine. If openser forwards to asterisk B (whether with a manual forward, a manual t_relay, or either forward or t_relay using the dispatcher module), the phone sends en error message, one rtp packet, and hangs up. Which is strange because it has already previously responded with a 200 ok sdp packet. If the phone is a counterpath eyebeam, it sends 481 Call/Transaction does not exist. If the phone is a linksys spa 941, it sends Status: 400 Bad Request. This suggests to me that the problem does not lie with the phone. Interestingly, using the spa phone as an example, the call id is the same on the 400 bad request packet as on the 200 ok sdp packet. I can send packet logs. Or if there is any other information I can help you with. Thank you, Mark Price On 4/9/07, Mark Price &lt;markprice(a)gmail.com&gt; wrote: