I have a Kamailio server forwarding REGISTERs to an Asterisk box, similar to the way Daniel shows here:
http://kb.asipto.com/asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb
Can I force Kamailio to append rport=5060 to the topmost Via header, prior to forwarding the REGISTER to Asterisk? I tried add_local_rport() but it only included 'rport' and not 5060.
Thanks, Marc
Basically, I'm trying to get Asterisk to send all future INVITEs to Kamailio on port 5060 and not the source port of the REGISTER. My REGISTER looks like this:
U 1.1.1.1:59738 -> 2.2.2.2:5060 REGISTER sip:2.2.2.2:5060 SIP/2.0. Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK404.05c2e5a7.0. Via: SIP/2.0/UDP 3.3.3.3:10654 ;rport=56417;branch=z9hG4bK-d8754z-a5ad572f022375cb-1---d8754z-. Max-Forwards: 16. To: sip:sip7878_spqa@2.2.2.2. From: sip:sip7878_spqa@2.2.2.2;tag=d8932554. Call-ID: OWU3NDM5N2MxOTVkOTM5YjE4MjZkMDFjYWIyN2JlNjI.. CSeq: 2 REGISTER. Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE. Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri. User-Agent: Z 3.3.21933 r21903. Allow-Events: presence, kpml. Content-Length: 0. Path: sip:3.3.3.3:56417;lr. Contact: sip:sip7878_spqa@1.1.1.1:5060. Expires: 3600. .
Subsequant INVITEs are sent to 1.1.1.1:59738 and not 1.1.1.1:5060. I need them to go to 1.1.1.1:5060.
On Fri, Mar 28, 2014 at 2:28 PM, Marc Soda msoda@coredial.com wrote:
Hello,
rport and Via headers are used for routing the SIP responses back to the device sending the request. They are not used at all for routing INVITE requests.
The tutorial you refer to is generating a new REGISTER from Kamailio to Asterisk, putting in it the Contact header with the address of kamailio. So Asterisk should send the INVITE to kamailio.
Cheers, Daniel
On 28/03/14 19:37, Marc Soda wrote:
I'm rewriting the Contact header in the REGISTER to be Kamailio on port 5060. For some reason Asterisk is sending INVITEs on the source port of the message and not 5060. I thought rport would correct that, but it sounds like rport is only intended to for subsequent messages in a given transaction...
On Fri, Mar 28, 2014 at 2:43 PM, Daniel-Constantin Mierla <miconda@gmail.com
wrote: