Jump to content

penta s.r.l.

Members
 View Profile  See their activity

  • Posts

    38

  • Joined

  • Last visited

 Content Type 

Posts posted by penta s.r.l.

  1. Error: 400 Bad Request

    in Trunk Setup

    Posted

    Well, that does not mean that the registrar is RFC compliant. I don't see why the REGISTER should be a Bad Request.

     

    So far the pbxnsip trunk was able to register will all popular SIP providers. Maybe SPS EUT can tell what is bad in the register request... I don't see it.

    Strangely enough, I've deleted the trunk and recreated it (using the same data) and now it works.. :)

  2. Error: 400 Bad Request

    in Trunk Setup

    Posted

    Not sure, but it seems that this is not the first request that the PBX sends to the provider.

     

    I never heared about a server with the name "SPS EUT GW 01", maybe they have written their own little SIP software.

     

    The problem is that I can register to the provider using EyeBeam but not with pbxnsip. :)

  3. Error: 400 Bad Request

    in Trunk Setup

    Posted

    Could you help me to decode the error following this request to register?

    Thank you.

     

    [7] 2009/06/18 23:48:11: SIP Tx udp:83.211.227.21:5060:

    REGISTER sip:voip.eutelia.it SIP/2.0

    Via: SIP/2.0/UDP 192.168.xx.yy:5060;branch=z9hG4bK-8be9d4687e29492fe66a65a56eaba639;rport

    From: "111222333" <sip:111222333@voip.eutelia.it>;tag=53223

    To: "111222333" <sip:111222333@voip.eutelia.it>

    Call-ID: bo8pfk8d@pbx

    CSeq: 47528 REGISTER

    Max-Forwards: 70

    Contact: <sip:111222333@192.168.xx.yy:5060;transport=udp;line=d3d94468>;+sip.instance="<urn:uuid:290191a7-c420-4279-b874-d847a684834c>"

    User-Agent: pbxnsip-PBX/3.3.0.3165

    Authorization: Digest realm="voip.eutelia.it",nonce="4a392a5aea78754b2fea45340545c05306936a85",response="19b7a13e513d4ef2b41c81db67e62c97",username="111222333@83.211.227.21",uri="sip:voip.eutelia.it",qop=auth,nc=00001728,cnonce="49a6eb92",algorithm=MD5

    Expires: 3600

    Content-Length: 0

     

    [7] 2009/06/18 23:48:11: SIP Rx udp:83.211.227.21:5060:

    SIP/2.0 400 Bad Request

    Via: SIP/2.0/UDP 192.168.xx.yy:5060;branch=z9hG4bK-8be9d4687e29492fe66a65a56eaba639;rport=5060;received=88.32.xx.yy

    From: "111222333" <sip:111222333@voip.eutelia.it>;tag=53223

    To: "111222333" <sip:111222333@voip.eutelia.it>;tag=d7cbdeb4f107ce82ed834cadd3d6dbb2.fcc2

    Call-ID: bo8pfk8d@pbx

    CSeq: 47528 REGISTER

    Server: SPS EUT GW 01 (0.9.6 (i386/linux))

    Content-Length: 0

    Warning: 392 83.211.227.21:5060 "Noisy feedback tells: pid=3533 req_src_ip=88.32.xx.yy req_src_port=5060 in_uri=sip:voip.eutelia.it out_uri=sip:voip.eutelia.it via_cnt==1"

  4. Music on Hold while ringing

    in Hunt Group Setup

    Posted

    3.0.1 release notes say:

    "For small groups, it is difficult to maintain a constant service in agent groups. Having the phone ringing for a long time gives a bad impression to the caller. In order to cover these problems, the PBX now offers the option to continue playing the music on hold with the mixed IVR messages, even if the agents are ringing already."

     

    We've just upgraded our pbxnsip to v3.3

    How can we put MoH while our hunt groups are ringing??

     

    Thank you.

  6. Line monitoring on SPA94x

    in Linksys Phones

    Posted

    I tried to configure my SPA941/2 phones in order to monitor other extensions, without success.

    I'm only able to speed dial an extension using the line keys.

     

    Is there anyone using these phones with these features on?

    By the way, in the administration phone page, wich kind of server should I specify? Broadsoft, SPA9000, Asterisk or RFC3265_4235?

     

    Phones have last firmware.

     

    Nicola

  7. Conciliating dial plans and address book numbers

    in Dial Plan Setup

    Posted

    Well, this is not a stupid question. The point about version 3.1 is that address book entries and also other "telephone" numbers are internally stored in the "+" format (e.g. +3912345678). Havnig 003912345678 as well as 012345678 is just creating such a big mess that you can never be sure what number you want to dial.

    So it's best to wait for 3.1 to be released, before working on the address book.

    When you think this will happen?

     

    The "9" prefix that indicates an outside line becomes a little bit pointless in SIP. Like on the cell phone you have to push the "dial" button any way, especially in countries like Italy where you can't know how long a number is.

    If you do want a "9" prefix, the phone has to deal with it and strip it. It is just to make you comfortable to hear a dial tone after entering a nine, but it has no more technical background. Psychology. IMHO we should just get over it and just dial the number that we want to talk to.

    If you explicity want to route +-numbers in the dial plan then you have to use a pattern like "+*" or "+39*".

    I understand.. we were just studying the manual, and the great part of existing examples are US oriented. :)

     

    Anyway, right now we have 2 outbound trunks, one is the Gateway and the other is the VoIP provider.

    Due to local rates, we are using mainly the PSTN and the VoIP only when we have no more PSTN lines availables.

    To select the line, we just type '8' or '9' in front of the number.. any tip on this?

    Can we tell the pbx to use the VoIP trunk when the Gateway is full?

     

    Thank you for your answers.

     

    Nicola

  8. Dynamically changing a scheduled flag

    in Service Flags

    Posted

    Agreed, running 3.1.0.3043 (Win32)

    created a test DAY NIGHT Flag assigned my extension to change / monitor

    set time schedule for 8:00am to 11:59am, the service flag shows set,

    calling the service flag I get a dual tone acknowledgement, but the service flag remains set.

    I've never seen this feature work on any previous releases.

    I've just setup a workaround.

    The day/night service flag I use is the 79, so I've created a manual service flag 78.

    In the first auto attendant, pbxnsip evaluates first 78 and then 79.

    78 Is normally clear, so 79 does its job most of the times.

    But if I set 78 manually (using the phone), it jumps to the hunt group that usually answers, skipping the night flag.

     

    Nicola

  12. Conciliating dial plans and address book numbers

    in Dial Plan Setup

    Posted

    May be this may seems a quite stupid question, but since it's our first installation, we'll take the risk. :-)

     

    We have a dial plan like this:

     

    110 Our_VoIP_Provider 8*

    120 Our_PSTN__Gateway 9*

     

    In the address book we have to put a 9 in front of the number to route the call to the PSTN Gwy.

    This works, but callers won't be recognized when calling inbound, for the numbers do not clash.

     

    The question arises since I've seen all dial plans examples less or more like our.

     

    How do you conciliate address book numbers and dial plans?

    Do we have to add another line in the Dial Plan for calls originating from speed dial codes?

     

    e.g.

    110 Our_VoIP_Provider 8*

    120 Our_PSTN__Gateway 9*

    130 Our_PSTN__Gateway *

     

    Thank you

     

    Nicola

  13. Not displaying the address book name

    in General Setup

    Posted

    We have a trunk that redirects inbound calls to an auto-attendant, then to an hunt group.

    In this case, we see the Caller-ID but not the corresponding address book name (in the call log page of pbxnsip)

     

    If we tell the trunk to redirect incoming calls directly to an extension, then we see the matching name.

     

    We are using pbxnsip 3.0.1.3023 (Win32).

×
×
  • Create New...