| Summary: | ASTERISK-12539: Registering asterisk to other port apart from by default 5060 port | ||
| Reporter: | destiny6628 (destiny6628) | Labels: | |
| Date Opened: | 2008-08-08 02:15:05 | Date Closed: | 2011-06-07 14:07:25 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Channels/chan_sip/Registration |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | Hi I am trying to register a user id based and password account on asterisk of net4india but on 2345 port apart from by default SIP port 5060 . But i am unable to register on same because of the following reason Retransmitting #1 (no NAT) to 202.71.134.13:2345: REGISTER sip:202.71.134.13:2345 SIP/2.0 Via: SIP/2.0/UDP 220.227.2.234:5060;branch=z9hG4bK58dcb721;rport From: <sip:052231881@202.71.134.13>;tag=as1aa8835b To: <sip:052231881@202.71.134.13> Call-ID: 0e63f0cf6f16b67e37a465c64a7d24da@127.0.0.1 CSeq: 117 REGISTER User-Agent: Asterisk PBX Max-Forwards: 70 Expires: 120 Contact: <sip:052231881@220.227.2.234> Event: registration Content-Length: 0 The problem i can see instead of sending the request on another port 2345 its still taking the port 5060 in Via: SIP/2.0/UDP 220.227.2.234:5060;branch=z9hG4bK58dcb721;rport . ****** ADDITIONAL INFORMATION ****** I have spoken to the providers as well , they have the problem with this request URI Via: SIP/2.0/UDP 220.227.2.234:5060;branch=z9hG4bK58dcb721;rport We are using asterisk-1.4.21.2 register => 052241881:4827@202.71.134.13:2345/052231881 This is the register line i am using . | ||
| Comments: | By: Mark Michelson (mmichelson) 2008-08-08 17:22:40 It appears that Asterisk is sending the REGISTER on the port that you specified. If the provider is complaining because you are expecting to receive the response to the REGISTER on a specific port, then the provider is in violation of RFC 3261. The RFC is clear that responses must be sent to the same host and port from which the request was sent. I may be misunderstanding the problem (or it may be that Asterisk is not actually sending the request to port 2345 as it claims). Can you provide a packet capture of the problem so that we can verify that Asterisk is sending the request to the proper port and that the provider is sending the response to the same place from which the request was sent? If the provider claims that you have to receive SIP traffic on port 2345, then you can get around their non-compliance by setting bindport=2345 in sip.conf. The problem with this is that you will have to either set all of your phones to also send their SIP signaling to Asterisk on port 2345 or you will have to set up a proxy on port 5060 which relays the traffic to Asterisk on port 2345. If I have misunderstood the problem, please let me know. By: destiny6628 (destiny6628) 2008-08-11 04:51:05 Hi Yes you are absolutely correct and this defintely violation of RFC3261. bind port in the meanwhile time worked. Thanks for the prompt response . By: Mark Michelson (mmichelson) 2008-08-17 17:34:30 All right, then I'm going to close this since this is definitely an issue with your provider and not Asterisk. | ||