Provisioning Web Service - Extra SIP Accounts and Extensions
Is there any form of sys.Dial("local") call, or any other way to ring all subaccounts registered with MSS, and not only clients registered with one subaccount or main account username?
What I'm trying to do is:
(1) by default forward all incoming calls to all registered clients;
(2) be able to route certain calls to one subaccount only.
If all my clients are registered with the same username, I can do (1) but not (2). And if different clients are using different subaccounts I can't find a way to do (1) ...
Thanks!
What I'm trying to do is:
(1) by default forward all incoming calls to all registered clients;
(2) be able to route certain calls to one subaccount only.
If all my clients are registered with the same username, I can do (1) but not (2). And if different clients are using different subaccounts I can't find a way to do (1) ...
Thanks!
How do I answer or route calls coming in on extensions?
I have st up sub-domains, accounts and extensions, but when I ring an extension, it returns 404 Not Found. In the monitoring log, is a message:
But that's all I see, I can't 'process' it in my dial plan.
I have st up sub-domains, accounts and extensions, but when I ring an extension, it returns 404 Not Found. In the monitoring log, is a message:
Code: Select all
Incoming call on extension for iangrant to sip:xxxxxx@sub-domain from yyyyy@voxalot.com.
The only place you should be attempting to use web services with mss is at the link below. There are no authid's required there.
http://www.mysipswitch.com/provisioning.asmx
http://www.mysipswitch.com/provisioning.asmx
i agree that exactly this WSDL doesn't require authid
meanwhile there is already in place the AJAX infrastructure, you know, which is also ready to use and is activelly used
so such the functionality like list providers, add/update provider etc might be also explicetly allowed to use via web services...
i guess you mind it, don't you?
meanwhile there is already in place the AJAX infrastructure, you know, which is also ready to use and is activelly used
so such the functionality like list providers, add/update provider etc might be also explicetly allowed to use via web services...
i guess you mind it, don't you?
No I don't mind at all the services are there to use. The consideration is the time and priority of doing the work to convert those web services to using a username/password of putting together a new web service to give you an authid. We've never had a request or need to expose those web services in any other form up until now.shkaff wrote:i agree that exactly this WSDL doesn't require authid
meanwhile there is already in place the AJAX infrastructure, you know, which is also ready to use and is activelly used
so such the functionality like list providers, add/update provider etc might be also explicetly allowed to use via web services...
i guess you mind it, don't you?
If you asked Guillaume nicely he might have time to come up with the authid web service.
Regards,
Aaron