[Spce-user] Faxing T.38

Martin Stix ms at pluteus.at
Thu Jul 10 07:57:29 EDT 2014


Ok, no, this is just because I reactivated my proxy.cfg.customtt.tt2

If I remove it I have the same issues with t.38.

regards


mit freundlichen Grüßen
best regards
Martin Stix
CEO
pluteus communication solutions
ms at pluteus.at<mailto:ms at pluteus.at>
www.pluteus.at
Dampfsägestraße 17
3300 Amstetten
Austria
tel.: +43 7472 28165 20
fax.: +43 7472 28165 22

Von: Martin Stix [mailto:ms at pluteus.at]
Gesendet: Donnerstag, 10. Juli 2014 13:45
An: Matthew Ogden
Cc: spce-user
Betreff: Re: [Spce-user] Faxing T.38

Hi!

Hi!

Just saw this when executing ngcpcfg apply, can this be related?


Starting Asterisk PBX: asterisk.
Executing action for /etc/ngcp-config/templates/etc/kamailio/proxy/ngcpcfg.servi                                                        ces
Not executing command for kamailio-proxy: invalid configuration file!
-e
0(16765) ERROR: <core> [cfg.y:3272]: yyparse(): cfg. parser: failed to find com                                                        mand rtpproxy_answer
0(16765) : <core> [cfg.y:3411]: yyerror_at(): parse error in config file /etc/k                                                        amailio/proxy/proxy.cfg, line 369, column 38: unknown command, missing loadmodul                                                        e?

0(16765) ERROR: <core> [cfg.y:3272]: yyparse(): cfg. parser: failed to find com                                                        mand rtpproxy_offer
0(16765) : <core> [cfg.y:3411]: yyerror_at(): parse error in config file /etc/k                                                        amailio/proxy/proxy.cfg, line 446, column 37: unknown command, missing loadmodul                                                        e?

0(16765) ERROR: <core> [cfg.y:3272]: yyparse(): cfg. parser: failed to find com                                                        mand rtpproxy_destroy
0(16765) : <core> [cfg.y:3411]: yyerror_at(): parse error in config file /etc/k                                                        amailio/proxy/proxy.cfg, line 1475, column 23: unknown command, missing loadmodu                                                        le?

0(16765) ERROR: <core> [cfg.y:3272]: yyparse(): cfg. parser: failed to find com                                                        mand rtpproxy_destroy
0(16765) : <core> [cfg.y:3411]: yyerror_at(): parse error in config file /etc/k                                                        amailio/proxy/proxy.cfg, line 1501, column 24: unknown command, missing loadmodu                                                        le?

0(16765) ERROR: <core> [cfg.y:3272]: yyparse(): cfg. parser: failed to find com                                                        mand rtpproxy_answer
0(16765) : <core> [cfg.y:3411]: yyerror_at(): parse error in config file /etc/k                                                        amailio/proxy/proxy.cfg, line 5087, column 37: unknown command, missing loadmodu                                                        le?

0(16765) ERROR: <core> [cfg.y:3272]: yyparse(): cfg. parser: failed to find com                                                        mand rtpproxy_offer
0(16765) : <core> [cfg.y:3411]: yyerror_at(): parse error in config file /etc/k                                                        amailio/proxy/proxy.cfg, line 5125, column 36: unknown command, missing loadmodu                                                        le?

0(16765) ERROR: <core> [cfg.y:3272]: yyparse(): cfg. parser: failed to find com                                                        mand rtpproxy_offer
0(16765) : <core> [cfg.y:3411]: yyerror_at(): parse error in config file /etc/k                                                        amailio/proxy/proxy.cfg, line 6192, column 35: unknown command, missing loadmodu                                                        le?

ERROR: bad config file (7 errors)

regards



mit freundlichen Grüßen
best regards
Martin Stix
CEO
pluteus communication solutions
ms at pluteus.at<mailto:ms at pluteus.at>
www.pluteus.at<http://www.pluteus.at>
Dampfsägestraße 17
3300 Amstetten
Austria
tel.: +43 7472 28165 20
fax.: +43 7472 28165 22

Von: Matthew Ogden [mailto:matthew at tenacit.net]
Gesendet: Mittwoch, 09. Juli 2014 21:05
An: Martin Stix
Cc: Daniel Grotti; spce-user
Betreff: Re: AW: AW: [Spce-user] Faxing T.38


If you are sure you don't have sdp fillter settings then it does look like it must be something wrong in the generic templates you are using of 3.3.1

I am not even sure how to downgrade.  I usually use a vm so I can roll back easily age testing my call scenarios on our backup server.

Hopefully someone from sipwise is able to shed some more light.
On 09 Jul 2014 10:41 AM, "Martin Stix" <ms at pluteus.at<mailto:ms at pluteus.at>> wrote:
Hi!

Attached the 2 sanitized logfiles for that call.

Also my only custom proxy template where I rewrite anonymous calls.
($var(caller_uri) = “sip:anonymous@” + $avp(s:callee_domain);)
But just saw this template file was marked as old….So actually no special config.

regards


mit freundlichen Grüßen
best regards
Martin Stix
CEO
pluteus communication solutions
ms at pluteus.at<mailto:ms at pluteus.at>
www.pluteus.at<http://www.pluteus.at>
Dampfsägestraße 17
3300 Amstetten
Austria
tel.: +43 7472 28165 20<tel:%2B43%207472%2028165%2020>
fax.: +43 7472 28165 22<tel:%2B43%207472%2028165%2022>

Von: Matthew Ogden [mailto:matthew at tenacit.net<mailto:matthew at tenacit.net>]
Gesendet: Mittwoch, 09. Juli 2014 08:55
An: Martin Stix
Cc: Daniel Grotti; spce-user
Betreff: Re: AW: [Spce-user] Faxing T.38


Hi Martin

Did you manage to find the issue?
On 08 Jul 2014 6:30 PM, "Martin Stix" <ms at pluteus.at<mailto:ms at pluteus.at>> wrote:

Hi!



I'm on

mr3.3.1<https://www.sipwise.com/news/announcements/sipprovider-v3-3-released/>

​I'll do the new traces and send the logs.




Mit freundlichen Grüßen
best regards

Martin Stix
________________________________
Von: Matthew Ogden <matthew at tenacit.net<mailto:matthew at tenacit.net>>
Gesendet: Dienstag, 8. Juli 2014 18:18
An: Martin Stix
Cc: Daniel Grotti; spce-user
Betreff: Re: [Spce-user] Faxing T.38


Ya its not ideal that is not working.  Are you sure you are on the latest version of 2.8.

I can't remember the commands (I'm using my mobile right now).  But if you search through some of my posts someone like Daniel or Andreas is probably showing someone like me how.  So get that output in the mean time.

The next thing I would do is some the Wireshark screenshot like you did. For both call legs together - just multi select them at the same time.

Lastly show your kamailio proxy and lb loss for the same call.  Just do a search  and replace to "sanitize" them before sending them. If you any custom template files attach that too.
Then at least all the info is available to the next sip wise person you reads your email.

Kind regards
On 08 Jul 2014 4:20 PM, "Martin Stix" <ms at pluteus.at<mailto:ms at pluteus.at>> wrote:
Hi!

Tested with various pbx's and xcapi, same results.
The test pbx before only accepts t.38, no g711.

Regards


Mit freundlichen Grüßen
Martin Stix
ms at pluteus.at<mailto:ms at pluteus.at>

-------- Ursprüngliche Nachricht --------
Von: Daniel Grotti
Datum:08.07.2014 13:36 (GMT+01:00)
An: spce-user at lists.sipwise.com<mailto:spce-user at lists.sipwise.com>
Betreff: Re: [Spce-user] Faxing T.38

Hi Martin,
there is no way to terminate T38 on SPCE.
If your clients support T38 you can pass-through.
Otherwise, they need to negotiate by their self G711.

SPCE acts as a relay in this case.

That looks like a broken PBX, cause the communication is establish in G711, and then the PBX try to send a T38 re-invite which is rejected with a 488.
At this point the PBX should continue in G711 instead of send a BYE.

Daniel




On 07/08/2014 11:47 AM, Martin Stix wrote:

Hi!



Here's the one from client device, you see Reinvite to T.38:



[cid:image001.png at 01CF9C46.E3383870]

regards







mit freundlichen Grüßen

best regards

Martin Stix

CEO

pluteus communication solutions

ms at pluteus.at<mailto:ms at pluteus.at>

www.pluteus.at<http://www.pluteus.at/>

Dampfsägestraße 17

3300 Amstetten

Austria

tel.: +43 7472 28165 20<tel:%2B43%207472%2028165%2020>

fax.: +43 7472 28165 22<tel:%2B43%207472%2028165%2022>



-----Ursprüngliche Nachricht-----
Von: Andreas Granig [mailto:agranig at sipwise.com]
Gesendet: Dienstag, 08. Juli 2014 11:38
An: spce-user at lists.sipwise.com<mailto:spce-user at lists.sipwise.com>
Betreff: Re: [Spce-user] Faxing T.38



Hello,



You need to figure out where the re-invite is really coming from. The NGCP itself never initiates re-invites by itself. Probably it's the user's device? You need to capture the full call, not only the leg from NGCP to carrier.



Andreas



On 07/08/2014 11:04 AM, Martin Stix wrote:

> Hi!

>

> Has anything changed from 3.2 to 3.3.1?

>

>

>

> We are no longer able to terminate T.38 in and outgoing.

>

>

>

> Shouldn’t there be T.38 in Reinvite? It now shows g711U.

>

> From client to sipwise it states T.38.

>

>

>

> If nothing changed I have to bother my carrier.

>

>

>

> Screenshot:

>

>

>

>

>

> Thanks

>

>

>

>

>

>

>

>

>

> mit freundlichen Grüßen

> best regards

>

> *Martin Stix*

>

> CEO

> pluteus communication solutions

> ms at pluteus.at<mailto:ms at pluteus.at> <mailto:ms at pluteus.at>

>

> www.pluteus.at<http://www.pluteus.at/>

>

> Dampfsägestraße 17

> 3300 Amstetten

> Austria

> tel.: +43 7472 28165 20<tel:%2B43%207472%2028165%2020>

> fax.: +43 7472 28165 22<tel:%2B43%207472%2028165%2022>

>

>

>

>

>

> _______________________________________________

> Spce-user mailing list

> Spce-user at lists.sipwise.com<mailto:Spce-user at lists.sipwise.com>

> http://lists.sipwise.com/listinfo/spce-user

>



_______________________________________________

Spce-user mailing list

Spce-user at lists.sipwise.com<mailto:Spce-user at lists.sipwise.com>

http://lists.sipwise.com/listinfo/spce-user


_______________________________________________

Spce-user mailing list

Spce-user at lists.sipwise.com<mailto:Spce-user at lists.sipwise.com>

http://lists.sipwise.com/listinfo/spce-user


_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com<mailto:Spce-user at lists.sipwise.com>
http://lists.sipwise.com/listinfo/spce-user
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140710/18cc9aac/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 47753 bytes
Desc: image001.png
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140710/18cc9aac/attachment-0001.png>


More information about the Spce-user mailing list