[Spce-user] Incoming call failed with 404 (callee is not local)
Yazar Lwin
yarzarlwin at gmail.com
Thu Sep 12 00:28:13 EDT 2019
Hi All,
One update info:
I didn't configure E.164 for user. We just simply use number as SIP user
name. Peering is FPBX server and it just simply route user prefix to our
NGCP. Inbound peer rule is passed. Here is the log.
Sep 10 15:58:23 office-voice-gw proxy[2978]: NOTICE: <script>: Call from
PSTN - R=sip:502491 at 172.18.79.20 ID=
1dbc5525128e3293633935166acbb3b3 at 172.18.79.15:5060
UA='FPBX-14.0.13.4(16.5.0)'
Sep 10 15:58:23 office-voice-gw proxy[2978]: NOTICE: <script>: Inbound
peering group '1' matched, looking up peer host - R=sip:502491 at 172.18.79.20
ID=1dbc5525128e3293633935166acbb3b3 at 172.18.79.15:5060
UA='FPBX-14.0.13.4(16.5.0)'
Sep 10 15:58:23 office-voice-gw proxy[2978]: NOTICE: <script>: Selected
peering host id '1' as inbound peer - R=sip:502491 at 172.18.79.20 ID=
1dbc5525128e3293633935166acbb3b3 at 172.18.79.15:5060
UA='FPBX-14.0.13.4(16.5.0)'
Sep 10 15:58:23 office-voice-gw proxy[2978]: NOTICE: <script>: Dialog
managed, lua_dlg_callid:[1dbc5525128e3293633935166acbb3b3 at 172.18.79.15:5060]
- R=sip:502491 at 172.18.79.20 ID=
1dbc5525128e3293633935166acbb3b3 at 172.18.79.15:5060
UA='FPBX-14.0.13.4(16.5.0)'
Sep 10 15:58:23 office-voice-gw proxy[2978]: NOTICE: <script>:
User-Provided CLI '308000' taken from From-User - R=sip:502491 at 172.18.79.20
ID=1dbc5525128e3293633935166acbb3b3 at 172.18.79.15:5060
UA='FPBX-14.0.13.4(16.5.0)'
Sep 10 15:58:23 office-voice-gw proxy[2978]: NOTICE: <script>:
Network-Provided CLI '308000' taken from From-User - R=
sip:502491 at 172.18.79.20 ID=
1dbc5525128e3293633935166acbb3b3 at 172.18.79.15:5060
UA='FPBX-14.0.13.4(16.5.0)'
Sep 10 15:58:23 office-voice-gw proxy[2978]: NOTICE: <script>: Setting '
308000 at 172.18.79.15' as initiating user-provided CLI - R=
sip:502491 at 172.18.79.20 ID=
1dbc5525128e3293633935166acbb3b3 at 172.18.79.15:5060
UA='FPBX-14.0.13.4(16.5.0)'
Sep 10 15:58:23 office-voice-gw proxy[2978]: NOTICE: <script>: Setting '
308000 at 172.18.79.15' as initiating network-provided CLI - R=
sip:502491 at 172.18.79.20 ID=
1dbc5525128e3293633935166acbb3b3 at 172.18.79.15:5060
UA='FPBX-14.0.13.4(16.5.0)'
Sep 10 15:58:23 office-voice-gw proxy[2978]: NOTICE: <script>: Callee is
not local - R=sip:502491 at 172.18.79.20 ID=
1dbc5525128e3293633935166acbb3b3 at 172.18.79.15:5060
UA='FPBX-14.0.13.4(16.5.0)'
Sep 10 15:58:23 office-voice-gw proxy[2978]: NOTICE: <script>: Call to
unknown user - R=sip:502491 at 172.18.79.20 ID=
1dbc5525128e3293633935166acbb3b3 at 172.18.79.15:5060
UA='FPBX-14.0.13.4(16.5.0)'
Sep 10 15:58:23 office-voice-gw proxy[2978]: NOTICE: <script>: Setting acc
source-leg for uuid '0':
'0|308000|172.18.79.105|308000|||0|||0|call|127.0.0.1|1568107703.880597||||||||||||308000||||'
- R=sip:502491 at 172.18.79.20 ID=
1dbc5525128e3293633935166acbb3b3 at 172.18.79.15:5060
UA='FPBX-14.0.13.4(16.5.0)'
Sep 10 15:58:23 office-voice-gw proxy[2978]: NOTICE: <script>: Setting acc
destination-leg for uuid '0':
'0|||0|502491|0|502491|172.18.79.20|502491|172.18.79.20|0||||||||||||502491|||'
- R=sip:502491 at 172.18.79.20 ID=
1dbc5525128e3293633935166acbb3b3 at 172.18.79.15:5060
UA='FPBX-14.0.13.4(16.5.0)'
Sep 10 15:58:23 office-voice-gw proxy[2978]: NOTICE: <script>: Sending
reply S=404 Not Found fs='127.0.0.1:5062' du='127.0.0.1:5060' - R=
sip:502491 at 172.18.79.20 ID=
1dbc5525128e3293633935166acbb3b3 at 172.18.79.15:5060
UA='FPBX-14.0.13.4(16.5.0)'
On Thu, Sep 12, 2019 at 10:29 AM Yazar Lwin <yarzarlwin at gmail.com> wrote:
> Hi All,
>
> I've looked for the resolution in older posts but didn't find yet.
> We set up NGCP (CE version mr 7.2.1) with 2 IP.
> One is used for domain IP and another is used for peering. User
> registered to domain IP. User can't reach to peering IP as it's for
> external communications with peer server.
> When incoming call hit to NGCP with peering IP, NGCP can't treat the
> subscriber as local user since registered domain IP is different with
> peering IP.
> Please help how to resolve this in NGCP. I believe it's been solved
> somewhere in forum but I can't find it.
>
> Best regards,
> Yazar
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20190912/5f2650fb/attachment-0002.html>
More information about the Spce-user
mailing list