[Spce-user] Incoming calls forbidden - prefix or domain problem?

Jiri Ptacnik ptakjura at gmail.com
Tue Oct 13 08:11:10 EDT 2020


Thanks Matthias,

good hint for a better log, that point me to the finish line. We have
not setup inbound peering rule: firstly we had wrong setup of inbound
rules, and after we deleted all, there should be at least one. I put
here dot rule, so everything is coming to.

George

po 12. 10. 2020 v 12:22 odesílatel Matthias Hohl
<matthias.hohl at telematica.at> napsal:
>
> Easier it would be if you do a grep on the call-id on var/log/ngcp/kamailio-proxy.log
> Then you see how the call will be procressed by the spce and you can see there any problem too.
>
> Am 10.10.2020 um 09:23 schrieb EMMANUEL AFANG <afang.emmanuel at gmail.com>:
>
> 
> Hi
> If the Destination is not called with country code, then I think a zero prefixed.
>
> Also, you need Inbound Peering configured for with a correct match for the incoming calls.
>
>
> On Thu, 8 Oct 2020, 8:44 am Jiri Ptacnik, <ptakjura at gmail.com> wrote:
>>
>> Hi all,
>>
>> SPCE 8.5.1
>>
>> outgoing calls works fine.
>>
>> But incoming not. In subscriber we have
>>
>> SIP URI like this 111222333 at phone.dest.st
>>
>> In ngrep-sip on destination server we can see this:
>>
>> U 2020/10/08 09:30:05.255854 13.16.16.17:5060 -> 13.16.16.14:5060 #16
>> SIP/2.0 403 Forbidden'
>> Via: SIP/2.0/UDP
>> 13.16.16.14;rport=5060;branch=z9hG4bKf5a2.ab97ca7b89077c46e9b475952b537435.0'
>> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKdrq93atR;rport=5080'
>> From: <sip:421888888888 at sip.source.st>;tag=05C56D6A-5F7EBFEC000C8E16-9F8E7700'
>> To: <sip:421111222333 at sip.source.st>;tag=95c37a12bff1a2c36d72bf8333176544.78550000'
>> CSeq: 10 INVITE'
>> Call-ID: 05e801494863fe8e599e45bf3ef491a7 at 12.7.12.63:5060_b2b-1'
>> Server: Sipwise NGCP Proxy 8.X'
>> Content-Length: 0'
>> '
>>
>> There are two mysterious things:
>>
>> In TO section, there is country code in this example 421, but defined
>> SIP URI in subscriber is without country code.
>>
>> Is it problem?
>>
>> Or weird is, in TO sections is after @ sign source domain, not
>> destination domain?
>>
>> What should be wrong?
>>
>> Thanks, George
>>
>> --
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> https://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com




More information about the Spce-user mailing list