sip incoming issue

[morio]

h i every one,
hope some one get me some insite on this. its a oxe r 11.2.2 with sip trunk, it was working well untill we had to shift the location of the site. so now the new sip provider has implemented so many changes. some how i got the sip gate way up with authentication enabled and out going is fine. but for incoming i have a big problem.
when i configure the pilot numbet to AA, and when i call the pilot or any other DID range the call routes to the AA. if i remove the pilot DID from the DID translator and call any DID the OXE response with 404 not found.
in all incoming calls i get the pilot number in the INVITE as shown below
INVITE sip:+9661110108621@10.255.248.23;transport=UDP SIP/2.0

but the PAI for DID is
P-Called-Party-ID: <sip:+966112682300@fmc.stc.com.sa>
which ir right.
can i force the OXE to take in to account of the PAI and not the INVITE?

thanks in advance
PS if require trace let me know ill post it,,,,

[sadim]

I think the problem is not the oxe not looking at the PAI, but the fact that the provider is sending the fqdn (fmc.stc.com.sa) and not the ip addr.
If a dns server is not configured, the provider has to send the ip.
Ask the provider to send the ip and not the fqdn

[morio]

hi sadim.
thanks for your response. yes we are using the provider DNS.

[sadim]

so, on your external gw, the remote domain is configured with that fqdn, correct?
also, on the external gw, the dns server ip addr and type is configured

[morio]

h sadim
thanks for the response, i have attached my internal sip and external sip gateway config. can you please let me know if i have done anything wrong in there with regarding the DNS.

thanks

[sadim]

Hi, can you try with SIP Remote Domain = fmc.stc.com.sa (do not forget to restart the sipmotor)

[morio]

hi sadim,
yes i have tried that as well, but same behaviuor.

thanks

[sadim]

In that case, I think it's time to show a motortrace and detail as much as possible the test scenario (calling number, called number, ...)

[morio]

i have attached the traces. please check incoming call D69 from MOTVIEW.

[morio]

FROM 0509345978
Ton 0112682300

INVITE sip:+9661110108621@10.255.248.23;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 10.141.40.20:5060;branch=z9hG4bK3ogd2c2020g7ohoo48f0.1
Call-ID: utjprmjwpr8yuu3u6t888j080ur5jwb5@10.208.12.17
From: <sip:0509345978@10.141.40.20;user=phone>;tag=p5p53wu8
To: <sip:0112682300;phone-context=fmc.stc.com.sa@10.255.248.23;user=phone>
CSeq: 1 INVITE
Accept: application/sdp,application/3gpp-ims+xml
Allow: INVITE,ACK,OPTIONS,CANCEL,BYE,UPDATE,INFO,REFER,NOTIFY,MESSAGE,PRACK
Contact: <sip:10.141.40.20:5060;Dpt=eada-200;transport=udp>;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
Max-Forwards: 60
Supported: timer,100rel,gruu
User-Agent: SM-A715F-VK1 Samsung IMS 6.0
Session-Expires: 1800
Min-SE: 600
P-Asserted-Identity: <sip:+966509345978@fmc.stc.com.sa>
P-Asserted-Identity: <tel:+966509345978>
P-Called-Party-ID: <sip:+966112682300@fmc.stc.com.sa>
P-Early-Media: supported
P-Preferred-Service: urn:urn-7:3gpp-service.ims.icsi.mmtel
Accept-Contact: *;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
Content-Length: 781
Content-Type: application/sdp