Sunil,
Sorry for not being clear before. One of the reasons SIP end
points register dynamically is to keep up to date contact information on
the Registrar. That requirement in your scenario is removed as the end
device does not move (not easily anyway), it is not like a IP phone or a
soft client that can potentially change addressing easily per user. The
software I work on is commercial and I am less familar with open source
Application Server / Registrars, but when I said static I meant that the
[EMAIL PROTECTED] is manually defined.
In your example below the service provider etc would manually
configure [EMAIL PROTECTED], [EMAIL PROTECTED] etc.
In the configurations I have seen the GW does not register on
behalf of the phones.
Wayne Davies
sunil vatnal <[EMAIL PROTECTED]>
29/10/2004 05:34 PM
Please respond to sunil vatnal
To: [EMAIL PROTECTED]
cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: [Sip-implementors] T1 channel registration in SIP gateway
Hi Wayne/All,
Basically, I am interested to know how the individual phones are
registered in the SIP Registrar server in this scenario.
In the cases of sip softphones or the SIP ip endpoints, they will get
registered with server after sending REGISTER messages with [EMAIL PROTECTED] endpoint
name.
But when SIP g/w is connected to T1 interface, individual phones cannot be
registered like SIP ip endpoints.
As you have replied, static registration is happening here. Could you
please give some more information on this static registration of the SIP
g/w.
--------------- ------------ ------ Phone A
| SIP Server | -----------> | SIP G/W | ---------------------PBX
------ phone B
| | SIP | | T1 ------ phone
C
--------------- ------------ ------ phone D
Thanks and regards,
- sunil vatnal
----- Original Message -----
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED] ; [EMAIL PROTECTED]
Sent: Friday, October 29, 2004 2:01 PM
Subject: Re: [Sip-implementors] T1 channel registration in SIP gateway
Sunil,
It is somewhat typical IMO that a GW device in this scenario would
be statically assigned to a user - and the server acting as a Application
Server / Registrar will hold a this static registration that will not
expire.
As an example:
When a incoming call comes into the the Application Server for an
extension off the PBX the Application Server will INVITE the GW device to
setup a call. The incoming INVITE at the GW will match a dial-peer (or
whatever CPE specific config / terminology is applicable to the device)
and perform the setup signalling over the E1/T1 connection to the PBX.
Where it goes from here touches on other things - SIP to ISUP
mapping etc, but your original query should be answered I hope.
Regards,
Wayne.
MVATNAL SUNIL <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
29/10/2004 12:05 PM
Please respond to sunil.vatnal
To: [EMAIL PROTECTED]
cc:
Subject: [Sip-implementors] T1 channel registration in SIP
gateway
Dear SIP implementers,
In the architecture shown below,
--------------- ------------
| Call Manager| -----------> | SIP G/W | ---------------------PBX
| | SIP | | T1
--------------- ------------
How the gateway is going to register with the SIP server, i.e., Call
Manager?
Is each and very phone connected with the gateway going to be registered
with the Server?
Please explain the T1 23 registration process in this case.
Lots of thanks,
- sunil vatnal
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
******************************************************************************
- NOTICE FROM DIMENSION DATA AUSTRALIA
This message is confidential, and may contain proprietary or legally
privileged information. If you have received this email in error, please
notify the sender and delete it immediately.
Internet communications are not secure. You should scan this message and
any attachments for viruses. Under no circumstances do we accept liability
for any loss or damage which may result from your receipt of this message
or any attachments.
******************************************************************************
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
