Hi Roman, Thanks for giving me access to your box. I'm bringing this thread back online. As I described in this thread, all you need to do is to NOT mess around with the xml file and let sendRegister() method do its magic. Your Karoo Bridge is now happily registered with call centric. If you have more questions, feel free to post them here so that others may learn how to use the bridge as well. Happy Flexi-Routing.
Joegen On 06/12/2011 10:52 AM, Roman Gelfand wrote: > Is there anyway I could debug it to see what is causing it. > > Also, based on what you are saying, it sounds kind of odd that I am > trying to authenticate back with my server instead of going to > callcentric. > > On Fri, Jun 10, 2011 at 5:44 PM, Joegen Baclor<[email protected]> wrote: >> The port shoudn't matter. >> >> On 06/11/2011 04:17 AM, Roman Gelfand wrote: >>> My firewall is in transparent mode. Both inside and outside is open. >>> >>> On Fri, Jun 10, 2011 at 11:43 AM, Tony Graziano >>> <[email protected]> wrote: >>>> It might also matter how your firewall is treating that port. >>>> >>>> On Fri, Jun 10, 2011 at 12:08 PM, Roman Gelfand<[email protected]> >>>> wrote: >>>>> I just confirmed there is a ton srv records for callcentric.com. >>>>> Looking up srv record for callcentric, I found they are listening on >>>>> port 5080. Does it matter here? >>>>> >>>>> On Fri, Jun 10, 2011 at 6:08 AM, Joegen Baclor<[email protected]> >>>>> wrote: >>>>>> Function prototype for sendRegister() is >>>>>> >>>>>> RouteProfile.prototype.sendRegister = function(user, domain, password, >>>>>> proxy, expires, interfaceIndex) >>>>>> >>>>>> Proxy must be an FQDN , SRV record or an IP address. if >>>>>> callcentric.com is >>>>>> not an SRV, you will have issues. >>>>>> >>>>>> You should not mess around with the gateway XML file. It should point >>>>>> to >>>>>> karoo bridge. Karoo bridge will rewrite this request internally and >>>>>> put >>>>>> the correct domain in the request uri as it gets out. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On 06/10/2011 08:41 PM, Roman Gelfand wrote: >>>>>>> I already send them this log and freeswitch.fsxml file. They are >>>>>>> saying that I should remove the following lines from configuration. >>>>>>> >>>>>>> <param name="proxy" value="[Karoo Public IP]:5060"/> >>>>>>> <param name="register-proxy" value="[Karoo Public IP]:5060"/> >>>>>>> >>>>>>> Perhaps, this explains that it is trying to authenticate to me instead >>>>>>> of callcentric. >>>>>>> >>>>>>> May be my handlers are bad... >>>>>>> >>>>>>> >>>>>>> sip.cfg >>>>>>> ---------- >>>>>>> >>>>>>> interfaces = ( >>>>>>> { >>>>>>> default = true; >>>>>>> ip-address = "[Karoo Public IP]"; >>>>>>> tcp-enabled = false; >>>>>>> sip-port = 5060; >>>>>>> }, >>>>>>> { >>>>>>> ip-address = "[Karoo Lan IP]"; >>>>>>> tcp-enabled = false; >>>>>>> sip-port = 5060; >>>>>>> } ); >>>>>>> >>>>>>> >>>>>>> routes.js >>>>>>> -------------- >>>>>>> >>>>>>> function Route() >>>>>>> { >>>>>>> this.sendRegister( >>>>>>> "[user id]", "callcentric.com", "pwd", "callcentric.com", >>>>>>> 1800, >>>>>>> 0); >>>>>>> } >>>>>>> >>>>>>> Route.prototype = new RouteProfile(); >>>>>>> >>>>>>> Route.prototype.isRoutable = function() >>>>>>> { >>>>>>> if (is_mysipdomain_routable(this)) >>>>>>> return true; >>>>>>> else >>>>>>> return false; >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Tue, Jun 7, 2011 at 6:41 PM, Joegen Baclor<[email protected]> >>>>>>> wrote: >>>>>>>> Roman, >>>>>>>> >>>>>>>> Your ITSP keeps on saying your registration is stale. Would you be >>>>>>>> able >>>>>>>> to >>>>>>>> send them this log and ask why they think the reg is stale? >>>>>>>> >>>>>>>> One thing I see in error is that the uri in the proxy-authorization >>>>>>>> header >>>>>>>> is uri="sip:[Karoo Public IP]:5060". It should be >>>>>>>> sip:callcentric.com. >>>>>>>> Did >>>>>>>> you manually change any thing in the XML config files by hand? >>>>>>>> >>>>>>>> ---- >>>>>>>> >>>>>>>> 10:07:31.809: [CID=c0c0cbc6]>>> REGISTER >>>>>>>> sip:callcentric.com;transport=udp SIP/2.0 LEN: 843 SRC: [Karoo Public >>>>>>>> IP]:5060 DST: 204.11.192.23:5060 ENC: 0 PROT: udp >>>>>>>> 10:07:31.810: >>>>>>>> { >>>>>>>> [CID=c0c0cbc6] REGISTER sip:callcentric.com;transport=udp >>>>>>>> SIP/2.0 >>>>>>>> [CID=c0c0cbc6] From:<sip:[SIP User or account >>>>>>>> ID]@callcentric.com;transport=udp>;tag=HBm0jHa04patc >>>>>>>> [CID=c0c0cbc6] To:<sip:[SIP User or account >>>>>>>> ID]@callcentric.com;transport=udp> >>>>>>>> [CID=c0c0cbc6] Call-ID: 05b34627-633a-4506-b3f7-90f4eb843d39 >>>>>>>> [CID=c0c0cbc6] CSeq: 13233363 REGISTER >>>>>>>> [CID=c0c0cbc6] Expires: 1800 >>>>>>>> [CID=c0c0cbc6] User-Agent: OSS Karoo FS >>>>>>>> [CID=c0c0cbc6] Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, >>>>>>>> MESSAGE, >>>>>>>> UPDATE, INFO, REGISTER, REFER, NOTIFY >>>>>>>> [CID=c0c0cbc6] Supported: timer, precondition, path, replaces >>>>>>>> [CID=c0c0cbc6] Proxy-Authorization: Digest username="[SIP >>>>>>>> User or >>>>>>>> account ID]", realm="callcentric.com", >>>>>>>> nonce="b4ab72d4da9cad28ae9cf62d73f7dde9", opaque="", algorithm=MD5, >>>>>>>> uri="sip:[Karoo Public IP]:5060", >>>>>>>> response="38edd6a4a5ac2d46c125309407bc62b9" >>>>>>>> [CID=c0c0cbc6] Content-Length: 0 >>>>>>>> [CID=c0c0cbc6] Max-Forwards: 69 >>>>>>>> [CID=c0c0cbc6] Contact:<sip:[SIP User or account ID]@[Karoo >>>>>>>> Public >>>>>>>> IP]:5060;transport=udp> >>>>>>>> [CID=c0c0cbc6] Via: SIP/2.0/UDP [Karoo Public >>>>>>>> IP]:5060;branch=z9hG4bKe0d8900e-8e2d-11e0-a907-0800274986dc;rport >>>>>>>> }; >>>>>>>> 10:07:31.863: [CID=c0c0cbc6] Found Transaction >>>>>>>> register13233363z9hG4bKe0d8900e-8e2d-11e0-a907-0800274986dc >>>>>>>> 10:07:31.863: [CID=c0c0cbc6]<<< SIP/2.0 407 Proxy >>>>>>>> Authentication >>>>>>>> Required LEN: 498 SRC: 204.11.192.23:5060 DST: [Karoo Public IP]:5060 >>>>>>>> EXT: >>>>>>>> [[Karoo Public IP]] ENC: 0 PROT: udp >>>>>>>> 10:07:31.864: >>>>>>>> { >>>>>>>> [CID=c0c0cbc6] SIP/2.0 407 Proxy Authentication Required >>>>>>>> [CID=c0c0cbc6] v: SIP/2.0/UDP [Karoo Public >>>>>>>> >>>>>>>> IP]:5060;branch=z9hG4bKe0d8900e-8e2d-11e0-a907-0800274986dc;rport=5060 >>>>>>>> [CID=c0c0cbc6] f:<sip:[SIP User or account >>>>>>>> ID]@callcentric.com;transport=udp>;tag=HBm0jHa04patc >>>>>>>> [CID=c0c0cbc6] t:<sip:[SIP User or account >>>>>>>> ID]@callcentric.com;transport=udp> >>>>>>>> [CID=c0c0cbc6] i: 05b34627-633a-4506-b3f7-90f4eb843d39 >>>>>>>> [CID=c0c0cbc6] CSeq: 13233363 REGISTER >>>>>>>> [CID=c0c0cbc6] Proxy-Authenticate: Digest >>>>>>>> realm="callcentric.com", >>>>>>>> domain="sip:callcentric.com", >>>>>>>> nonce="03cf3951967118bca596862d5d64be5b", >>>>>>>> opaque="", stale=TRUE, algorithm=MD5 >>>>>>>> [CID=c0c0cbc6] l: 0 >>>>>>>> }; >>>>>>>> >>>>>>>> >>>>>>>> On 06/07/2011 09:15 PM, Roman Gelfand wrote: >>>>>>>> >>>>>>>> I have generated debug log of a registration attempt. Please, find >>>>>>>> the attached log file. >>>>>>>> Thanks in advance >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> sipx-users mailing list >>>>>>>> [email protected] >>>>>>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>>>>>>> >>>>> _______________________________________________ >>>>> sipx-users mailing list >>>>> [email protected] >>>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>>>> >>>> >>>> -- >>>> ====================== >>>> Tony Graziano, Manager >>>> Telephone: 434.984.8430 >>>> sip: [email protected] >>>> Fax: 434.326.5325 >>>> >>>> Email: [email protected] >>>> >>>> LAN/Telephony/Security and Control Systems Helpdesk: >>>> Telephone: 434.984.8426 >>>> sip: [email protected] >>>> >>>> Helpdesk Contract Customers: >>>> http://support.myitdepartment.net >>>> Blog: >>>> http://blog.myitdepartment.net >>>> >>>> Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 >>>> _______________________________________________ >>>> sipx-users mailing list >>>> [email protected] >>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>>> >>> _______________________________________________ >>> sipx-users mailing list >>> [email protected] >>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>> >> _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
