Well, I activated the max forward check and also added the 'alias= 192.168.1.240' to the global config section of the ser.cfg. But I am still getting "483 too many hops" I have disabled register for the time being. But then i should be getting 404 and not 483 as you suggested.If its a problem of local memory being overrun, how do i resolve this issue? Have attached the ser.cfg file for ref. Any comments? Regards and TIA, Urvish
On Wednesday 26 November 2003 , Nils Olheimer wrote: Simply Ser does not recognize, that 192.168.1.240 is its local name (probably because that IP is not resolvable via DNS). And, for whatever reason, you deactivated the maximum forward check. Thus the INVITE is forward in an endless loop to Ser itself (you can probably see that if you sniff on the loopback interface). Finaly the request is probably getting so big, that Ser is getting out of (local) memory. 1. activate the maximxum forward check in the begining of your route section. Then you should receive "483 Too Many Hops" instead of the 500. 2. add 'alias = 192.168.1.240' to your global config section, then Ser should recognize that the request is for the local proxy (and you will probably receive 404, because your phone is not regeistered)
Greets Nils
On Wednesday 26 November 2003 17:22, Urvish Khandwalla wrote:
i have a 6 line SIP phone. Its IP address is 192.168.1.159. Im placing a call to 5555 ( another line on the same phone). I have set the proxy for both the lines to my SERs IP address (192.168.1.240).I havent enabled register with proxy on the phone but i tried that before and that gave me the same server error as the one mentioned below.
These are the packets that i have captured while making the call. Now the problem is that I am unable to understand the kind of internal error it is giving.
18 6.670873 192.168.1.159 192.168.1.240 SIP/SDPRequest: INVITE sip:5555 at 192.168.1.240, with session description
19 6.671179 192.168.1.240 192.168.1.159 SIPStatus: 100 trying -- your call is important to us
20 6.732622 192.168.1.240 192.168.1.159 SIPStatus: 500 I'm terribly sorry, server error occured (2/TM)
21 6.801520 192.168.1.159 192.168.1.240 SIPRequest: ACK sip:5555 at 192.168.1.240
Also the SIP message header of Packet 20 , as shown below, talks about warning 392. Does anyone know what warning it is?
FRAME 20: Session Initiation Protocol Status line: SIP/2.0 500 I'm terribly sorry, server error occured (2/TM) Message Header Via: SIP/2.0/UDP 192.168.1.159:5060 From: "in2" <sip:in2 at 192.168.1.240>;tag=00036b3c33b500071afb6b0a-38f8c47a To: <sip:5555 at 192.168.1.240>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-188d
Call-ID:
00036b3c-33b50007-2047443d-0967cdd3 at 192.168.1.159 CSeq: 101 INVITE Server: Sip EXpress router (0.8.11 (i386/linux)) Content-Length: 0 Warning: 392 192.168.1.240:5060 "Noisy feedback tells: pid=925 req_src_ip=192.168.1.240 req_src_port=5060 in_uri=sip:5555 at 192.168.1.240 out_uri=sip:5555 at 192.168.1.240 via_cnt==112"
I have attached my ser.sfg for your reference. TIA, Urvish Khandwalla
On Nov 27, 2003 at 00:46, Urvish Khandwalla Urvish.Khandwalla@colorado.edu wrote:
Well, I activated the max forward check and also added the 'alias= 192.168.1.240' to the global config section of the ser.cfg. But I am still getting "483 too many hops" I have disabled register for the time being. But then i should be getting 404 and not 483 as you suggested.If its a problem of local memory being overrun, how do i resolve this issue?
You don't need to add an ip address as an alias. Aliases are for domain names that cannot be detected by ser on startup (reverse dns (listen ips) doesn't include your domain name).
You get 483 because you enabled maxforwards and now the if the message is forwarded more then 10 times, it will be dropped and you'll get this message (as opposed to running out of memory when forwardind the message back to yourself forever).
Have attached the ser.cfg file for ref. Any comments?
if (uri=~"mydomain.com") {
This is the check that fails. Probably you use a domain name !=mydomain.com. It is better and safer to add all your domain to "alias=" and use if (uri==myself). If you don't want to use "myself", you should at least add your real domain name, host name and ip address to the if (uri~=) check.
Andrei
Hello,
sip:5555 is not a valid SIP URI, your clients should also put a domain into the URI.
Jan.
On 27-11 00:46, Urvish Khandwalla wrote:
Well, I activated the max forward check and also added the 'alias= 192.168.1.240' to the global config section of the ser.cfg. But I am still getting "483 too many hops" I have disabled register for the time being. But then i should be getting 404 and not 483 as you suggested.If its a problem of local memory being overrun, how do i resolve this issue? Have attached the ser.cfg file for ref. Any comments? Regards and TIA, Urvish
On Wednesday 26 November 2003 , Nils Olheimer wrote: Simply Ser does not recognize, that 192.168.1.240 is its local name (probably because that IP is not resolvable via DNS). And, for whatever reason, you deactivated the maximum forward check. Thus the INVITE is forward in an endless loop to Ser itself (you can probably see that if you sniff on the loopback interface). Finaly the request is probably getting so big, that Ser is getting out of (local) memory.
- activate the maximxum forward check in the begining of your route section.
Then you should receive "483 Too Many Hops" instead of the 500. 2. add 'alias = 192.168.1.240' to your global config section, then Ser should recognize that the request is for the local proxy (and you will probably receive 404, because your phone is not regeistered)
Greets Nils
On Wednesday 26 November 2003 17:22, Urvish Khandwalla wrote:
i have a 6 line SIP phone. Its IP address is 192.168.1.159. Im placing a call to 5555 ( another line on the same phone). I have set the proxy for both the lines to my SERs IP address (192.168.1.240).I havent enabled register with proxy on the phone but i tried that before and that gave me the same server error as the one mentioned below.
These are the packets that i have captured while making the call. Now the problem is that I am unable to understand the kind of internal error it is giving.
18 6.670873 192.168.1.159 192.168.1.240 SIP/SDPRequest: INVITE sip:5555 at 192.168.1.240, with session description
19 6.671179 192.168.1.240 192.168.1.159 SIPStatus: 100 trying -- your call is important to us
20 6.732622 192.168.1.240 192.168.1.159 SIPStatus: 500 I'm terribly sorry, server error occured (2/TM)
21 6.801520 192.168.1.159 192.168.1.240 SIPRequest: ACK sip:5555 at 192.168.1.240
Also the SIP message header of Packet 20 , as shown below, talks about warning 392. Does anyone know what warning it is?
FRAME 20: Session Initiation Protocol Status line: SIP/2.0 500 I'm terribly sorry, server error occured (2/TM) Message Header Via: SIP/2.0/UDP 192.168.1.159:5060 From: "in2" <sip:in2 at 192.168.1.240>;tag=00036b3c33b500071afb6b0a-38f8c47a To: <sip:5555 at 192.168.1.240>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-188d
Call-ID:
00036b3c-33b50007-2047443d-0967cdd3 at 192.168.1.159 CSeq: 101 INVITE Server: Sip EXpress router (0.8.11 (i386/linux)) Content-Length: 0 Warning: 392 192.168.1.240:5060 "Noisy feedback tells: pid=925 req_src_ip=192.168.1.240 req_src_port=5060 in_uri=sip:5555 at 192.168.1.240 out_uri=sip:5555 at 192.168.1.240 via_cnt==112"
I have attached my ser.sfg for your reference. TIA, Urvish Khandwalla
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-
Andrei Pelinescu-Onciul -
Jan Janak -
Urvish Khandwalla