How can we help you today?
Start a new topic

Issue with multiple identities

Hi!


We are using Snom D345 phones at our office and I've just stumbled over an issue with a recently added identity. After adding the new identity it seems to conflict with one of the other identities that are already configured on the phone. Resulting in only one of those two connections being able to register and the other timing out. The only thing that I could find at the phones log was this:

May 21 10:49:54.505 [WARN ] SIP: transaction_timeout udp: 1000186 (32000)

May 21 10:49:54.505 [ERROR ] SIP: transport error: 1000186 -> Udp:192.168.0.32:5060

May 21 10:49:54.505 [ERROR ] SIP: request 1000186 destination invalid Udp:192.168.0.32:5060 313535383432383135303333383139-liprfh69r4bn

May 21 10:49:54.505 [ERROR ] SIP: transport error 1000186: generating fake 599

May 21 10:49:54.506 [ERROR ] SIP: Registrar 851002@gsipproxy.domain.com timed out

May 21 10:50:21.885 [FATAL ] SIP: sip_transport_state_cb context lost

May 21 10:50:21.885 [FATAL ] SIP: sip_transport_state_cb context lost


If I configure this identity on an independent phone it works just as intended.


Has anybody experienced this before?


Tobias,


What version of firmware? Are you hosting your own DNS that results in  gsipproxy.domain.com being resolved to 192.168.0.32?



May 21 10:49:54.505 [ERROR ] SIP: transport error: 1000186 -> Udp:192.168.0.32:5060

May 21 10:49:54.505 [ERROR ] SIP: request 1000186 destination invalid Udp:192.168.0.32:5060 313535383432383135303333383139-liprfh69r4bn

May 21 10:49:54.505 [ERROR ] SIP: transport error 1000186: generating fake 599

May 21 10:49:54.506 [ERROR ] SIP: Registrar 851002@gsipproxy.domain.com timed out


Is the IP address 192.168.0.32 within you Network's DHCP scope and routable to on your phone's Network?



Regards,


Snom Support

Hi Sean,

the phones are currently running firmware version 10.1.33.33 and yes everything is routable and resolvable from the phone's network as the line/identity is able to connect sometimes but then the other identity fails to connect. For example: 

- Reboot of the phone

- Identity 1 connected and Identity 2 timed out

- Reboot again

- Identity 2 connected and Identity 1 timed out


While it seems to be random which identity is able to connect.


Kind regards,

Tobias

Tobias,


Are both Identities registering to the same Registrar:  gsipproxy.domain.com >  192.168.0.32:5060 

Sean,


no, actually they are registering to two completely independent servers.

Tobias,



Are you hosting your own DNS on your local LAN? Does gsipproxy.domain.com resolve to the private IP address 192.168.0.32? Is  192.168.0.32 your Firewall? 



Regards,



Snom Support

Yes we are hosting an own DNS but gsipproxy.domain.com is resolved by an external forwarder (that is managed by the team that hosts this registrar) and it resolves to the address 192.168.0.32 which isn't our firewall. 

Again, when the "gsipproxy.domain.com" identity is the only identity that is configured on exactly the same phone it connects and works as desired so I wouldn't assume a DNS issue here. 

Tobias,


I created a ticket for this issue.



Regards,



Snom Support

Login or Signup to post a comment