VoIP Mailing List Archives

[dujinfang at gmail.com]

Hi,

I'm on version 13524, call from zoiper is ok, but when call zoiper, it keep rejecting calls, anyone can help? I'm seems always not the right time join in IRC


http://pastebin.freeswitch.org/9383




Thanks.

[brian at freeswitch.org]

To: <"user" <sip:639@192.168.1.27:5070;rinstance=59e15734a404c038>

Can you reproduce this or let us in your box to look at it... someone else reported this but I have yet to be able to reproduce it.


/b

On Jun 15, 2009, at 2:41 AM, seven wrote:

[dujinfang at gmail.com]

Yes, I can reproduce this, FYI, I have another box runs 13272 with the same zoiper without any problem.

You can login to our box, I will find you on IRC.

On Jun 15, 2009, at 10:21 PM, Brian West wrote:

[dujinfang at gmail.com]

Brain,


You are not on irc right now and it is midnight so I'm gona to sleep.


however when I try to reproduce that I found it event didn't get to Zoiper. I use the same Zoiper login to two boxes at the same time, version 13272 is ok while the other isn't. I noticed there is an extra line on the log of version 13524:


version 13272:


2009-06-15 22:54:14 [DEBUG] mod_sofia.c:83 sofia_on_init() sofia/internal/839 SOFIA INIT
2009-06-15 22:54:14 [DEBUG] mod_sofia.c:111 sofia_on_init() (sofia/internal/839) State Change CS_INIT -> CS_ROUTING




version 13524:


2009-06-15 22:50:46 [DEBUG] mod_sofia.c:83 sofia_on_init() sofia/internal/637 SOFIA INIT
2009-06-15 22:50:46 [DEBUG] sofia_glue.c:1599 sofia_glue_do_invite() [url=sip:637@192.168.1.27:5070]sip:637@192.168.1.27:5070[/url]%3 Setting proxy route to sofia/internal/637
2009-06-15 22:50:46 [DEBUG] mod_sofia.c:111 sofia_on_init() (sofia/internal/637) State Change CS_INIT -> CS_ROUTING



And here is a more detailed paste:
http://pastebin.freeswitch.org/9386


Thank you taking time for this. If you need more detail I'd like to collect and can open ssh for further debug.


7.


On Jun 15, 2009, at 10:21 PM, Brian West wrote:

[dujinfang at gmail.com]

Hi, the difference is the Contact where the "%3B" should be ";" . Is it configurable or a bug?


13272:


Call-ID: OTg4NmRlNzY5OThmNzgwM2E3ZmRkYzVhNjVmODMyYjA.
User: 839@192.168.1.15 (839@192.168.1.15)
Contact: "user" <[url=sip:839@192.168.1.27:5070;rinstance=0f6c69c813f97b49;transport=UDP]sip:839@192.168.1.27:5070;rinstance=0f6c69c813f97b49;transport=UDP[/url]>
Agent: Zoiper rev.3065
Status: Registered(UDP)(unknown) EXP(2009-06-16 00:54:12)
Host: pbx3.veecue.com
IP: 192.168.1.27
Port: 5070
Auth-User: 839
Auth-Realm: 192.168.1.15



13524:


Call-ID: NWJhYWY0YjJmMzdlNWQ4MWIwZjc2NGM5NjQzZDU3NTg.
User: 637@192.168.1.16 (637@192.168.1.16)
Contact: "user" <[url=sip:637@192.168.1.27:5070;rinstance=cb5d34523fca3400;transport=UDP;fs_nat=yes;fs_path=sip%3A637%40192.168.1.27%3A5070%3Brinstance%3Dcb5d34523fca3400%3Btransport%3DUDP]sip:637@192.168.1.27:5070;rinstance=cb5d34523fca3400;transport=UDP;fs_nat=yes;fs_path=sip%3A637%40192.168.1.27%3A5070%3Brinstance%3Dcb5d34523fca3400%3Btransport%3DUDP[/url]>
Agent: Zoiper rev.3065
Status: Registered(UDP-NAT)(unknown) EXP(2009-06-16 01:42:56)
Host: pbx1.veecue.com
IP: 192.168.1.27
Port: 5070
Auth-User: 637
Auth-Realm: 192.168.1.16










On Jun 15, 2009, at 10:21 PM, Brian West wrote:

[dujinfang at gmail.com]

Hi brain,

Are you still looking into this?


I think it must be some error when it register, I manually changed the contract str in the registration db, immediately it works. After re-register, stop work again.


Should I report this to jira?


sqlite> select contact from sip_registrations where contact like '%637%';
contact
"user" <[url=sip:637@192.168.1.27:5070;rinstance=8df223525ea557b0;transport=UDP;fs_nat=yes;fs_path=sip%3A637%40192.168.1.27%3A5070%3Brinstance%3D8df223525ea557b0%3Btransport%3DUDP]sip:637@192.168.1.27:5070;rinstance=8df223525ea557b0;transport=UDP;fs_nat=yes;fs_path=sip%3A637%40192.168.1.27%3A5070%3Brinstance%3D8df223525ea557b0%3Btransport%3DUDP[/url]>


sqlite> update sip_registrations set contact='"user" <[url=sip:637@192.168.1.27:5070;rinstance=8df223525ea557b0;transport=UDP;fs_nat=yes;fs_path=sip%3A637%40192.168.1.27%3A5070]sip:637@192.168.1.27:5070;rinstance=8df223525ea557b0;transport=UDP;fs_nat=yes;fs_path=sip%3A637%40192.168.1.27%3A5070[/url]>' where contact like '%637%';








On Jun 15, 2009, at 10:21 PM, Brian West wrote:

[mike at jerris.com]

If you can catch brian or me on irc can you provide remote access to this box and we should be able to fix this pretty quick


Mike

On Jun 16, 2009, at 5:20 AM, seven <dujinfang@gmail.com (dujinfang@gmail.com)> wrote:

[dujinfang at gmail.com]

Almost caught you on IRC Mike.

Our server is in a NAT'd network and all agents registered in the same LAN. I can remotely register by using the public IP and the contact string is right.


Call-ID: ZTZhMGJkZTE0NzNjZTlmZTkxYmU5NWRlZTU1MzJlYTE.
User: 637@192.168.1.16 (637@192.168.1.16)
Contact: "user" <[url=sip:637@210.73.8.180:5090;rinstance=9fc589bbc407518f]sip:637@210.73.8.180:5090;rinstance=9fc589bbc407518f[/url]>
Agent: Zoiper rev.1809



So it's like only happens on our LAN and where there's a fs_path present.


Just curious, why agents registered on a local LAN has param fs_nat=yes; (default internal profile, port 5060) ?


Seems our time doesn't match, I'm generally available in office 9:00AM-6:00PM GMT+0800, so will try to catch you tomorrow.


Thank you.

On Jun 16, 2009, at 7:35 PM, Michael Jerris wrote:

[brian at freeswitch.org]

Ok i'll have to se what I can do about reproducing this issue now that I have more info on how its happening.

/b

On Jun 16, 2009, at 7:40 AM, dujinfang wrote:

[Prometheus001 at gmx.net]

May this help also: I just tried current Zoiper with TLS. Outbound is
working, inbound not.

Zoiper registeres with the following contact info:
"7233213"
<sip:7233213@217.xx.xx.xxx:51989;rinstance=85925cbf0ecc0ab4;transport=TLS>
When a call comes in, Zoiper rings once and then hangs up. It shows
"service or option not implemented" in the Zoiper log.

My snom phones with the same parameters in the same network (they are
all nated) register differently
"723323"
<sip:723323@192.168.178.143:2059;transport=tls;line=4xbyd8h3;fs_nat=yes;fs_path=sip%3A723323%40217.xx.xx.xxx%3A2059%3Btransport%3Dtls%3Bline%3D4xbyd8h3>

My FS logs show for an incoming call to Zoiper:
7233213@217.xx.xx.xxx:51989;rinstance=85925cbf0ecc0ab4;transport=TLS)
Running State Change CS_CONSUME_MEDIA
2009-06-16 14:50:16.336881 [DEBUG] switch_core_state_machine.c:502
(sofia/internal/sip:7233213@217.xx.xx.xxx:51989;rinstance=85925cbf0ecc0ab4;transport=TLS)
State CONSUME_MEDIA
2009-06-16 14:50:16.336881 [DEBUG] sofia.c:3100 Channel
sofia/internal/sip:7233213@217.xx.xx.xxx:51989;rinstance=85925cbf0ecc0ab4;transport=TLS
entering state [calling][0]
2009-06-16 14:50:16.340881 [DEBUG] sofia.c:3100 Channel
sofia/internal/sip:7233213@217.xx.xx.xxx:51989;rinstance=85925cbf0ecc0ab4;transport=TLS
entering state [terminated][415]
2009-06-16 14:50:16.340881 [NOTICE] sofia.c:3660 Hangup
sofia/internal/sip:7233213@217.xx.xx.xxx:51989;rinstance=85925cbf0ecc0ab4;transport=TLS
[CS_CONSUME_MEDIA] [SERVICE_NOT_IMPLEMENTED]

Its seems that something with the codecs fails here, although I have
enabled all codecs in Zoiper and FS offers alaw.

Best regards
Peter

Brian West schrieb:

[dujinfang at gmail.com]

What's wrong of the contact string? 639(snom) works but 637(zoiper) doesn't.


"user" <[url=sip:637@192.168.1.27:5070;rinstance=e1e47e9a22f3e450;transport=UDP;fs_nat=yes;fs_path=sip%3A637%40192.168.1.27%3A5070%3Brinstance%3De1e47e9a22f3e450%3Btransport%3DUDP]sip:637@192.168.1.27:5070;rinstance=e1e47e9a22f3e450;transport=UDP;fs_nat=yes;fs_path=sip%3A637%40192.168.1.27%3A5070%3Brinstance%3De1e47e9a22f3e450%3Btransport%3DUDP[/url]>


"seven" <[url=sip:639@192.168.1.21:2051;line=298293g2;fs_nat=yes;fs_path=sip%3A639%40192.168.1.21%3A2051%3Bline%3D298293g2]sip:639@192.168.1.21:2051;line=298293g2;fs_nat=yes;fs_path=sip%3A639%40192.168.1.21%3A2051%3Bline%3D298293g2[/url]>



On Jun 16, 2009, at 8:43 PM, Brian West wrote:

[brian at freeswitch.org]

I need sip traces... also can you guys register to my dev box? dev.bkw.org with default user/pass try 1009 thru 1015 please.

/b

On Jun 16, 2009, at 8:17 AM, Seven Du wrote:

[mike at jerris.com]

This issue is now fixed in svn. Thanks Seven for access to your box to troubleshoot.

Mike

On Jun 16, 2009, at 9:17 AM, Seven Du wrote: