Mike, how exactly should I format the file? I got the pcap file, how do I convert it to text so that you can easily read it?
On Sun, Oct 4, 2009 at 6:48 PM, Michael Jerris <[email protected]> wrote: > I've never been able to read these, why exactly do I need a text protocol > to be decoded for me? Ends up being too much noise so I just don't bother. > Mike > > On Oct 4, 2009, at 6:19 PM, Nicolas Brenner wrote: > > Here it is: > > - http://pastebin.freeswitch.org/10582 > > (it is the pcap file I sent on the first email of this thread, converted to > text with 'tshark -V -r') > > On Sun, Oct 4, 2009 at 5:40 PM, Michael Jerris <[email protected]> wrote: > >> can you send a link of a text sip trace please. >> >> On Oct 1, 2009, at 3:29 PM, Nicolas Brenner wrote: >> >> Any ideas about this? >> >> The SIP provider is offering H323, but I'm not quite sure about that, is >> mod_opal working right? >> >> Thanks! >> >> Nicolas >> >> On Tue, Sep 29, 2009 at 6:42 PM, Nicolas Brenner >> <[email protected]>wrote: >> >>> Anthony, thanks. Below are my config files for the two gateways from the >>> sip trace. Both files are located in conf/directory/default. >>> >>> --------------------- >>> >>> redvoiss.xml (the one that works) >>> >>> <include> >>> <user id="gateway_redvoiss"> >>> <gateways> >>> <gateway name="redvoiss-pp"> >>> <param name="username" value="xxxxxxx"/> >>> <param name="password" value="xxxxxxx"/> >>> <param name="from-domain" value="pxextmy.redvoiss.net"/> >>> <param name="realm" value="pxextmy.redvoiss.net"/> >>> <param name="proxy" value="pxextmy.redvoiss.net"/> >>> <param name="from-user" value="xxxxxxx"/> >>> <param name="caller-id-in-from" value="false"/> >>> <param name="expire-seconds" value="600"/> >>> <param name="register" value="true"/> >>> <param name="retry_seconds" value="5"/> >>> <param name="extension" value="2010"/> >>> <param name="context" value="public"/> >>> <param name="codec-prefs" value="G729"/> >>> <param name="rfc2833-pt" value="101"/> >>> </gateway> >>> </gateways> >>> <params> >>> <param name="password" value="4321"/> >>> </params> >>> </user> >>> </include> >>> >>> --------------------- >>> >>> orange.xml (the one that doesn't work) >>> >>> <include> >>> <user id="gateway_orange"> >>> <gateways> >>> <gateway name="orange"> >>> <param name="username" value="xxxxxxx"/> >>> <param name="password" value="xxxxxxx"/> >>> <param name="from-domain" value="216.72.10.39"/> >>> <param name="realm" value="216.72.10.39"/> >>> <param name="proxy" value="216.72.10.39"/> >>> <param name="from-user" value="xxxxxxx"/> >>> <param name="caller-id-in-from" value="false"/> >>> <param name="expire-seconds" value="600"/> >>> <param name="register" value="true"/> >>> <param name="retry_seconds" value="5"/> >>> <param name="extension" value="2011"/> >>> <param name="context" value="public"/> >>> <param name="codec-prefs" value="G729"/> >>> <param name="rfc2833-pt" value="101"/> >>> </gateway> >>> </gateways> >>> <params> >>> <param name="password" value="4321"/> >>> </params> >>> </user> >>> </include> >>> >>> --------------------- >>> >>> If I remove the register=true param for the non-working gateway, I don't >>> get the registration error on the cli, but then all call attempts get >>> rejected with a 401 Unauthorized, and I get a hangup cause of >>> NORMAL_UNSPECIFIED. >>> >>> >>> Best, >>> >>> Nicolas >>> >>> >>> >>> On Tue, Sep 29, 2009 at 2:22 PM, Anthony Minessale < >>> [email protected]> wrote: >>> >>>> 900 level errors are sofia internal errors so probably something is >>>> wrong with your gateway config xml. >>>> if you want to send it with any critical info replaced with XXX maybe we >>>> can see the issue for you. >>>> >>>> >>>> >>>> On Tue, Sep 29, 2009 at 1:05 PM, Nicolas Brenner <[email protected] >>>> > wrote: >>>> >>>>> Hello everyone, >>>>> >>>>> I am trying to add a gateway, but after configuring it just like the >>>>> others gateways I have, it is failing to register with a message like >>>>> this: >>>>> >>>>> 2009-09-29 12:54:40.853440 [ERR] sofia_reg.c:1402 orange Registration >>>>> Failed with status Operation has no matching challenge [904]. failure #1 >>>>> 2009-09-29 12:54:40.906798 [WARNING] sofia_reg.c:364 orange Failed >>>>> Registration, setting retry to 10 seconds. >>>>> >>>>> I captured the sip traffic and noticed that when trying to register >>>>> with one gateway (the one that works), I get a "Trying" reply immediately >>>>> followed by a "401 Unauthorized" which contains a "WWW-Authenticate: >>>>> digest" >>>>> with a "qop=auth" parameter. Then Freeswitch replies with a second >>>>> REGISTER >>>>> including a large "Authorization: digest" section with cnonce and >>>>> nc=00000001 parameters. >>>>> >>>>> The gateway which doesn't register, doesn't send the "qop=auth" >>>>> parameter together with the "401 Unauthorized", and then Freeswitch sends >>>>> a >>>>> "Authorization: digest" section on the second REGISTER with no cnonce or >>>>> nc >>>>> parameters. >>>>> >>>>> I know very little abouth SIP, so I'm wondering what this "qop=auth" >>>>> parameter means and how does it affect the registration process. Is there >>>>> any way to do without the qop=auth parameter? >>>>> >>>>> Also, I tried registering with X-Lite directly to the gateway, and it >>>>> worked, so it appears to be a problem in the Freeswitch/gateway >>>>> combination. >>>>> (Note: X-Lite sends an "Authorization: digest" section on the _first_ >>>>> REGISTER, apparently this makes a difference) >>>>> >>>>> Attached is a sip trace for the registration traffic when doing "sofia >>>>> profile external restart reloadxml" on the cli, captured with "tshark -i >>>>> eth0 -o "rtp.heuristic_rtp: TRUE" -w /tmp/capture.pcap -b filesize:51200 >>>>> -b >>>>> files:100 -R 'sip or rtp or icmp or dns or rtcp or t38'" >>>>> >>>>> >> _______________________________________________ >> FreeSWITCH-users mailing list >> [email protected] >> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users >> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users >> http://www.freeswitch.org >> >> > _______________________________________________ > FreeSWITCH-users mailing list > [email protected] > http://lists.freeswitch.org/mailman/listinfo/freeswitch-users > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users > http://www.freeswitch.org > > > > _______________________________________________ > FreeSWITCH-users mailing list > [email protected] > http://lists.freeswitch.org/mailman/listinfo/freeswitch-users > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users > http://www.freeswitch.org > >
_______________________________________________ FreeSWITCH-users mailing list [email protected] http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
