08-28-2013 12:32 PM - last edited on 03-25-2019 09:09 PM by ciscomoderator
Hello,
When I change to the tms prosioning extensionmode , do not work sip to sip calls oand calls from the internet to my internal network.
I know that because when i change back to the agent tms legacy mode,the calls work perfectly, why?
I tried configuring zones in check credentials and treated as authenticated but the problem continue.
What I can do?
08-28-2013 02:20 PM
Hello
I guess you are talking about Jabber/Movi clients cannot call to internet and SIP <> SIP calls does not work when you switch to TMSPE.
have you configured provisioning template on TMSPE for Jabber?
did you review the settings in provisioning template and are they correct?
have you checked jabber/Movi clients are getting the provisioning info?
are there the logs shows regarding this failure?
have you run the TMS diagnostics tool after switching?
are you sure the templates are getting pushed to VCS?
need much more data to assist you.
regards, Ahmad
08-28-2013 02:34 PM
No, the problem is as follows:
I have an Internet connected EX90 registered in VCS-E, and another EX90 registered at the internal network with VCS-C when i enable mode TMS Provioning Extension, ex90 from the internet can not make calls but it receives from the internal network via h323.
Now, when I place both within the internal network by registering on the VCS-C, I can make calls from both EX90 via H323 but not SIP-SIP
When I change the mode TMS Agent everything works OK.
08-28-2013 02:41 PM
sounds like you haven't implemented all the setting parameters in provisioning template for EX90 on TMSPE.
have you defined any bandwidth restriction on your provisioning settings?
can you post your provisioning template setting here?
08-29-2013 09:00 AM
The ex90 is registered perfectly well, I can place calls h323 to h323 but no sip-sip, only do so if I go back to TMS Agent mode ... When attempting to call sip alias once tells me can not connect . On the call>>history appears :
Name | Value | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
H323 Profile Authentication LoginName | {first_name}_{last_name} | ||||||||||||||||||||
H323 Profile Authentication Mode | On | ||||||||||||||||||||
H323 Profile CallSetup Mode | Gatekeeper | ||||||||||||||||||||
H323 Profile Gatekeeper Address | 192.168.0.xx | ||||||||||||||||||||
H323 Profile H323Alias E164 | {office_phone} | ||||||||||||||||||||
H323 Profile H323Alias ID | {office_phone}@protokolgroup.com | ||||||||||||||||||||
Network Assignment | DHCP | ||||||||||||||||||||
Provisioning ExternalManager Address | clustername.protokolgroup.com | ||||||||||||||||||||
Provisioning ExternalManager Domain | protokolgroup.com | ||||||||||||||||||||
Provisioning Mode | Auto | ||||||||||||||||||||
Public SIP Server Address | xxx.xx.xx.xx | ||||||||||||||||||||
SIP Profile Authentication LoginName | {first_name}_{last_name} | ||||||||||||||||||||
SIP Profile DefaultTransport | Auto | ||||||||||||||||||||
SIP Server Address | 192.168.0.xxx | ||||||||||||||||||||
Time TimeFormat | 12H | ||||||||||||||||||||
Time Zone | GMT-04:30 (Caracas) |
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: