Jump to content

SnomOne receiving 486 from TG784n device?


voipguy
 Share

Recommended Posts

Hi,

 

Hoping someone can help me with this or give me some ideas of what is causing this.

 

Using snomone ver 4.5 the voip device is a Thomson TG784n firmware ver 8.43

 

This is a random problem. When you call the TG784N voip number from your cell or landline the TG784N will ring normally....but sometimes when I call the TG784n it goes straight to voicemail? The TG784n doesn't even ring - the person that has the TG784n doesn't even know somebody just tried to call them. I can see the TG784n is registered to my someone PBX. I know the TG784n is getting the call because I can see in the TG784n logs it is receiving the sip invite from my someone PBX. I did a wireshark trace on my PBX and I can see the TG784n did send back a 486 busy - but why? The TG784n was not in a call.

 

This is 100% not a NAT issue.

 

Here is the log from my TG784n for a failed call - goes straight to voicemail - because TG784n sends 486 to pbx:

 

Info Jul 22 12:43:02 VOIP: [784n] [4165551234] [FXS1] INVITE - SIP message received
Info Jul 22 12:43:02 VOIP: [784n] [4165551234] [FXS1] 401 Unauthorized - SIP message sent
Info Jul 22 12:43:03 VOIP: [784n] [4165551234] [FXS1] ACK - SIP message received
Info Jul 22 12:43:03 VOIP: [784n] [4165551234] [FXS1] INVITE - SIP message received
Info Jul 22 12:43:04 FIREWALL event (1 of 3): created rules
Info Jul 22 12:43:05 VOIP: [784n] [4165551234] [FXS1] 180 Ringing - SIP message sent
Info Jul 22 12:43:07 VOIP: [784n] [4165551234] [FXS1] NOTIFY - SIP message received
Info Jul 22 12:43:07 VOIP: [784n] [4165551234] [FXS1] 401 Unauthorized - SIP message sent
Info Jul 22 12:43:07 VOIP: [784n] [4165551234] [FXS1] NOTIFY - SIP message received
Info Jul 22 12:43:07 VOIP: [784n] [4165551234] [FXS1] 200 OK - SIP message sent
Info Jul 22 12:43:27 VOIP: [784n] [4165551234] [FXS1] REGISTER - SIP message sent
Info Jul 22 12:43:27 VOIP: [784n] [4165551234] [FXS1] 200 Ok - SIP message received

 

Here is log from snomone - same call:

 

[5] 2013/07/22 12:44:53: Identify trunk (IP address and DID match) 98
[9] 2013/07/22 12:44:53: Resolve 2473446: aaaa udp VoipProxyIP 5060
[9] 2013/07/22 12:44:53: Resolve 2473446: a udp VoipProxyIP 5060
[9] 2013/07/22 12:44:53: Resolve 2473446: udp VoipProxyIP 5060
[6] 2013/07/22 12:44:53: Call-leg 241: Sending RTP for 17566fdc17@VoipProxyIP to (ip removed):6210, codec not set yet
[8] 2013/07/22 12:44:53: Incoming call: Request URI sip:4165551234@snomoneipaddress:5060, To is <sip:4165551234@snomoneipaddress:5060>
[5] 2013/07/22 12:44:53: Domain trunk 507265@snomonedomainname sends call to 4165551234 in domain snomonedomainname
[8] 2013/07/22 12:44:53: Set the To domain based on To user 4165551234@snomonedomainname
[9] 2013/07/22 12:44:53: Resolve 2473447: url sip:4165551234@ipaddress:5060
[9] 2013/07/22 12:44:53: Resolve 2473447: udp ipaddress 5060
[8] 2013/07/22 12:44:54: Answer challenge with username 4165551234
[9] 2013/07/22 12:44:54: Resolve 2473448: udp ipaddress 5060 udp:1
[9] 2013/07/22 12:44:54: Resolve 2473449: udp ipaddress 5060 udp:1
[9] 2013/07/22 12:44:54: Message repetition, packet dropped
[7] 2013/07/22 12:44:54: Call f15f0326@pbx: Clear last INVITE
[9] 2013/07/22 12:44:54: Resolve 2473450: url sip:4165551234@ipaddress:5060
[9] 2013/07/22 12:44:54: Resolve 2473450: udp ipaddress 5060
[5] 2013/07/22 12:44:54: INVITE Response 486 Busy Here: Terminate f15f0326@pbx
[6] 2013/07/22 12:44:54: Call-leg 241: Codec g729/8000 is chosen for call id 17566fdc17@VoipProxyIP
[9] 2013/07/22 12:44:54: Resolve 2473451: aaaa udp VoipProxyIP 5060
[9] 2013/07/22 12:44:54: Resolve 2473451: a udp VoipProxyIP 5060
[9] 2013/07/22 12:44:54: Resolve 2473451: udp VoipProxyIP 5060
[8] 2013/07/22 12:44:54: Hangup: Call 242 not found
[5] 2013/07/22 12:44:54: set codec: codec g729/8000 is set to call-leg 241

 

 

When the TG784n sends back " 401 Unauthorized - SIP message sent" my snomone pbx logs this "Answer challenge with username 4165551234"

 

There must be a setting inside the TG784n that I can switch off that snomone doesn't like or maybe a setting in snomone that has to be changed?

 

 

Things/patterns I've noticed:

 

1. Why does the TG784n send a 401 when snomone sends invite to it for a call? Yes snomone answer the nonce security question with the right answer and the call continues but why does the TG784n send the 401 in the first place? Even on a successful call where the TG784n phone does ring this initial 401 happens.

 

On my Speedtouch 780wl firmware ver 7.4 which is the modem model before the 784N modem it doesn't send a sip 401 message back to the pbx and I don't see NOTIFY messages coming from PBX to TG784n.

 

2. When the call is successful on the TG784n I still see the sip 401 but I don't see the "NOTIFY - SIP message received" - the call works and the TG784n rings? It's almost like the TG784n is saying to snomone I'm busy 486 so I can't deal with your NOTIFY message that you just sent me, were in the middle of trying to setup a call here.

 

3. If I turn the voicemail box off in snomone and I dial the TG784n and the call fails I hear a busy signal because the TG784n sent a 486, when mailbox is enabled I don't hear busy signal and it goes straight to voicemail - I know this is how it's suppose to work when snomone gets a 486 back but why are we getting a 486 back from the TG784n?

 

 

Any help would be appreciated. I've been working on this problem for over a week, I must have made a 100 test changes.

 

Thanks

 

 

 

 

 

 

 

 

 

 

 

Link to comment
Share on other sites

At first glance it sounds like a bug. Is there any newer software available?

 

A possible workaround could be to use the trunk failover feature of the PBX. When the TG784n fails, just try again! Because the PBX is a B2BUA, it will have a separate Call-ID, which might fool the gateway and have it process the new request as separate request. That should lower the probability of this behavior significantly and if it is still too high, maybe add a third one -_- . It is definitively a dirty workaround, but one that actually might do the job.

Link to comment
Share on other sites

Hi Snom ONE,

 

Thanks for replying. I can't do the work around, I need to find out why it's happening - it's just a setting somewhere among the 200 plus settings in the TG784n.

 

Can you tell me why snomone sends a notify msg to the TG784n ?

 

It seems for all the failed calls it's when snomone sends the notify msg.

 

Thanks,

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...