[Spce-user] Sipwise C5 softswitch commercial version
Daniel Grotti
dgrotti at sipwise.com
Tue Jan 10 04:52:31 EST 2017
Hi,
the problem is you "INBOUND PEERING RULES" for your peering server.
As you can read from the web interface in the "Inbound Peering Rules":
"ALL of the rules must match to choose the peering group for inbound calls."
So you MUST add at least 1 matching rule.
I suggest to add:
field: from-user
pattern: .*
Cheers,
--
Daniel Grotti
On 01/10/2017 10:36 AM, Cedric Le wrote:
> Hi Dainel,
>
> My scenario just register to Hoiio Sip account from SipC5 with DID
> 6566028047. I already registered successful, I can make outbound call
> but for the incoming call can not work this is the log as you required.
>
> Jan 10 10:30:40 spce proxy[2578]: NOTICE: <script>: New request on proxy
> - M=INVITE R=sip:203.205.28.49:40388;transport=udp
> F=sip:6568174383 at 122.152.145.120
> <mailto:sip%3A6568174383 at 122.152.145.120> T=sip:6566028047 at 203.205.28.49
> <mailto:sip%3A6566028047 at 203.205.28.49> IP=202.79.210.70:5060
> <http://202.79.210.70:5060> (127.0.0.1:5060 <http://127.0.0.1:5060>)
> ID=0cdb7f9c6ba3796c67fd40b306524015 at 122.152.145.115:5060-b2b_1 UA='Sippy
> B2BUA (RADIUS)'
> Jan 10 10:30:40 spce proxy[2578]: NOTICE: <script>: Call from PSTN -
> R=sip:203.205.28.49:40388;transport=udp
> ID=0cdb7f9c6ba3796c67fd40b306524015 at 122.152.145.115:5060-b2b_1 UA='Sippy
> B2BUA (RADIUS)'
> Jan 10 10:30:40 spce proxy[2578]: NOTICE: <script>: No matching inbound
> peer rule in any peering group, rejecting call -
> R=sip:203.205.28.49:40388;transport=udp
> ID=0cdb7f9c6ba3796c67fd40b306524015 at 122.152.145.115:5060-b2b_1 UA='Sippy
> B2BUA (RADIUS)'
> Jan 10 10:30:40 spce proxy[2579]: NOTICE: <script>: New request on proxy
> - M=INVITE R=sip:203.205.28.49:40388;transport=udp
> F=sip:6568174383 at 122.152.145.120
> <mailto:sip%3A6568174383 at 122.152.145.120> T=sip:6566028047 at 203.205.28.49
> <mailto:sip%3A6566028047 at 203.205.28.49> IP=202.79.210.70:5060
> <http://202.79.210.70:5060> (127.0.0.1:5060 <http://127.0.0.1:5060>)
> ID=0cdb7f9c6ba3796c67fd40b306524015 at 122.152.145.115:5060-b2b_1 UA='Sippy
> B2BUA (RADIUS)'
> Jan 10 10:30:40 spce proxy[2579]: NOTICE: <script>: Call from PSTN -
> R=sip:203.205.28.49:40388;transport=udp
> ID=0cdb7f9c6ba3796c67fd40b306524015 at 122.152.145.115:5060-b2b_1 UA='Sippy
> B2BUA (RADIUS)'
> Jan 10 10:30:40 spce proxy[2579]: NOTICE: <script>: No matching inbound
> peer rule in any peering group, rejecting call -
> R=sip:203.205.28.49:40388;transport=udp
> ID=0cdb7f9c6ba3796c67fd40b306524015 at 122.152.145.115:5060-b2b_1 UA='Sippy
> B2BUA (RADIUS)'
>
> Thanks
>
>
> On Tue, Jan 10, 2017 at 5:27 PM, Daniel Boghici <dboghici at sipwise.com
> <mailto:dboghici at sipwise.com>> wrote:
>
> that's the drwback with the Community Edition, if you have problems
> the support is on best effort basis, that means you need to describe
> the scenario you are testing and send an email to the list spce-user
> like I see you did for the install problem.
>
>
> Login as root with ssh into the server, and start the /tail -f
> /var/log/ngcp/kamailio-proxy.log/
>
> than make a test call and check the logs, collect that and put it in
> the email to spce-users, one of the engineers that monitor that list
> will send a reply.
>
>
> Cheers,
>
> Dan
>
>
> On 2017-01-10 10:19, Cedric Le wrote:
>> Hi Daniel,
>>
>> We are facing the issue can not forward incoming call to
>> Subscriber . Can you help to assign anyone help us to find the
>> root cause?
>>
>> Thanks
>>
>> On Mon, Jan 9, 2017 at 5:54 PM, Daniel Boghici
>> <dboghici at sipwise.com <mailto:dboghici at sipwise.com>> wrote:
>>
>> ok in order to avoid any problems with instalation try to
>> install the iso directly:
>>
>>
>> http://deb.sipwise.com/spce/images/sip_provider_CE_installcd.iso
>> <http://deb.sipwise.com/spce/images/sip_provider_CE_installcd.iso>
>>
>> Cheers,
>>
>> Dan
>>
>> On 2017-01-09 10:52, Cedric Le wrote:
>>> Hi Daniel,
>>>
>>> Thanks for your reply,
>>>
>>> Our plan will up to sip:provider PRO appliance but we need to
>>> install and understand anything from sip wise. We are
>>> reading youd handbook and We will contact you when we had
>>> completed.
>>>
>>> Thanks
>>>
>>> On Mon, Jan 9, 2017 at 5:47 PM, Daniel Boghici
>>> <<mailto:dboghici at sipwise.com>dboghici at sipwise.com
>>> <mailto:dboghici at sipwise.com>> wrote:
>>>
>>> Hi Cedric,
>>>
>>> I see you are testing our Community Edition, if you would
>>> like to have a quick demo of our Commercial Edition,
>>> please don't hesitate to contact me directly.
>>>
>>> I can set-up a screen sharing meeting and I can present
>>> you the features of the platform and answer many of your
>>> questions.
>>>
>>> Regards,
>>>
>>> --
>>> Dan Boghici
>>> Sales Engineer
>>> https://www.youtube.com/watch?v=n1xK8G1VEiQ
>>> <https://www.youtube.com/watch?v=n1xK8G1VEiQ>
>>>
>>>
>>>
>>>
>>> --
>>> Thanks and Regard,
>>> Cedric Le
>>
>> --
>> Dan Boghici
>> Sales Engineer
>> https://www.youtube.com/watch?v=n1xK8G1VEiQ
>> <https://www.youtube.com/watch?v=n1xK8G1VEiQ>
>>
>> --
>> Thanks and Regard,
>> Cedric Le
> --
> Dan Boghici
> Sales Engineer
> https://www.youtube.com/watch?v=n1xK8G1VEiQ
> <https://www.youtube.com/watch?v=n1xK8G1VEiQ>
>
>
>
>
> --
> Thanks and Regard,
> Cedric Le
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
>
More information about the Spce-user
mailing list