CCA 2.0 XO config does not work

Post a reply


In an effort to prevent automatic submissions, we require that you complete the following challenge.
Smilies
:D :) ;) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :!: :?: :idea: :arrow: :| :mrgreen: :geek: :ugeek:

BBCode is ON
[img] is ON
[flash] is OFF
[url] is ON
Smilies are ON

Topic review
   

Expand view Topic review: CCA 2.0 XO config does not work

Re:CCA 2.0 XO config does not work

by Guest » Sat Jan 08, 2011 7:02 pm

We discovered that CCA support static sip trunking for XO and the line was provisioned for dymanic sip which at this time CCA mostly supports using the generic sip provider. The MWI setting was requested by XO but may not have been needed. I suppose this could have been a problem with any provider, when you dont know if they were using static or dynamic sip. I had not heard of that before but now I know plenty! Thanks for the help, we are up and running now.

Re:CCA 2.0 XO config does not work

by Guest » Sat Jan 08, 2011 6:08 pm

If you are asking for the CLI then essentially here is what CCA does if you want to register all DIDs with the same username / password combination (note DIDs / username / password are all examples) 1.Each DID is mapped to an extension (i.e. ephone-dn) as belowephone-dn 10 dual-line number 201 secondary 4085559601 no-reg  primary!ephone-dn 11 dual-linenumber 202 secondary 4085559602 no-reg  primary 2. Authentication is globally configuredsip-ua  authentication username 4085559600 password test 3. Configure registrar serversip-ua  registrar ipv4:x.x.x.x (or DNS) Now you can check the status via - show sip reg stat. I want to make it clear that CCA does actually do this on the back end when you add a DID to extension mapping in the Inbound Dialplan section

Re:CCA 2.0 XO config does not work

by Guest » Sat Jan 08, 2011 6:04 pm

How does CCA write the authentication for teh DIDs? In this case we are needing to enter a seperate authentication line for EVERY did, all 60! I would like to see what a config looks like that works with XO AND was configured with the XO choice in the dropdown list. Thanks

Re:CCA 2.0 XO config does not work

by Guest » Sat Jan 08, 2011 5:21 pm

Past installs with XO required no realm and did require registration of all DIDs with the same username / password which is done in CCA with the current fields available. Hence no additional fields are available. From what you state, sounds like this is not the case with this XO deployment (not sure if its different service packages). If you have the configs & debugs or a TAC case number would like to followup and ensure this works.

Re:CCA 2.0 XO config does not work

by Guest » Sat Jan 08, 2011 4:23 pm

Thanks for the response. I have TAC and XO on the line with no success. I just dont understand how CCA worked in the past with this type of problem. I dont have access to the config right now as they are working on it. Everything seems to center on adding the realm at the end of the authentication and apparently needing to register each individual sip did as well. So far no success.  My only complaint is that if XO is a certified provider then why dont they offer more fields for configuration OR add them to the config for us.

Top