I have a problem with siproxd - or at least I think. Outbound calls work perfect, but as soon as I get an inbound call, the hardphone (Snom) seems to have a problem with the SIP address. The call is delivered as username@localproxy. The localproxy seems not to be known on the Snom phone and the call is rejected.
Any ideas? Thx for your help
reto
Log file from Snom phone:
Received from udp:192.168.1.1:5060 at 1/3/2011 19:07:18:647 (1213 bytes):
The first question is where does this (wrong?) "localproxy" originate.
A few questions to look at:
- Do you use a Registrar?
- Is your SNOM properly configured (Registers with an external SIP Registrar)
- If you use an external registrar I would expect a proper domain to be present and not "localproxy"
- Are there any other "funny" SIP proxies involved?
I assume that you have only one *local* phone (your SNOM) connected to siproxd.
If all fails, you can try to add a default target in the siproxd configuration. You can specify the full SIP URI that your SNOM accepts.
######################################################################
plugin_defaulttarget_log = 1
# target must be a full SIP URI with the syntax
# sip:user@host
plugin_defaulttarget_target = sip:internal@dddd:port
Best regards,
/Thomas
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As to your questions:
1) I do use a registrar
2) The SNOM registers properly with the registrar (at least I think - outbound calls are possible)
3) There is a proper domain present at the siproxd… it seems as if siproxd replaces the proper domain name with the localproxy
4) No other SIP proxies are involved
I do have several local phones (3 to be precise) and I'm also using 2 different accounts. All three phones (all SNOM) have the same issue/problem.
Are there situations where siproxd (I use it as plugin on pfSense) addes the localproxy as domain?
Best regards
reto
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Could you make a debug log file (debuglevel=-1) from siproxd beginning at starting siproxd, including the registration sequence of your phone at the provider and such an incoming call that fails. I will have a look what is going on and where the localproxy is coming from.
What I can say, there is no hardcoded way that siproxd does substitute a hostname by localproxy. It must be present somewhere outside siproxd (the hostname of the machine running siproxd comes to mind - ?).
Personally I'm using siproxd to masquerady several SIP accounts, also including a SNOM phone as local UA and have not seen such problems, so I'm confident that it is possible to get this working.
Please send the logfile to my SF email account and don't attach it here.
Best regards,
/Thomas
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi all
I have a problem with siproxd - or at least I think. Outbound calls work perfect, but as soon as I get an inbound call, the hardphone (Snom) seems to have a problem with the SIP address. The call is delivered as username@localproxy. The localproxy seems not to be known on the Snom phone and the call is rejected.
Any ideas? Thx for your help
reto
Log file from Snom phone:
Received from udp:192.168.1.1:5060 at 1/3/2011 19:07:18:647 (1213 bytes):
INVITE sip:username@192.168.1.191:3072 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.1:5060;branch=z9hG4bK6ae294d9626a9d6fb5aa2b3c5e4aaf7f
Via: SIP/2.0/UDP 212.55.198.132;branch=z9hG4bK0e07.09bd32f3.0
Via: SIP/2.0/UDP 212.55.198.131:5061;branch=z9hG4bK117233d9;rport=5061
Record-Route: <sip:siproxd@192.168.1.1:5060;lr>
Record-Route: <sip:212.55.198.132;lr=on;ftag=as130ba29e>
From: "0763551620" <sip:0763551620@212.55.198.131:5061>;tag=as130ba29e
To: <sip:username@localproxy>
Call-ID: 0bcf11697969070b5b264e535d5d4626@212.55.198.131
CSeq: 102 INVITE
Contact: <sip:0763551620@212.55.198.131:5061>
Content-Type: application/sdp
Allow: INVITE
Allow: ACK
Allow: CANCEL
Allow: OPTIONS
Allow: BYE
Allow: REFER
Allow: SUBSCRIBE
Allow: NOTIFY
User-agent: e-fon
Max-forwards: 68
Date: Tue, 01 Mar 2011 18:07:19 GMT
Content-Length: 364
v=0
o=root 18478 18478 IN IP4 192.168.1.1
s=session
c=IN IP4 192.168.1.1
t=0 0
m=audio 7072 RTP/AVP 8 0 111 3 97 18 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:111 G726-32/8000
a=rtpmap:3 GSM/8000
a=rtpmap:97 iLBC/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
Sent to udp:192.168.1.1:5060 at 1/3/2011 19:07:18:653 (661 bytes):
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 192.168.1.1:5060;branch=z9hG4bK6ae294d9626a9d6fb5aa2b3c5e4aaf7f
Via: SIP/2.0/UDP 212.55.198.132;branch=z9hG4bK0e07.09bd32f3.0
Via: SIP/2.0/UDP 212.55.198.131:5061;branch=z9hG4bK117233d9;rport=5061
From: "0763551620" <sip:0763551620@212.55.198.131:5061>;tag=as130ba29e
To: <sip:username@localproxy>
Call-ID: 0bcf11697969070b5b264e535d5d4626@212.55.198.131
CSeq: 102 INVITE
User-Agent: snom821/8.4.18
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO, UPDATE
Allow-Events: talk, hold, refer, call-info
Supported: timer, 100rel, replaces, from-change
Content-Length: 0
Hi,
The first question is where does this (wrong?) "localproxy" originate.
A few questions to look at:
- Do you use a Registrar?
- Is your SNOM properly configured (Registers with an external SIP Registrar)
- If you use an external registrar I would expect a proper domain to be present and not "localproxy"
- Are there any other "funny" SIP proxies involved?
I assume that you have only one *local* phone (your SNOM) connected to siproxd.
If all fails, you can try to add a default target in the siproxd configuration. You can specify the full SIP URI that your SNOM accepts.
######################################################################
plugin_defaulttarget_log = 1
# target must be a full SIP URI with the syntax
# sip:user@host
plugin_defaulttarget_target = sip:internal@dddd:port
Best regards,
/Thomas
Hi Thomas
First of all, thanks for the fast input.
As to your questions:
1) I do use a registrar
2) The SNOM registers properly with the registrar (at least I think - outbound calls are possible)
3) There is a proper domain present at the siproxd… it seems as if siproxd replaces the proper domain name with the localproxy
4) No other SIP proxies are involved
I do have several local phones (3 to be precise) and I'm also using 2 different accounts. All three phones (all SNOM) have the same issue/problem.
Are there situations where siproxd (I use it as plugin on pfSense) addes the localproxy as domain?
Best regards
reto
Hi Reto,
Could you make a debug log file (debuglevel=-1) from siproxd beginning at starting siproxd, including the registration sequence of your phone at the provider and such an incoming call that fails. I will have a look what is going on and where the localproxy is coming from.
What I can say, there is no hardcoded way that siproxd does substitute a hostname by localproxy. It must be present somewhere outside siproxd (the hostname of the machine running siproxd comes to mind - ?).
Personally I'm using siproxd to masquerady several SIP accounts, also including a SNOM phone as local UA and have not seen such problems, so I'm confident that it is possible to get this working.
Please send the logfile to my SF email account and don't attach it here.
Best regards,
/Thomas