Re: Visited Network Identity

443 views
Skip to first unread message

Mamadou

unread,
Sep 3, 2012, 3:01:37 AM9/3/12
to discuss-doubango
This looks like a bug in OpenIMSCore (or regression as it was working)
because its up to the P-CSCF to add this header before forwarding the
request to the I-CSCF.
For more info: rfc 3455 section 4.3.2.1

On Sep 2, 1:53 pm, siavashs <siavash.s...@gmail.com> wrote:
> I'm testing idoubs 2.200.702 with latest OpenIMSCore svn.
> The server response is: SIP/2.0 400 Bad Request - P-Visited-Network-ID
> header missing
> I checked the headers in the packet sent from client(idoubs) and did not
> find the mentioned header.
> Does idoubs(doubango) support this feature?
> If yes: How can I set the value/enable it?

Carsten Bock

unread,
Sep 3, 2012, 3:16:43 AM9/3/12
to doub...@googlegroups.com
Hi,

It looks like your sending to the I-CSCF directly, instead of using
the P-CSCF first.
I don't know iDoubs, but i know IMSDroid and Boghe, so i assume the
settings are similar.

Probably an issue with your "Network"-settings: There could be two issues here:
1) Did you configure the proper P-CSCF (IP/hostname and Port)? If no,
then this is the issue...
2) Did you enable DNS-NAPTR-SRV? If yes (and you want to stick with
this setting), please check your DNS-Records. The DNS-NAPTR records
should look like this (i use ims.ng-voice.com for my IMS-Cloud, so the
P-CSCF can be located by querying DNS-NAPTR-SRV on ims.ng-voice.com):

carsten@carsten-ThinkCentre-M57p ~ $ host -v -t NAPTR ims.ng-voice.com
Trying "ims.ng-voice.com"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30656
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;ims.ng-voice.com. IN NAPTR

;; ANSWER SECTION:
ims.ng-voice.com. 300 IN NAPTR 40 50 "s" "SIP+D2T" ""
_sip._tcp.pcscf.ims.ng-voice.com.
ims.ng-voice.com. 300 IN NAPTR 10 50 "s" "SIPS+D2T" ""
_sips._tcp.pcscf.ims.ng-voice.com.
ims.ng-voice.com. 300 IN NAPTR 20 50 "s" "SIP+D2U" ""
_sip._udp.pcscf.ims.ng-voice.com.

Received 219 bytes from 192.168.178.254#53 in 39 ms
(in my case: indicating that your preferred transport is SIP-TLS
(Priority 10), next UDP (20) last TCP (30)).

The OpenIMS-Core hasn't been touched for so long, so i don't think
they introduced a bug... ;-)

So long,
Carsten

2012/9/3 Mamadou <diopm...@doubango.org>:
> --
>
>



--
Carsten Bock
CEO (Geschäftsführer)

ng-voice GmbH
Schomburgstr. 80
D-22767 Hamburg / Germany

http://www.ng-voice.com
mailto:car...@ng-voice.com

Office +49 40 34927219
Fax +49 40 34927220

Sitz der Gesellschaft: Hamburg
Registergericht: Amtsgericht Hamburg, HRB 120189
Geschäftsführer: Carsten Bock
Ust-ID: DE279344284

Hier finden Sie unsere handelsrechtlichen Pflichtangaben:
http://www.ng-voice.com/imprint/

Mamadou

unread,
Sep 3, 2012, 3:24:53 AM9/3/12
to doub...@googlegroups.com, Carsten Bock
This make sense. Perhaps he is using port 5060 instead of 4060.

Siavash Safi

unread,
Sep 3, 2012, 3:28:54 AM9/3/12
to doub...@googlegroups.com, Carsten Bock
P-CSCF is listening on port 4060
I-CSCF is listening on port 5060

The default port in idoubs configuration was port 5060, is it wrong?
Also I don't have any DNS SRV records, I set the IMS servers IP address in client configuration.

-- 
Regards,
Siavash Safi
Sent with Sparrow

--

Mamadou

unread,
Sep 3, 2012, 3:38:00 AM9/3/12
to doub...@googlegroups.com, Siavash Safi, Carsten Bock
Yes. Have to be 4060.
--
 
 

Siavash Safi

unread,
Sep 3, 2012, 3:48:22 AM9/3/12
to Mamadou, doub...@googlegroups.com, Carsten Bock
Now it's working.
Thanks for your support.

-- 
Regards,
Siavash Safi
Sent with Sparrow

Raamkanna Saranathan

unread,
Nov 19, 2013, 2:58:57 PM11/19/13
to doub...@googlegroups.com, Mamadou, Carsten Bock
Thanks for this thread guys. Boghe is the only client i was able to get to work with OpenIMSCore. With the rest of the clients such as linphone, x-lite etc, i am not able to configure them correctly to point to the correct PCSCF IP/Port.

Raam
Reply all
Reply to author
Forward
0 new messages