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/