[Spce-user] Sipwise C5 softswitch commercial version

Cedric Le cedric at hoiio.com
Wed Jan 11 23:55:25 EST 2017


Hi Daniel,

We still facing with can not receive incoming call. Now can match with
inbound route but seem like not query success the callee number, it alway
show Callee is not local and call to unknow user.

Jan 12 05:47:00 spce proxy[2527]: NOTICE: <script>: New request on proxy -
M=ACK 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=26282ae75bd945607f001b397390515b at 122.152.145.121:5060-b2b_1 UA='<null>'
Jan 12 05:47:00 spce proxy[2540]: 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=26282ae75bd945607f001b397390515b at 122.152.145.121:5060-b2b_1 UA='Sippy
B2BUA (RADIUS)'
Jan 12 05:47:00 spce proxy[2540]: NOTICE: <script>: Call from PSTN -
R=sip:203.205.28.49:40388;transport=udp
ID=26282ae75bd945607f001b397390515b at 122.152.145.121:5060-b2b_1 UA='Sippy
B2BUA (RADIUS)'
Jan 12 05:47:00 spce proxy[2540]: NOTICE: <script>: Inbound peering group
'1' matched, looking up peer host - R=sip:203.205.28.49:40388;transport=udp
ID=26282ae75bd945607f001b397390515b at 122.152.145.121:5060-b2b_1 UA='Sippy
B2BUA (RADIUS)'
Jan 12 05:47:00 spce proxy[2540]: NOTICE: <script>: Selected peering host
id '2' as inbound peer - R=sip:203.205.28.49:40388;transport=udp
ID=26282ae75bd945607f001b397390515b at 122.152.145.121:5060-b2b_1 UA='Sippy
B2BUA (RADIUS)'
Jan 12 05:47:00 spce proxy[2540]: NOTICE: <script>: Dialog managed,
lua_dlg_callid:[26282ae75bd945607f001b397390515b at 122.152.145.121:5060-b2b_1]
- R=sip:203.205.28.49:40388;transport=udp
ID=26282ae75bd945607f001b397390515b at 122.152.145.121:5060-b2b_1 UA='Sippy
B2BUA (RADIUS)'
Jan 12 05:47:00 spce proxy[2540]: NOTICE: <script>: IMS marker,
s:ims_role='<null>', s:caller_uuid='0', s:callee_uuid='<null>',
s:acc_caller_user='6568174383', s:acc_caller_domain='202.79.210.70'  -
R=sip:203.205.28.49:40388;transport=udp
ID=26282ae75bd945607f001b397390515b at 122.152.145.121:5060-b2b_1 UA='Sippy
B2BUA (RADIUS)'
Jan 12 05:47:00 spce proxy[2540]: NOTICE: <script>: User-Provided CLI
'6568174383' taken from From-User - R=sip:203.205.28.49:40388;transport=udp
ID=26282ae75bd945607f001b397390515b at 122.152.145.121:5060-b2b_1 UA='Sippy
B2BUA (RADIUS)'
Jan 12 05:47:00 spce proxy[2540]: NOTICE: <script>: Network-Provided CLI
'6568174383' taken from From-User -
R=sip:203.205.28.49:40388;transport=udp
*ID=26282ae75bd945607f001b397390515b at 122.152.145.121:5060-b2b_1
UA='Sippy B2BUA (RADIUS)'*
*Jan 12 05:47:00 spce proxy[2540]: NOTICE: <script>: Rewriting
user-provided CLI '6568174383' to '6566028047' -
R=sip:203.205.28.49:40388;transport=udp
ID=26282ae75bd945607f001b397390515b at 122.152.145.121:5060-b2b_1 UA='Sippy
B2BUA (RADIUS)'*
*Jan 12 05:47:00 spce proxy[2540]: NOTICE: <script>: Rewriting
network-provided CLI '6568174383' to '6566028047' -
R=sip:203.205.28.49:40388;transport=udp
ID=26282ae75bd945607f001b397390515b at 122.152.145.121:5060-b2b_1 UA='Sippy
B2BUA (RADIUS)'*
*Jan 12 05:47:00 spce proxy[2540]: NOTICE: <script>: Setting
'6566028047 at 122.152.145.107 <6566028047 at 122.152.145.107>' as initiating
user-provided CLI - R=sip:203.205.28.49:40388;transport=udp
ID=26282ae75bd945607f001b397390515b at 122.152.145.121:5060-b2b_1 UA='Sippy
B2BUA (RADIUS)'*
*Jan 12 05:47:00 spce proxy[2540]: NOTICE: <script>: Setting
'6566028047 at 122.152.145.107 <6566028047 at 122.152.145.107>' as initiating
network-provided CLI - R=sip:203.205.28.49:40388;transport=udp
ID=26282ae75bd945607f001b397390515b at 122.152.145.121:5060-b2b_1 UA='Sippy
B2BUA (RADIUS)'*
*Jan 12 05:47:00 spce proxy[2540]: NOTICE: <script>: Callee is not local -
R=sip:203.205.28.49:40388;transport=udp
ID=26282ae75bd945607f001b397390515b at 122.152.145.121:5060-b2b_1 UA='Sippy
B2BUA (RADIUS)'*
*Jan 12 05:47:00 spce proxy[2540]: NOTICE: <script>: Call to unknown user -
R=sip:203.205.28.49:40388;transport=udp
ID=26282ae75bd945607f001b397390515b at 122.152.145.121:5060-b2b_1 UA='Sippy
B2BUA (RADIUS)'*
*Jan 12 05:47:00 spce proxy[2540]: NOTICE: <script>: Setting acc source-leg
for uuid '0':
'0|6568174383|202.79.210.70|6566028047|||0|||0|call|202.79.210.70|1484196420.700569||||||||||||'
- R=sip:203.205.28.49:40388;transport=udp
ID=26282ae75bd945607f001b397390515b at 122.152.145.121:5060-b2b_1 UA='Sippy
B2BUA (RADIUS)'*
Jan 12 05:47:00 spce proxy[2540]: NOTICE: <script>: Setting acc
destination-leg for uuid '0':
'0|||0|<null>|0|<null>|203.205.28.49||203.205.28.49|0||||||||||||' -
R=sip:203.205.28.49:40388;transport=udp
ID=26282ae75bd945607f001b397390515b at 122.152.145.121:5060-b2b_1 UA='Sippy
B2BUA (RADIUS)'
Jan 12 05:47:00 spce proxy[2540]: NOTICE: <script>: [dialog:failed]
decreased redis counters
lua_dlg_callid:[26282ae75bd945607f001b397390515b at 122.152.145.121:5060-b2b_1]
- R=sip:you at kamailio.org ID=123 UA='<null>'
Jan 12 05:47:00 spce proxy[2532]: NOTICE: <script>: New request on proxy -
M=ACK 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=26282ae75bd945607f001b397390515b at 122.152.145.121:5060-b2b_1 UA='<null>'
Jan 12 05:47:01 spce proxy[2531]: NOTICE: <script>: New request on proxy -
M=REGISTER R=sip:192.168.1.40;transport=UDP
F=sip:sip123456 at 192.168.1.40;transport=UDP
T=sip:sip123456 at 192.168.1.40;transport=UDP IP=192.168.1.17:65070 (
127.0.0.1:5060) ID=ehAVfQbmACmEpBfk-ks6XA.. UA='Zoiper rv2.8.26'
Jan 12 05:47:01 spce proxy[2531]: NOTICE: <script>: Contacts successfully
updated, expires in 60s - R=sip:192.168.1.40;transport=UDP
ID=ehAVfQbmACmEpBfk-ks6XA.. UA='Zoiper rv2.8.26'



[image: Inline image 1]

[image: Inline image 2]

[image: Inline image 3]


Please correct me if i was wrong
Looking hear from you soon.



On Wed, Jan 11, 2017 at 5:41 PM, Daniel Grotti <dgrotti at sipwise.com> wrote:

> Dear Cedric,
> I already replied on that.
> This is not a Rewrite Rules problem, but a PEERING RULE problems.
> Read my reply please: https://lists.sipwise.com/pipe
> rmail/spce-user/2017-January/011085.html
>
>
>
> --
> Daniel Grotti
>
>
> On 01/11/2017 10:31 AM, Cedric Le wrote:
>
>> 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
>> <mailto: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
>>
>>     Inline image 5
>>
>>     Step 2:
>>     Created one RR outbound callee and applied to domain.
>>
>>     Inline image 1
>>
>>     Inline image 2
>>
>>     Step 3:
>>     Created one RR inbound callee and applied to peer
>>
>>     Inline image 3
>>
>>     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
>>     <http://203.205.28.49:40388>;transport=udp
>>     F=sip:6568174383 at 122.152.145.107
>>     <mailto:sip%3A6568174383 at 122.152.145.107>
>>     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=23a9cb387e4ced215589f54e27a39f91 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 <http://203.205.28.49:40388>;transport=udp
>>     ID=23a9cb387e4ced215589f54e27a39f91 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 <http://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 <mailto: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
>>         <http://203.205.28.49:40388>;transport=udp
>>         ID=0cdb7f9c6ba3796c67fd40b306524015 at 122.152.145.115:5060-b2b_1
>>         <mailto:ID=0cdb7f9c6ba3796c67fd40b306524015 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
>>         <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
>>>         <http://203.205.28.49:40388>;transport=udp
>>>         F=<mailto:sip%3A6568174383 at 122.152.145.120>sip:6568174383@
>>> 122.152.145.120
>>>         <mailto:sip:6568174383 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
>>>         <mailto: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
>>>         <http://203.205.28.49:40388>;transport=udp
>>>         ID=0cdb7f9c6ba3796c67fd40b306524015 at 122.152.145.115:5060-b2b_1
>>>         <mailto: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
>>>         <http://203.205.28.49:40388>;transport=udp
>>>         ID=0cdb7f9c6ba3796c67fd40b306524015 at 122.152.145.115:5060-b2b_1
>>>         <mailto: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
>>>         <http://203.205.28.49:40388>;transport=udp
>>>         F=<mailto:sip%3A6568174383 at 122.152.145.120>sip:6568174383@
>>> 122.152.145.120
>>>         <mailto:sip:6568174383 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
>>>         <mailto: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
>>>         <http://203.205.28.49:40388>;transport=udp
>>>         ID=0cdb7f9c6ba3796c67fd40b306524015 at 122.152.145.115:5060-b2b_1
>>>         <mailto: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
>>>         <http://203.205.28.49:40388>;transport=udp
>>>         ID=0cdb7f9c6ba3796c67fd40b306524015 at 122.152.145.115:5060-b2b_1
>>>         <mailto: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
>>>>             <<mailto:dboghici at sipwise.com>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/im
>>>> ages/sip_provider_CE_installcd.iso
>>>>                 <http://deb.sipwise.com/spce/i
>>>> mages/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
>>>
>>         --
>>         Dan Boghici
>>         Sales Engineer
>>         https://www.youtube.com/watch?v=n1xK8G1VEiQ
>>         <https://www.youtube.com/watch?v=n1xK8G1VEiQ>
>>
>>
>>
>>
>>     --
>>     Thanks and Regard,
>>     Cedric Le
>>
>>
>>
>>
>> --
>> Thanks and Regard,
>> Cedric Le
>>
>>
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> https://lists.sipwise.com/listinfo/spce-user
>>
>> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
>



-- 
Thanks and Regard,
Cedric Le
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20170112/8d90870e/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 11399 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20170112/8d90870e/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 51575 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20170112/8d90870e/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 26922 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20170112/8d90870e/attachment-0005.png>


More information about the Spce-user mailing list