This is for more general topics about networking and vendors.
1 post • Page 1 of 1
I am trying to connect to XO using SIP. The page in CCA is very simple, a couple of IP addresses and the username and password. The config that it generates does not work. So what is bad is that any changes I make will make it so that I cant work with the entire VOICE window. The XO tech asked me for this: sip-ua authentication username 7-XXX password 7XXXXXXXXXXXX no remote-party-id retry invite 2 retry register 10 timers connect 100 registrar ipv4:XXX.XXX.148.155:5060 expires 3600 sip-server ipv4:XXX.XXX.148.155:5060 host-registrar The tech made edits and sent me this to put back into the router: credentials username XXX9600 password 7-XXX realm XXX.XXX.148.155 credentials username 7-XXX password 7-XXX realm XXX.XXX.148.155 authentication username 7-XXX password 7-XXX realm XXX.XXX.148.155 no remote-party-id retry invite 2 retry register 3 timers connect 100 mwi-server ipv4:10.1.10.1 expires 3600 port 5060 transport udp registrar ipv4:XXX.XXX.148.155:5060 expires 3600 sip-server ipv4:XXX.XXX.148.155:5060 Sorry this community text editor is re-formating the commands into a paragraph and it wont let me return it to a list. I have a customer that cant make calls and TAC usually has no clue about CCA. Please help ASAP. Thanks Message was edited by: eoncablewire
Not sure why the XO tech added the additional credentials CLI & mwi server (that is what I could read based on the post) - assume that still did not make a difference? Can you provide a complete show run & deb ccsip message of calls that fail so I can take a look (you can PM me if you wish). Note, if you use the Generic SIP Trunk provider option, CCA does allow a lot more GUI fields to enter and match what the XO tech is sending over.
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.
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.
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