[Spce-user] Sipwise C5 softswitch commercial version

Wed Jan 11 04:31:32 EST 2017

Hi all,

Do you have any update form this?

Thanks

On Wed, Jan 11, 2017 at 9:59 AM, Cedric Le <cedric at hoiio.com> wrote:

> HI All,
>
> 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. I was follow the guide from handbook to
> setup but still not working.
>
> Step1: I created one subscriber with number 65 6 6028047
>
> [image: Inline image 5]
>
> Step 2:
> Created one RR outbound callee and applied to domain.
>
> [image: Inline image 1]
>
> [image: Inline image 2]
>
> Step 3:
> Created one RR inbound callee and applied to peer
>
> [image: Inline image 3]
>
> [image: Inline image 4]
>
> But still showing logs message "No matching inbound peer rule in any
> peering group, rejecting call"
>
> Jan 11 02:44:02 spce proxy[2566]: NOTICE: <script>: New request on proxy -
> M=INVITE R=sip:203.205.28.49:40388;transport=udp F=
> sip:6568174383 at 122.152.145.107 T=sip:6566028047 at 203.205.28.49 IP=
> 202.79.210.70:5060 (127.0.0.1:5060) ID=23a9cb387e4ced215589f54e27a39f
> 91 at 122.152.145.115:5060-b2b_1 UA='Sippy B2BUA (RADIUS)'
> Jan 11 02:44:02 spce proxy[2566]: NOTICE: <script>: Call from PSTN - R=sip:
> 203.205.28.49:40388;transport=udp ID=23a9cb387e4ced215589f54e27a39f
> 91 at 122.152.145.115:5060-b2b_1 UA='Sippy B2BUA (RADIUS)'
> Jan 11 02:44:02 spce proxy[2566]: NOTICE: <script>: No matching inbound
> peer rule in any peering group, rejecting call - R=sip:203.205.28.49:40388
> ;transport=udp ID=23a9cb387e4ced215589f54e27a39f91 at 122.152.145.115:5060-b2b_1
> UA='Sippy B2BUA (RADIUS)'
>
>
> Please correct me if i was wrong.
> Looking to hear from you soon.
>
> Thanks
> Regards
>
>
>
> On Tue, Jan 10, 2017 at 5:49 PM, Daniel Boghici <dboghici at sipwise.com>
> wrote:
>
>> Dear Cedric,
>>
>> 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=0cdb7f9c6ba3796c67fd40b3065
>> 24015 at 122.152.145.115:5060-b2b_1 UA='Sippy B2BUA (RADIUS)'
>>
>>
>>
>> Have you configured an inbound rewrite rule , that you applied under
>> number manipulation for your peering server? like the manual says here?
>>
>>
>> https://www.sipwise.org/doc/mr5.0.1/spce/ar01s05.html#dialplans
>> 5.6.7. Creating Dialplans for Peering Servers
>>
>> For each peering server, you can use one of the Rewrite Rule Sets that
>> was created previously as explained in Section 5.6, “Configuring Rewrite
>> Rule Sets”
>> <https://www.sipwise.org/doc/mr5.0.1/spce/ar01s05.html#dialplans> (keep
>> in mind that special variables ${caller_ac} and ${caller_cc} can not be
>> used when the call comes from a peer). To do so, click on the name of the
>> peering server, look for the preference called *Rewrite Rule Sets*.
>>
>> If your peering servers don’t send numbers in E.164 format *<cc><ac><sn>*,
>> you need to create *Inbound Rewrite Rules* for each peering server to
>> normalize the numbers for caller and callee to this format, e.g. by
>> stripping leading + or put them from national into E.164 format.
>>
>> Likewise, if your peering servers don’t accept this format, you need to
>> create *Outbound Rewrite Rules* for each of them, for example to append
>> a *+* to the numbers.
>>
>> On 2017-01-10 10:36, 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%3A6568174383 at 122.152.145.120>sip:6568174383 at 122.152.145.120 T=
>> sip:6566028047 at 203.205.28.49 IP=202.79.210.70:5060 (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=0cdb7f9c6ba3796c67fd40b3065
>> 24015 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=0cdb7f9c6ba3796c67fd40b3065
>> 24015 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%3A6568174383 at 122.152.145.120>sip:6568174383 at 122.152.145.120 T=
>> sip:6566028047 at 203.205.28.49 IP=202.79.210.70:5060 (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=0cdb7f9c6ba3796c67fd40b3065
>> 24015 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=0cdb7f9c6ba3796c67fd40b3065
>> 24015 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>
>> 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>
>>> 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
>>>>
>>>> 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 < <dboghici at sipwise.com>
>>>> 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
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Thanks and Regard,
>>>> Cedric Le
>>>>
>>>>
>>>> --
>>>> Dan Boghici
>>>> Sales Engineerhttps://www.youtube.com/watch?v=n1xK8G1VEiQ
>>>>
>>>> --
>>> Thanks and Regard,
>>> Cedric Le
>>>
>>> --
>>> Dan Boghici
>>> Sales Engineerhttps://www.youtube.com/watch?v=n1xK8G1VEiQ
>>>
>>> --
>> Thanks and Regard,
>> Cedric Le
>>
>> --
>> Dan Boghici
>> Sales Engineerhttps://www.youtube.com/watch?v=n1xK8G1VEiQ
>>
>>
>
>
> --
> Thanks and Regard,
> Cedric Le
>

-- 
Thanks and Regard,
Cedric Le
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20170111/c5944725/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 49993 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20170111/c5944725/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 5179 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20170111/c5944725/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 26962 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20170111/c5944725/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 59097 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20170111/c5944725/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 48286 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20170111/c5944725/attachment-0009.png>