hi guys,
i have a issue with the public sip trunk. im using a SBC (cisco) for the natting. the public operator insists in using domain name (itc.sa).
all out going calls are fine no issue, but i cant receive any. when i receive a call the oxe is refusing with 404 message.
i hope some one can help me on this. i have posted the traced of ok out going and not ok incoming.
regards
Morio
OXE sip trunk reply 404 rejected/not found here
OXE sip trunk reply 404 rejected/not found here
You do not have the required permissions to view the files attached to this post.
Re: OXE sip trunk reply 404 rejected/not found here
the oxe did not find a sipext gw for this call.
maybe activate "Via Header_ Inbound Calls Routing" under System -> other System parameter -> SIP parameter
maybe activate "Via Header_ Inbound Calls Routing" under System -> other System parameter -> SIP parameter
Re: OXE sip trunk reply 404 rejected/not found here
HI Alexik, thanks for the reply, i will try your suggestion on the site by tomorrow, will update you.
thanks again..
thanks again..
Re: OXE sip trunk reply 404 rejected/not found here
Hi Alexik,
done the change and even rebooted the system but still the same. I requested the provider to set the invite as same as domain. any other ideas guys. if you require more details just let me know,,
regards
morio
done the change and even rebooted the system but still the same. I requested the provider to set the invite as same as domain. any other ideas guys. if you require more details just let me know,,
regards
morio
Re: OXE sip trunk reply 404 rejected/not found here
On the Invite i can see:
INVITE sip:+966115051030@sbc-trunking.itc.sa SIP/2.0
So it seems that the SBC has a rule that changes the domain from itc.sa to sbc-trunking.itc.sa
You can check and correct this on the sbc configuration and this should be the right to solve the issue.
As a work around, you can create an additional SIP Ext Gw for that domain
BRegards
Sadim
INVITE sip:+966115051030@sbc-trunking.itc.sa SIP/2.0
So it seems that the SBC has a rule that changes the domain from itc.sa to sbc-trunking.itc.sa
You can check and correct this on the sbc configuration and this should be the right to solve the issue.
As a work around, you can create an additional SIP Ext Gw for that domain
BRegards
Sadim
Re: OXE sip trunk reply 404 rejected/not found here
hi sadim,
@sbc-trunking.itc.sa was sent from the provider, i informed them abut this and they are now sending itc.sa for the domain in the INVITE,,, i will attach the new traces,,
thanks
@sbc-trunking.itc.sa was sent from the provider, i informed them abut this and they are now sending itc.sa for the domain in the INVITE,,, i will attach the new traces,,
thanks
Re: OXE sip trunk reply 404 rejected/not found here
these are the new traced where the provider sends @itc.sa in the INVITE
You do not have the required permissions to view the files attached to this post.
Re: OXE sip trunk reply 404 rejected/not found here
The same error in both case
CProxyCall::forwardTheRequestToEachTarget] ---*--- LICENSES ---*--- External caller
Tue Dec 1 14:21:02 2020 111d [CProxyCall::forwardTheRequestToEachTarget] ---*--- LICENSES ---*--- External callee according to To header
(con
DDI not working?! trunk-context?! interdomain , intra domain signaling
CProxyCall::forwardTheRequestToEachTarget] ---*--- LICENSES ---*--- External caller
Tue Dec 1 14:21:02 2020 111d [CProxyCall::forwardTheRequestToEachTarget] ---*--- LICENSES ---*--- External callee according to To header
(con
DDI not working?! trunk-context?! interdomain , intra domain signaling
Re: OXE sip trunk reply 404 rejected/not found here
hi haroun,
thanks for the reply but i dont understand it, can you please explain ..
thanks for the reply but i dont understand it, can you please explain ..
Re: OXE sip trunk reply 404 rejected/not found here
Hi,
Change the parameter mgr-system-other syst params-SIP parameters-Loose Route with RegID to False, and try again
Note: not sure if a sipmotor restart is needed.
Change the parameter mgr-system-other syst params-SIP parameters-Loose Route with RegID to False, and try again
Note: not sure if a sipmotor restart is needed.

