<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi Daniel,</p>
<p>You have this chapter in Handbook but is does not go in details
for Registration Mode. Can you check this and provide more info
for Registration Mode.<br>
</p>
<h4 class="title">7.10.4. Registration</h4>
<p>SIP-PBX can use either Static or Registration Mode. While
SIPconnect 1.1 continues to require TLS support at MUST strength,
one should note that using TLS for signaling does not require the
use of the SIPS URI scheme. SIPS URI scheme is obsolete for this
purpose.</p>
<p><b>Static Mode. </b>While SIPconnect 1.1 allows the use of Static
mode, this poses additional maintenance overhead on the operator.
The administrator should create a static registration for the
SIP-PBX: go to Susbcribers, <span class="emphasis"><em>Details</em></span>→<span
class="emphasis"><em>Registered Devices</em></span>→<span
class="emphasis"><em>Create Permanent Registration</em></span>
and put address of the SIP-PBX in the following format:
<a class="moz-txt-link-freetext" href="sip:username@ipaddress:5060">sip:username@ipaddress:5060</a> where username=username portion of SIP
URI and ipaddress = IP address of the device.</p>
<p><b>Registration Mode. </b>It is recommended to use the
Registration mode with SIP credentials defined for the SIP-PBX
subscriber.</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 9/29/2020 11:20 AM, Daniel Grotti
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:012acb22-e95c-cced-7926-f16f497b9ec5@sipwise.com">Hi,
<br>
you can have the following VOIP entities:
<br>
<br>
<br>
1. SIP trunk, or peering
<br>
This is a peering for the SPCE, used to send calls outside the
system, to PSTN, mobile, other providers. As well as receive
incoming calls from outside world.
<br>
<br>
This is configured in the PEERINGS section.
<br>
Peerings are autheticated via source IP for incoming calls, so
external peering CANNOT register agains SPCE.
<br>
<br>
Another scenario is that your provided(peering) is asking you to
authenticate when sending call out to him, and this can be done
using the peering's preference REMOTE AUTHENTICATION section.
<br>
<br>
<br>
2. Subscribers.
<br>
<br>
This are the local user in SPCE.
<br>
They can be simple SIP phones, or PBX, or any other kind of VOIP
system that requires to be your subscriber.
<br>
<br>
As your subscriber, they (can) REGISTER agains SPCE, using
username/password.
<br>
<br>
This credentials can be configured in a SIP phone or in an
Asterisk PBX. SPCE will act and Asterisk trunk, where asterisk or
any other PBX will send the outbound call to.
<br>
<br>
Subscribers that does not support DIGEST authentication, can be
authenticate by source IP or From Pattern. Also SPCE can send call
to them using the STATIC REGISTRATION. Please see documentation
about this case.
<br>
<br>
<br>
<br>
<br>
Hope this help,
<br>
<br>
<br>
<br>
Daniel Grotti
<br>
<br>
Head of Customer Support Sipwise GmbH
<br>
e: <a class="moz-txt-link-abbreviated" href="mailto:dgrotti@sipwise.com">dgrotti@sipwise.com</a> Europaring F15
<br>
t: +43(0)130120332 A-2345 Brunn Am Gebirge
<br>
w: <a class="moz-txt-link-abbreviated" href="http://www.sipwise.com">www.sipwise.com</a> FN: 305595f FG: LG Wiener Neustadt
<br>
<br>
On 9/29/20 11:08 AM, Neofone Info wrote:
<br>
<blockquote type="cite">Thank you for your time but maybe what i
searching to archive is not so usual with SPCE.
<br>
<br>
I have a SIP trunk where there i receive specific calls and the
calls need to be answered by a phone.
<br>
<br>
the SIP trunk has registration credentials in order to work. SIP
trunk needs to register in SPCE than i can route the received
calls to the subscribers.
<br>
<br>
the link provided is for outbound calls and registering outbound
peers. in need for inbound calls
<br>
<br>
On 9/29/2020 12:41 AM, Matthias Hohl wrote:
<br>
<blockquote type="cite">Again: what setup do you want?
<br>
<br>
Create a subscriber on SPCE and connect your pbx via this
subscriber and phones on the pbx.
<br>
Then create a peering on SPCE and connect them to a Carrier
SIP Trunk provider.
<br>
<br>
Thats normal setup.
<br>
<br>
If you want a PBX as your carrier, use IP Athentification or
enable user/pass authentification for peerings.
<br>
<br>
Check handbook for details.
<br>
<br>
=> create peering
<br>
=> create subscriber
<br>
<br>
All in all, read the handbook carefully
<br>
<br>
<br>
<blockquote type="cite">Am 28.09.2020 um 21:28 schrieb Neofone
Info <a class="moz-txt-link-rfc2396E" href="mailto:info@neofone.al"><info@neofone.al></a>:
<br>
<br>
<br>
<br>
hello,
<br>
<br>
<br>
I have a Sip Trunk that is with registration. So i need it
to receive calls. Why this seem so strange you can do it in
Asterisk in trunks.
<br>
<br>
Thanks
<br>
<br>
<br>
On 9/28/2020 8:02 PM, Matthias Hohl wrote:
<br>
<blockquote type="cite">
<br>
Hello,
<br>
<br>
no it is definitely no PBX at the end of the day.
<br>
<br>
It is a SIP server solution for providing a peering
connection to several hundreds or thousands of subscriber.
<br>
<br>
I really don’t get the point for what reason you want to
connect a SPCE to a PBX.. what is your plan?
<br>
<br>
Normally it goes this way: PTSN/SIP-NNI => SPCE =>
PBX
<br>
<br>
For sure you can, but you have to enable user/pass
authenficiation for peerings.
<br>
<br>
But anyway, this is not common… normally you do Peering
connections via ip authorization.
<br>
<br>
But like I told before, I really don’t get the point, what
you want to do with that.
<br>
<br>
*Von:*Neofone Info <a class="moz-txt-link-rfc2396E" href="mailto:info@neofone.al"><info@neofone.al></a>
<br>
*Gesendet:* Montag, 28. September 2020 19:25
<br>
*An:* Matthias Hohl <a class="moz-txt-link-rfc2396E" href="mailto:matthias.hohl@telematica.at"><matthias.hohl@telematica.at></a>;
'Walter Klomp' <a class="moz-txt-link-rfc2396E" href="mailto:walter@myrepublic.net"><walter@myrepublic.net></a>
<br>
*Cc:* <a class="moz-txt-link-abbreviated" href="mailto:spce-user@lists.sipwise.com">spce-user@lists.sipwise.com</a>
<br>
*Betreff:* Re: AW: [Spce-user] Register a PBX to SipWise
CE
<br>
<br>
I have information that can be done in CE.
<br>
<br>
CE is not a PBX at the end of the day? why i can register
a CE to a PBX and can't do the same with a PBX register in
CE? i have specific username and password of PBX that
can't be changed.
<br>
<br>
with register i mean the registration process of a device.
in a sip client you register a subscriber i need this also
in CE.
<br>
<br>
peering does not have option to register for incoming
calls or at least i didn't found it.
<br>
<br>
Thanks
<br>
<br>
On 9/28/2020 5:32 PM, Matthias Hohl wrote:
<br>
<br>
Hello,
<br>
<br>
i think you misunderstand the workflow of the SPCE.
<br>
<br>
You can’t register the SPCE as a subscriber on the
PBX.
<br>
<br>
You need to register the PBX as a subscriber on the
SPCE!
<br>
<br>
So you create a new subscriber on the SPCE and connect
your PBX
<br>
via the SPCE IP and the created Username and Password
of the
<br>
subscriber.
<br>
<br>
If you want to connect your PBX as a peering to the
SPCE, really
<br>
don’t know for what reason, than you can create a SPCE
Peering
<br>
and connect the SPCE to the PBX, but I really don’t
know why you
<br>
want to do this.
<br>
<br>
*Von:*Neofone Info <a class="moz-txt-link-rfc2396E" href="mailto:info@neofone.al"><info@neofone.al></a>
<a class="moz-txt-link-rfc2396E" href="mailto:info@neofone.al"><mailto:info@neofone.al></a>
<br>
*Gesendet:* Montag, 28. September 2020 17:09
<br>
*An:* Walter Klomp <a class="moz-txt-link-rfc2396E" href="mailto:walter@myrepublic.net"><walter@myrepublic.net></a>
<br>
<a class="moz-txt-link-rfc2396E" href="mailto:walter@myrepublic.net"><mailto:walter@myrepublic.net></a>
<br>
*Cc:* <a class="moz-txt-link-abbreviated" href="mailto:spce-user@lists.sipwise.com">spce-user@lists.sipwise.com</a>
<br>
<a class="moz-txt-link-rfc2396E" href="mailto:spce-user@lists.sipwise.com"><mailto:spce-user@lists.sipwise.com></a>
<br>
*Betreff:* Re: [Spce-user] Register a PBX to SipWise
CE
<br>
<br>
so you are saying that in a subscriber where i need to
create
<br>
username and password instead of this i enter username
and
<br>
password of the other PBX that i want to register in
sipwise?
<br>
<br>
i have the credential of another PBX and want to
register in
<br>
sipwise.
<br>
<br>
thanks
<br>
<br>
On 9/28/2020 4:25 PM, Walter Klomp wrote:
<br>
<br>
Just create a subscriber and use the username and
password
<br>
to register your PBX to it.
<br>
<br>
On Mon, 28 Sep 2020 at 21:00, Neofone Info
<<a class="moz-txt-link-abbreviated" href="mailto:info@neofone.al">info@neofone.al</a>
<br>
<a class="moz-txt-link-rfc2396E" href="mailto:info@neofone.al"><mailto:info@neofone.al></a>> wrote:
<br>
<br>
I am checking to configure a PBX in SipWice
CE. Register
<br>
it in sipwise
<br>
<br>
<br>
<br>
There is not information how i can register a
PBX with
<br>
username password
<br>
<br>
and host in sipwise CE.
<br>
<br>
<br>
<br>
can anyone send a link where this is covered
or provide
<br>
information how
<br>
<br>
i can register a PBX in sipwise to receive
calls?
<br>
<br>
<br>
<br>
thanks
<br>
<br>
<br>
<br>
<br>
<br>
-- <br>
Spce-user mailing list
<br>
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a>
<br>
<a class="moz-txt-link-rfc2396E" href="mailto:Spce-user@lists.sipwise.com"><mailto:Spce-user@lists.sipwise.com></a>
<br>
<br>
<a class="moz-txt-link-freetext" href="https://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com">https://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com</a>
<br>
<br>
-- <br>
Warmest Regards,
<br>
<br>
<br>
<a class="moz-txt-link-rfc2396E" href="https://myrepublic.com.sg/"><https://myrepublic.com.sg/></a>
<br>
<br>
<br>
<br>
*Walter Klomp*
<br>
<br>
Head of Voice & Systems
<br>
<br>
MyRepublic Limited
<br>
<br>
T: +65 6816 1120
<br>
<br>
F: +65 6717 2031
<br>
<br>
MyRepublic Limited
<br>
<br>
11 Lorong 3 Toa Payoh Block B Jackson Square
<br>
<br>
#04-11/15 Singapore 319579
<br>
<br>
<br>
myrepublic.com.sg
<a class="moz-txt-link-rfc2396E" href="https://myrepublic.com.sg/"><https://myrepublic.com.sg/></a>
<br>
<br>
Follow us on: Twitter
<a class="moz-txt-link-rfc2396E" href="https://twitter.com/myrepublic"><https://twitter.com/myrepublic></a> |
<br>
Facebook
<a class="moz-txt-link-rfc2396E" href="https://facebook.com/myrepublicsg"><https://facebook.com/myrepublicsg></a> | LinkedIn
<br>
<a class="moz-txt-link-rfc2396E" href="https://www.linkedin.com/company/myrepublic"><https://www.linkedin.com/company/myrepublic></a>
<br>
<br>
<br>
<br>
/The contents of this email and any attachments
are
<br>
confidential and may also be privileged. You must
not
<br>
disseminate the contents of this email and any
attachments
<br>
without permission of the sender. If you have
received this
<br>
email by mistake, please delete all copies and
inform the
<br>
sender immediately. You may refer to our company's
Privacy
<br>
Policy here
<br>
<a class="moz-txt-link-rfc2396E" href="https://myrepublic.net/sg/legal/terms-of-use-policies/privacy-policy/"><https://myrepublic.net/sg/legal/terms-of-use-policies/privacy-policy/></a>./<br>
<br>
<br>
</blockquote>
</blockquote>
</blockquote>
<br>
</blockquote>
<br>
</blockquote>
</body>
</html>