Hi James,
As I see, the INVITE has in URI sip:[email protected]
INVITE sip:[email protected] SIP/2.0
without any port indication, so the default 5060 is assumed. The proxy
cannot automatically discover what's the right port on the next hop if
not instructed by RURI or if not discovered via DNS SRV (not your case
as you use IPs).
So, the dialling party is the faulty one (198.162.0.1:9013 ) as it does
not provide a correct location of callee.
Regards,
Bogdan
James Mbuthia wrote:
> Hi guys,
>
> Hope you can help me out. I have a situation where my Opensips box is
> acting as a proxy/registration and location server. I have also
> changed my listening port from 5060 to 5059.
> The registration process works fine and my UAS gets a 200 response,
> its IP is 198.162.0.1:1167.
>
> However am getting a Request Timeout problem because once the proxy
> successfuly authenticates the UAC its forwading the INVITE request to
> my ip:5060. Since opensips is not configured on that port it gets a
> 408 Request Time out. Below is a snapshot of the headers from a sip
> trace.
>
>
> udp:198.162.0.1:5059 -> udp:198.162.0.1:7013
>
> SIP/2.0 407 Proxy Authentication Required
> Via: SIP/2.0/UDP 198.162.0.1:1167;rport=7013;branch=z9hG4bKynybt
> From:<sip:[email protected]>;tag=2325231
> To:<sip:[email protected]> ;tag=5594793ec2abca4d36972b7e2bfde24c.9363
> Call-ID:[email protected]
> CSeq: 1 INVITE
> Proxy-Authenticate: Digest realm="198.162.0.1",
> nonce="4cb834020000000547477b91a54ae9e5a553b9b6b633d830"
> Server: OpenSIPS (1.6.2-notls (i386/linux))
> Content-Length: 0
>
>
> udp:198.162.0.1:9013 -> udp:198.162.0.1:5059
>
> INVITE sip:[email protected] SIP/2.0
> Via: SIP/2.0/UDP 198.162.0.1:1167;rport=1645;branch=z9hG4bKynybt
> From:<sip:[email protected]>;tag=2325231
> To:<sip:[email protected]>
> Call-ID:[email protected]
> CSeq: 3 INVITE
> Contact: <sip:[email protected]>
> Proxy-Authorization: Digest username="jm21", realm="198.162.0.1",
> nonce="4cb834020000000547477b91a54ae9e5a553b9b6b633d830",
> uri="sip:[email protected]",
> response="53a86a6afd0d9fc9a118cb4a304f75d6", algorithm=MD5
> Content-type: application/sdp
> Max-Forwards: 69
> Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE
>
>
> udp:198.162.0.1:5059 -> udp:198.162.0.1:5060
>
> INVITE sip:[email protected] SIP/2.0
> Record-Route: <sip:198.162.0.1:5059;lr=on>
> Via: SIP/2.0/UDP 198.162.0.1:5059;branch=z9hG4bKa8e9.181ea9f5.0
> Via: SIP/2.0/UDP
> 198.162.0.1:1167;received=198.162.0.1;rport=9013;branch=z9hG4bKynybt
> From:<sip:[email protected]>;tag=2325231
> To:<sip:[email protected]>
> Call-ID:[email protected]
> CSeq: 3 INVITE
> Contact: <sip:[email protected]>
> Content-type: application/sdp
> Max-Forwards: 69
> Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE
>
>
> udp:198.162.0.1:5059 -> udp:198.162.0.1:9013
> SIP/2.0 408 Request Timeout
> Via: SIP/2.0/UDP 198.162.0.1:1167;rport=9013;branch=z9hG4bKynybt
> From:<sip:[email protected]>;tag=2325231
> To:<sip:[email protected]> ;tag=a2fc028f8d02e78ceae2b814452c9bc4-9363
> Call-ID:[email protected]
> CSeq: 3 INVITE
> Server: OpenSIPS (1.6.2-notls (i386/linux))
> Content-Length: 0
>
>
> My question is, why is the proxy routing the request to
> 198.162.0.1:5060 even after Opensips is not listening on that port? Is
> it possible to get it to route the request to the UAS i.e
> 198.162.0.1:1167?
>
> _______________________________________________
> Users mailing list
> [email protected]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
--
Bogdan-Andrei Iancu
OpenSIPS Bootcamp
15 - 19 November 2010, Edison, New Jersey, USA
www.voice-system.ro
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
