Yes, I configure it to _listen_ on port 5062 and the Asterisk should registring _that_ address on the Registrar. So it should register <sip:e...@ip:port> not <sip:e...@ip> (which is <sip:e...@ip:5060>
And it is doing that not only on registers, but also on INVITEs. Follwoing RFC3261, in-dialog messages are sent to the adjacent contact - but if that's wrong in the first place, the server (btw: what do you mean with server?) can't do anything. It would have been told to send it to the wrong port. Following that, I would have also configured him to _listen_ on IPx, so it must not send some other IP in the contact :-) Br Walter -----Ursprüngliche Nachricht----- Von: [email protected] [mailto:[email protected]] Im Auftrag von Chris Mason (Lists) Gesendet: Sonntag, 11. Jänner 2009 14:46 An: Asterisk Users Mailing List - Non-Commercial Discussion Betreff: Re: [asterisk-users] chan_sip on non-standard port 5062 - contact has no port You are configuring Asterisk to LISTEN on 5062 , if you want it to talk to another server on 5062, then configure that server's config stanza accordingly. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
