[OpenSIPS-Users] TCP CONNECT ERROR;
Premalatha Kuppan
premalatha at ngintech.com
Wed Jul 28 07:46:50 CEST 2010
Sorry forgot to attach the cfg file..attached now.
On Wed, Jul 28, 2010 at 11:15 AM, Premalatha Kuppan <premalatha at ngintech.com
> wrote:
> Still call fails to TC P enabled clients.
>
> Please find my config file attached. I dono where iam doing mistake
> :(..please help
>
>
> Jul 28 01:21:43 204548-4 /usr/local/sbin/opensips[21528]: REGISTER MESSAGE
> Jul 28 01:21:43 204548-4 /usr/local/sbin/opensips[21528]: REGISTER sips:PUBLIC
> IP <http://204.12.57.221:5061>SIP/2. From: <
> sip:588aa6e4-2af1-4fc0-ad67-6e5c16681e771000 at 10.11.11.181<sip%3A588aa6e4-2af1-4fc0-ad67-6e5c16681e771000 at 10.11.11.181>>;tag=14097453-6b37-4f1d-bb14-43
> Authorization: Digest username="4081112222", realm="PUBLIC IP",
> nonce="4c4fbe85000000013046f7331a315fdc29e6f14851cbedd9", uri="sips:PUBLIC
> IP:5061 <http://204.12.57.221:5061>",
> response="64375192e261bc5f3213bc6f56 ontent-Length: 0
> Jul 28 01:21:43 204548-4 /usr/local/sbin/opensips[21528]: ---- contact
> expire=<null> ; header expire =300; contact
> uri=sip:588aa6e4-2af1-4fc0-ad67-6e5c16681e771000 at 209.242.149.98:57086;transport=tls
>
> Jul 28 01:21:43 204548-4 /usr/local/sbin/opensips[21528]: ----This is
> register, parsing values - 588aa6e4-2af1-4fc0-ad67-6e5c16681e771000;
> sip:588aa6e4-2af1-4fc0-ad67-6e5c16681e771000 at 10.11.11.181<sip%3A588aa6e4-2af1-4fc0-ad67-6e5c16681e771000 at 10.11.11.181>;
>
> Jul 28 01:21:43 204548-4 /usr/local/sbin/opensips[21528]:
> NORMAL-REGISTRATION
> Jul 28 01:21:43 204548-4 /usr/local/sbin/opensips[21528]: CLIENT BEHIND NAT
>
> Jul 28 01:21:43 204548-4 /usr/local/sbin/opensips[21528]: contact before
> update <<sip:588aa6e4-2af1-4fc0-ad67-6e5c16681e771000 at 209.242.149.98:47043;transport=tls>>
>
> Jul 28 01:21:43 204548-4 /usr/local/sbin/opensips[21528]: via before update
> <SIP/2.0/TLS 10.11.11.181:57086
> ;rport;branch=z9hG4bKPj48764d96-c980-4584-aba4-2af5c6273165>
> Jul 28 01:21:43 204548-4 /usr/local/sbin/opensips[21528]: REGISTER MESSAGE
> Jul 28 01:21:43 204548-4 /usr/local/sbin/opensips[21528]: REGISTER sips:
> 204.12.57.221:5061 SIP/2. From: <
> sip:588aa6e4-2af1-4fc0-ad67-6e5c16681e771000 at 10.11.11.181<sip%3A588aa6e4-2af1-4fc0-ad67-6e5c16681e771000 at 10.11.11.181>>;tag=9428c49e-e3bb-4241-b3da-8e
> ontent-Length: 0a6e4-2af1-4fc0-ad67-6e5c16681e771000 at 209.242.149.98:47043
> ;transport=tls>
> Jul 28 01:21:44 204548-4 /usr/local/sbin/opensips[21528]: REGISTER MESSAGE
> Jul 28 01:21:44 204548-4 /usr/local/sbin/opensips[21528]: REGISTER sips:PUBLIC
> IP:5061 <http://204.12.57.221:5061> SIP/2. From: <
> sip:588aa6e4-2af1-4fc0-ad67-6e5c16681e771000 at 10.11.11.181<sip%3A588aa6e4-2af1-4fc0-ad67-6e5c16681e771000 at 10.11.11.181>>;tag=12a8089f-2955-480f-affb-6f
> ontent-Length: 0a6e4-2af1-4fc0-ad67-6e5c16681e771000 at 209.242.149.98:57086
> ;transport=tls>
> Jul 28 01:21:44 204548-4 /usr/local/sbin/opensips[21528]: REGISTER MESSAGE
> Jul 28 01:21:44 204548-4 /usr/local/sbin/opensips[21528]: REGISTER sips:
> PUBLIC:IP <http://204.12.57.221:5061> SIP/2. From: <
> sip:588aa6e4-2af1-4fc0-ad67-6e5c16681e771000 at 10.11.11.181<sip%3A588aa6e4-2af1-4fc0-ad67-6e5c16681e771000 at 10.11.11.181>>;tag=9428c49e-e3bb-4241-b3da-8e
> Authorization: Digest username="4081112222", realm="PUBLIC IP",
> nonce="4c4fbe85000000025275d997ab9c99b5ab5e0eac036575d0", uri="sips:PUBLIC
> IP <http://204.12.57.221:5061>", response="a81e038b357fb069199bb83f32
> ontent-Length: 0
> Jul 28 01:21:44 204548-4 /usr/local/sbin/opensips[21528]: ---- contact
> expire=<null> ; header expire =0; contact
> uri=sip:588aa6e4-2af1-4fc0-ad67-6e5c16681e771000 at 209.242.149.98:47043;transport=tls
>
> Jul 28 01:21:44 204548-4 /usr/local/sbin/opensips[21528]: This is
> de-registration
> Jul 28 01:21:44 204548-4 /usr/local/sbin/opensips[21528]: ----De-register
> DONE - 588aa6e4-2af1-4fc0-ad67-6e5c16681e771000
> Jul 28 01:21:44 204548-4 /usr/local/sbin/opensips[21528]: REGISTER MESSAGE
> Jul 28 01:21:44 204548-4 /usr/local/sbin/opensips[21528]: REGISTER sips:PUBLIC
> IP:5061 <http://204.12.57.221:5061> SIP/2. From: <
> sip:588aa6e4-2af1-4fc0-ad67-6e5c16681e771000 at 10.11.11.181<sip%3A588aa6e4-2af1-4fc0-ad67-6e5c16681e771000 at 10.11.11.181>>;tag=12a8089f-2955-480f-affb-6f
> Authorization: Digest username="4081112222", realm="PUBLIC IP",
> nonce="4c4fbe86000000034f58d23302892e98458c1907863d4951", uri="sips:
> 204.12.57.221:5061", response="df102121f9df50a2e205cd144a ontent-Length:
> 0
> Jul 28 01:21:44 204548-4 /usr/local/sbin/opensips[21528]: ---- contact
> expire=<null> ; header expire =300; contact
> uri=sip:588aa6e4-2af1-4fc0-ad67-6e5c16681e771000 at 209.242.149.98:57086;transport=tls
>
> Jul 28 01:21:44 204548-4 /usr/local/sbin/opensips[21528]: ----This is
> register, parsing values - 588aa6e4-2af1-4fc0-ad67-6e5c16681e771000;
> sip:588aa6e4-2af1-4fc0-ad67-6e5c16681e771000 at 10.11.11.181<sip%3A588aa6e4-2af1-4fc0-ad67-6e5c16681e771000 at 10.11.11.181>;
>
> Jul 28 01:21:44 204548-4 /usr/local/sbin/opensips[21528]:
> NORMAL-REGISTRATION
> Jul 28 01:23:48 204548-4 /usr/local/sbin/opensips[21523]: new branch at
> sip:123450 at 209.242.149.98:1025;transport=TCP
> Jul 28 01:23:49 204548-4 /usr/local/sbin/opensips[21523]:
> ERROR:core:tcp_blocking_connect: timeout 1 s elapsed from 1 s
> Jul 28 01:23:49 204548-4 /usr/local/sbin/opensips[21523]:
> ERROR:core:tcpconn_connect: tcp_blocking_connect failed
> Jul 28 01:23:49 204548-4 /usr/local/sbin/opensips[21523]:
> ERROR:core:tcp_send: connect failed
> Jul 28 01:23:49 204548-4 /usr/local/sbin/opensips[21523]:
> ERROR:tm:msg_send: tcp_send failed
> Jul 28 01:23:49 204548-4 /usr/local/sbin/opensips[21523]:
> ERROR:tm:t_forward_nonack: sending request failed
> Jul 28 01:23:50 204548-4 /usr/local/sbin/opensips[21523]: ACC: call missed:
> timestamp=1280294630;method=INVITE;from_tag=588744142;to_tag=;call_id=
> 77A4FDFA-2F28-69A0-4508-62C20778D044 at 122.183.196.26;code=477;reason=Request
> Failure
>
> On Tue, Jul 27, 2010 at 3:33 PM, Premalatha Kuppan <
> premalatha at ngintech.com> wrote:
>
>> Thanks. Sorry for frequent questions.
>>
>> The set-up is already up and running for UDP; i have problem for TCP and
>> TLS. Thats the reason looking for quick remedy.
>>
>> I dono which one is quick and easily done; protocol switching or transfer
>> call from asterisk and then opensips to hanlde it further between callee and
>> called.
>>
>> Please give your expertise advice.
>>
>>
>> On Tue, Jul 27, 2010 at 3:17 PM, Anca Vamanu <anca at opensips.org> wrote:
>>
>>> On 07/27/2010 12:29 PM, Premalatha Kuppan wrote:
>>> > while compiling , i'm getting error, :(
>>> >
>>> > b2b_logic.c:32:27: error: libxml/parser.h: No such file or directory
>>> > In file included from records.h:36,
>>> > from b2b_logic.c:41:
>>> > b2b_logic.h:56: error: expected specifier-qualifier-list before
>>> > ‘xmlNodePtr’
>>> > b2b_logic.h:78: error: expected specifier-qualifier-list before
>>> > ‘xmlDocPtr’
>>> >
>>> >
>>> > Between, I see Opensips as a proxy can do translation of tcp to UDP.
>>> > How can i achieve this for my requirement.
>>> >
>>> > Any idea ?
>>>
>>> You need to install libxml2-dev ( it is also written in the
>>> documentation).
>>> Yes, OpenSIPS does protocol switching.
>>>
>>> Regards,
>>>
>>> --
>>> Anca Vamanu
>>> www.voice-system.ro
>>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.opensips.org/pipermail/users/attachments/20100728/e225dec9/attachment-0001.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: opensips.cfg
Type: application/octet-stream
Size: 18952 bytes
Desc: not available
Url : http://lists.opensips.org/pipermail/users/attachments/20100728/e225dec9/attachment-0001.obj
More information about the Users
mailing list