30.10.2009 23:38:04
 Pierre Posts: 5
|
When I use an IP address for the SIP domain or just a hostname, I get a 502 error. Things are OK with a FQDN Those 3 options are accepted in the manager when I push the accept button. Other domains get replaced by the local address when pushing the accept button.
DNS is fine, I can ping & resolve IP address, hostname and fqdn.
Here are snips from the ini and log files Sip client and proxy are on the same PC. The register messages in both cases look identical and the IP address does not appear in them.
Pierre
******************************************* [Server] ListenIP=172.16.0.88 UseEA=0 EAddress= ListenPort=5060 SIPDomain=172.16.0.88 Logging=3 UPnPUpdatePd=3 B2BUA43xx=0 ENUMLookupEnabled=0 GUIPort=2035 StartupMode=Automatic
10/30/2009 2:55:41 PM - TekSIP Service 2.2.0.0 (Revision 0) is being started on : 172.16.0.88:5060 [Accounting disabled]
10/30/2009 2:55:47 PM - TekSIP Service is started on : 172.16.0.88:5060
SIP req. from : 172.16.0.88:30884 (UDP) - 10/30/2009 2:56:00 PM
REGISTER sip:phumbletlapxp.wirelessworld.airvananet.com SIP/2.0 [Via] = SIP/2.0/UDP 127.0.0.1:30884;branch=z9hG4bK-d8754z-902818537225210d-1---d8754z-;rport [Max-Forwards] = 70 [Contact] = <sip:phumblet@127.0.0.1:30884;rinstance=0e82d4b1fc5abb1f> [To] = "phumblet"<sip:phumblet@phumbletlapxp.wirelessworld.airvananet.com> [From] = "phumblet"<sip:phumblet@phumbletlapxp.wirelessworld.airvananet.com>;tag=6a1b5c63 [Call-ID] = ZDg1YzMwMTU2YTBmNzEzNWYxOGM5OWIxYTVmMjcwZDk. [CSeq] = 1 REGISTER [Expires] = 3600 [Allow] = INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO [User-Agent] = X-Lite release 1103k stamp 53621 [Content-Length] = 0
SIP req. to : 172.16.0.88:30884 (UDP) - 10/30/2009 2:56:00 PM
SIP/2.0 502 Unknown host or domain Via: SIP/2.0/UDP 127.0.0.1:30884;branch=z9hG4bK-d8754z-902818537225210d-1---d8754z-;received=172.16.0.88;rport=30884
******************************************* [Server] ListenIP=172.16.0.88 UseEA=0 EAddress= ListenPort=5060 SIPDomain=phumbletlapxp.wirelessworld.airvananet.com Logging=3 UPnPUpdatePd=3 B2BUA43xx=0 ENUMLookupEnabled=0 GUIPort=2035 StartupMode=Automatic
10/30/2009 3:04:45 PM - TekSIP Service 2.2.0.0 (Revision 0) is being started on : 172.16.0.88:5060 [Accounting disabled]
10/30/2009 3:04:50 PM - TekSIP Service is started on : 172.16.0.88:5060
SIP req. from : 172.16.0.88:7912 (UDP) - 10/30/2009 3:05:33 PM
REGISTER sip:phumbletlapxp.wirelessworld.airvananet.com SIP/2.0 [Via] = SIP/2.0/UDP 127.0.0.1:7912;branch=z9hG4bK-d8754z-8d24b61cc57cd500-1---d8754z-;rport [Max-Forwards] = 70 [Contact] = <sip:phumblet@127.0.0.1:7912;rinstance=28eaff9566b116da> [To] = "phumblet"<sip:phumblet@phumbletlapxp.wirelessworld.airvananet.com> [From] = "phumblet"<sip:phumblet@phumbletlapxp.wirelessworld.airvananet.com>;tag=443a0d0c [Call-ID] = ODY3M2E4MDJkMzNhNjdhMTEwYzFjODc3OThmOTk3NDE. [CSeq] = 1 REGISTER [Expires] = 3600 [Allow] = INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO [User-Agent] = X-Lite release 1103k stamp 53621 [Content-Length] = 0
SIP req. to : 172.16.0.88:7912 (UDP) - 10/30/2009 3:05:33 PM
SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 127.0.0.1:7912;branch=z9hG4bK-d8754z-8d24b61cc57cd500-1---d8754z-;received=172.16.0.88;rport=7912
|
|
0
• permalink
|
31.10.2009 00:34:54
 Admin Administrator Posts: 254
|
Hi,
Please make sure that phumbletlapxp.wirelessworld.airvananet.com resolves to 172.16.0.88
|
|
0
• permalink
|
31.10.2009 00:38:08
 Pierre Posts: 5
|
It does, of course
~ ping -n 1 PHUMBLETLAPXP.wirelessworld.airvananet.com Pinging PHUMBLETLAPXP.wirelessworld.airvananet.com [172.16.0.88] with 32 bytes of data: Reply from 172.16.0.88: bytes=32 time<1ms TTL=128
and also in the other direction: ~ ping -a 172.16.0.88 Pinging PHUMBLETLAPXP.wirelessworld.airvananet.com [172.16.0.88] with 32 bytes of data:
Pierre
|
|
0
• permalink
|
31.10.2009 01:10:40
 Pierre Posts: 5
|
Also the fact that the manager accepts an IP address, the hostname and the fqdn, but no other form (for example the fqdn without the .com or google.com), indicates that it can resolve them to a local interface. I just ran a script in the service environment to make sure there was nothing special there, and everything looked OK.
Pierre
|
|
0
• permalink
|