There are 2 port setting that you can change. Either you change the signalling port to contact SER:
when specifying the SIP Server just do: sip_server:port
In this case, if you change the port, make sure that your SER Server is listening on that port as well.
Or you can change the listen port of your Softphone. In this case, you don't need to alter anything else. Not sure about what you wanted. Can you provide the SIP messages log?
Jose Simoes
On 12/13/05, Juan <juan@uwtcallback.com> wrote:
Hi Jose.
I tried your way but I did not get it registred. I used many ports but couldn't get it registred.
I am not using any authentication and when using port 5060 the softphone registres OK.
My SER and my softphone (X- lite) are on the same network.
Any ideas?
Thanks in advance,
Juan Ferrari
United World Telecom
Most softphones allow that. When you are specifying a SIP server, for default (normally) it uses 5060. If you want to alter this port just do the following:
ser_IP_address:port_number
Jose Simoes
p.s. this works with X-Lite
On 12/5/05, Andrey Kouprianov <andrey.kouprianov@gmail.com
> wrote:
I guess it depends on your softphone... if it chooses to communicate
from port 5060, there's nothing you can do about it, unless you can
change it in the phone's settings...
Some softphones, for instance, get a random port...
On 12/5/05, sagar <
vids_cs@yahoo.com> wrote:
> Hi All,
>
> I am using ser 0.8.14 +asterisk B2bua.
>
> Currently softphone is registering on standard sip port 5060 .
> Is it possibe to use any other port like 5090 or 8069
>
>
> I tried to do so by changing the listining port to 5090 in ser.cfg but in
> case the softphone is not getting register.
>
>
> Here is the ser log
>
>
> 0(11348) SIP Request:
> 0(11348) method: <REGISTER>
> 0(11348) uri: <sip: 192.168.1.100>
> 0(11348) version: <SIP/2.0>
> 0(11348) parse_headers: flags=1
> 0(11348) end of header reached, state=5
> 0(11348) parse_headers: Via found, flags=1
> 0(11348) parse_headers: this is the first via
> 0(11348) After parse_msg...
> 0(11348) preparing to run routing scripts...
> 0(11348) DEBUG : is_maxfwd_present: searchi ng for max_forwards header
> 0(11348) parse_headers: flags=128
> 0(11348) DEBUG: is_maxfwd_present: value = 70
> 0(11348) parse_headers: flags=8
> 0(11348) DEBUG: add_param:
> tag=fa37b062306344d68023aed26289e820
> 0(11348) DEBUG: add_param: epid=f657995ecc
> 0(11348) end of header reached, state=29
> 0(11348) parse_headers: flags=256
> 0(11348) end of header reached, state=9
> 0(11348) DEBUG: get_hdr_field: <To> [37];
> uri=[sip:2851816416@192.168.1.100:5090]
> 0(11348) DEBUG: to body [<
sip:2851816416@192.168.1.100:5090>
> ]
> 0(11348) get_hdr_field: cseq <CSeq>: <1> <REGISTER>
> 0(11348) DEBUG: get_hdr_body : content_length=0
> 0(11348) found end of header
> 0(11348) find_first_route(): No Route headers found
> 0(11348) loose_route(): There is no Route HF
> 0(11348) parse_headers: flags=64
> 0(11348) parse_headers: flags=64
> 0(11348) parse_headers: flags=33554432
> 0(11348) check_self - checking if host==us: 13==13 && [192.168.1.100] ==
> [
192.168.1.100 ]
> 0(11348) check_self - checking if port 5090 matches port 5060
> 0(11348) check_self: host != me
> 0(11348) DEBUG: t_addifnew: msg id=1 , global msg id=0 , T on
> entrance=0xffffffff
> 0(11348) parse_headers: flags=-1
> 0(11348) parse_headers: flags=60
> 0(11348) t_lookup_request: start searching: hash=58712, isACK=0
> 0(11348) DEBUG: proceeding to pre-RFC3261 transaction matching
> 0(11348) DEBUG: t_lookup_request: no transaction found
> 0(11348) DEBUG: mk_proxy: doing DNS lookup...
> 0(11348) check_via_address(
192.168.1.2, 192.168.1.2, 0)
> 0(11348) DEBUG: add_to_tail_of_timer[4]: 0xb6165fe8
> 0(11348) DEBUG: add_to_tail_of_timer[0]: 0xb6165ffc
> 0(11348) SER: new transacti on fwd'ed
> 0(11348) DEBUG:destroy_avp_list: destroing list (nil)
> 0(11348) receive_msg: cleaning up
>
> Please advise.
>
> Thanks In Advance.
>
>
> ________________________________
> Yahoo! Personals
> Single? There's someone we'd like you to meet.
> Lots of someones, actually. Yahoo! Personals
>
>
> _______________________________________________
> Serusers mailing list
> serusers@lists.iptel.org
>
http://lists.iptel.org/mailman/listinfo/serusers
>
>
>
_______________________________________________
Serusers mailing list
serusers@lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers