kkttv
Intermediate
Joined: September 15 2008
Location: China
Posts: 1
|
| Posted: September 15 2008 at 5:58am | IP Logged
|
|
|
Dear Support,
I read the media engine developer reference. EnableSipRegisterServer can help user to register the phone lines to a sip register server. Do you support to register the selected phone lines to the sip register server only? Eg. register line 4, 7, 9 to the register server.
|
support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: September 15 2008 at 11:51am | IP Logged
|
|
|
Hi kkttv,
Thanks for posting your question.
You >>>
Do you support to register the selected phone lines to the sip register server only? Eg. register line 4, 7, 9 to the register server.
Support >>>
Yes, all of the individual phone lines of the media engine can be registered individually. In other words, any phone line can be associated with a registration name/extension.
Note however that if your VOIP app calls the EnableSipRegisterServer() API proc to register named for individual phone lines, make sure you specify a bogus registration name for the lines that you do not want to receive incoming calls.
For example: Assume we have a 16 line media engine, we could register valid extensions for phone lines 4, 6 and 9 using the following code:
Code:
.
.
.
TELEPHONY_RETURN_VALUE satus;
Status = EnableSipRegisterServer(
hStateMachine,
// the registration names for each phone line 0 trough 15.
“bogus, bogus, bogus, bogus,444, bogus,666, bogus, bogus,999, bogus, bogus, bogus, bogus, bogus, bogus”,
TRUE, // register individual phone line names.
TRUE, // registrar is the same as your proxy.
“MyProxy.com” // your registrar’s host address.
5060, // your registrar’s UDP server port.
3600, // reregister period in seconds.
3600, // registration expire time – seconds.
4000, // register response time out Ms.
FALSE // do not detect NAT via registration cycles.
);
.
.
.
|
|
|
The code above will instruct the media engine to perform 4 registration cycles. One for the registration name “bogus”, on for the name “444”, one for the name “666” and one for the name “999”. Note that the order of the registration names specified map directly to line 0 through line 15 (16 total lines).
If your media engine receives a call for extension 444 (receives an INVITE request for extension 444), the media engine will only present the incoming call to lines having been registered using the name “444”. In this case, the incoming call would be mapped to the single line 4.
Note that if you specified extension “444” to be mapped to more than on line using the above API procedure, then the media engine could present the incoming call to any of the lines having the “444” extension.
Hope this helps. Repost if you want further info.
Thanks,
Support
|
Active Topics 
Member List 
Search 
Help 
Register 
Login
LanScape Support Forum -> LanScape VOIP Media Engine™ - Pre-Sales Technical Support
Topic: Sip Register Server Support
