Interesting... I had never heard of "Karoo Bridge" - I'll have to contact them and see if they will sponsor ClueCon. :P

If you don't have access to the fs_cli then just use tcpdump and grab the port 5060 traffic (or whatever port your SIP traffic is on) and check for clues. Once you know where the problem is then you can work on fixing it.

-MC

On Thu, Jun 2, 2011 at 5:33 PM, Roman Gelfand <rgelfand2@gmail.com> wrote:
Thanks for your help.

The actual application I am using is Karoo Bridge SBC which is built
on FreeSwitch.  I found freeswitch.xml.fsxml configuration file.  I
suppose this the final resolved configuraiton.  I am not sure where I
set debug option.

Anyway, I thought the following could be useful for you to see.


09:03:38.274:   [CID=29f64488] B2B Transaction CREATED -
register13166648z9hG4bKr84Dr2gK3ccHm
09:03:38.274:   [CID=29f64488] JS: Setting transaction property
respond-to-packet-source=1
09:03:38.274:   [CID=29f64488] JS: Setting transaction property
auth-method=access-list
09:03:38.274:   [CID=29f64488] JS: Setting transaction property auth-method=none
09:03:38.310:   [CID=29f64488] >>> REGISTER
sip:callcentric.com;transport=udp SIP/2.0 LEN: 843 SRC:
XX.XX.XXX.XXX:5060 DST: 204.11.192.37:5060 ENC: 0 PROT: udp
09:03:38.310: ^M
{^M
               [CID=29f64488] REGISTER
sip:callcentric.com;transport=udp SIP/2.0^M
               [CID=29f64488] From:
<sip:1##########@callcentric.com;transport=udp>;tag=v0r8KQHmF054m^M
               [CID=29f64488] To:
<sip:1##########@callcentric.com;transport=udp>^M
               [CID=29f64488] Call-ID: 99b2a5a7-1e7c-4e65-b9ac-6fadbf4ca1c3^M
               [CID=29f64488] CSeq: 13166648 REGISTER^M
               [CID=29f64488] Expires: 1800^M
               [CID=29f64488] User-Agent: OSS Karoo FS^M
               [CID=29f64488] Allow: INVITE, ACK, BYE, CANCEL,
OPTIONS, MESSAGE, UPDATE, INFO, REGISTER, REFER, NOTIFY^M
               [CID=29f64488] Supported: timer, precondition, path, replaces^M
               [CID=29f64488] Proxy-Authorization: Digest
username="1##########", realm="callcentric.com",
nonce="a0667bbc4a83b98f36b9619405daa1f5", opaque="", algorithm=MD5,
uri="sip:XX.XX.XXX.XXX:5060",
response="d4ee3820ca6f33ac8d40afc319b82006"^M
               [CID=29f64488] Content-Length: 0^M
               [CID=29f64488] Max-Forwards: 69^M
               [CID=29f64488] Contact:
<sip:1##########@XX.XX.XXX.XXX:5060;transport=udp>^M
               [CID=29f64488] Via: SIP/2.0/UDP
XX.XX.XXX.XXX:5060;branch=z9hG4bK34487872-8cf7-11e0-a33e-0800274986dc;rport^M
};
09:03:38.279:   [CID=29f64488] B2B Transaction DESTROYED -
register13166647z9hG4bKQZBNp7ZF63Nyr
09:03:38.348:   [CID=29f64488] Found Transaction
register13166648z9hG4bK34487872-8cf7-11e0-a33e-0800274986dc
09:03:38.348:   [CID=29f64488] <<< SIP/2.0 407 Proxy Authentication
Required LEN: 498 SRC: 204.11.192.37:5060 DST: XX.XX.XXX.XXX:5060 EXT:
[XX.XX.XXX.XXX] ENC: 0 PROT: udp
09:03:38.348: ^M
{^M
               [CID=29f64488] SIP/2.0 407 Proxy Authentication Required^M
               [CID=29f64488] v: SIP/2.0/UDP
XX.XX.XXX.XXX:5060;branch=z9hG4bK34487872-8cf7-11e0-a33e-0800274986dc;rport=5060^M
               [CID=29f64488] f:
<sip:1##########@callcentric.com;transport=udp>;tag=v0r8KQHmF054m^M
               [CID=29f64488] t:
<sip:1##########@callcentric.com;transport=udp>^M
               [CID=29f64488] i: 99b2a5a7-1e7c-4e65-b9ac-6fadbf4ca1c3^M
               [CID=29f64488] CSeq: 13166648 REGISTER^M
               [CID=29f64488] Proxy-Authenticate: Digest
realm="callcentric.com", domain="sip:callcentric.com",
nonce="edbfefbbc2ab6d684bae2b1de3fec2ea", opaque="", stale=TRUE,
algorithm=MD5^M
               [CID=29f64488] l: 0^M
};
09:03:38.349: Missing contact header in REGISTER response.
09:03:38.350:   [CID=29f64488] >>> SIP/2.0 407 Proxy Authentication
Required LEN: 526 SRC: XX.XX.XXX.XXX:5060 DST: XX.XX.XXX.XXX:5080 ENC:
0 PROT: udp
09:03:38.351: ^M
{^M
               [CID=29f64488] SIP/2.0 407 Proxy Authentication Required^M
               [CID=29f64488] f:
<sip:1##########@callcentric.com;transport=udp>;tag=v0r8KQHmF054m^M
               [CID=29f64488] t:
<sip:1##########@callcentric.com;transport=udp>^M
               [CID=29f64488] i: 99b2a5a7-1e7c-4e65-b9ac-6fadbf4ca1c3^M
               [CID=29f64488] CSeq: 13166648 REGISTER^M
               [CID=29f64488] Proxy-Authenticate: Digest
realm="callcentric.com", domain="sip:callcentric.com",
nonce="edbfefbbc2ab6d684bae2b1de3fec2ea", opaque="", stale=TRUE,
algorithm=MD5^M
               [CID=29f64488] l: 0^M





On Thu, Jun 2, 2011 at 5:57 PM, Steven Ayre <steveayre@gmail.com> wrote:
> Sounds like they're not sending back a valid response.
>
> It would be useful to see what's beeing sent back and forth. Change the
> logging level to debug and do 'sofia global siptrace on' to log all sip
> packets so we can see what's in them. It could be a problem with their
> server not sending the correct reply or it could be that your configuration
> isn't quite right to interop with their server and needs tweaking.
>
> -Steve
>
>
> On 2 June 2011 21:33, Roman Gelfand <rgelfand2@gmail.com> wrote:
>>
>> I am running into trouble trying to register to ITSP.  The log file shows
>> ...
>>
>> 2011-06-01 21:58:10.950068 [WARNING] sofia_reg.c:401 Timeout
>> Registering 1XXXXXXXXXX-callcentric.com
>> 2011-06-01 21:58:11.957417 [WARNING] sofia_reg.c:425
>> 1XXXXXXXXXX-callcentric.com Failed Registration [0], setting retry to
>> 30 seconds.
>> 2011-06-01 21:58:42.046331 [NOTICE] sofia_reg.c:367 Registering
>> 1XXXXXXXXXX-callcentric.com
>>
>> When challenged by 407 message from ITSP, I get
>>
>> 05:03:12.857: Missing contact header in REGISTER response.
>>
>> Does anyone know what is happening here? or pointers how to troubleshoot
>> this?
>>
>> Thanks in advance
>>
>> _______________________________________________
>> FreeSWITCH-users mailing list
>> FreeSWITCH-users@lists.freeswitch.org
>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
>> http://www.freeswitch.org
>
>
> _______________________________________________
> FreeSWITCH-users mailing list
> FreeSWITCH-users@lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org
>
>

_______________________________________________
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org