[pjsip] Service-route overriding proxy

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Benny,

Hmm. Not sure. My montiorings:

1) No specification of service-route in config
* Register OK, server returns service route pointing to scscf:6060
* Invite is blocked by the registrar with error "Bad request - not following 
indicated service route". The request has been sent to pcscf:5060

2) Specification of service-route in config
* Register as above
* Invite is now sent to scscf:6060 (as specified in service route). This 
ends up in no response.

Shouldn't the Ua send the Invite to pcscf:5060, providing the received 
service route somewhere in the INVITE header in order to let the pcscf know, 
where to route the request?

As far as I can remember there was no ;lr in the service route. What would 
that change (besides the fact that I can't control the IMS platform)?

Regards


----- Original Message ----- 
From: "Benny Prijono" <bennylp@xxxxxxxxx>
To: "pjsip embedded/DSP SIP discussion" <pjsip at lists.pjsip.org>
Sent: Tuesday, October 30, 2007 4:23 PM
Subject: Re: [pjsip] Service-route overriding proxy


> Roland Klabunde wrote:
>> The current Service-Route handling seems to be wrong.
>> We believe that Service-Route should be copied to the Route element of 
>> any
>> SIP request following a REGISTER, but shouldn't be used as target for
>> e.g. INVITES.
>
> Could this be because of the lack of ";lr" in the S-R URI?
>
>  -benny
>
>
>
> _______________________________________________
> Visit our blog: http://blog.pjsip.org
>
> pjsip mailing list
> pjsip at lists.pjsip.org
> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
> 




[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux